Re: [PORTS] v6.3 release ToDo list and supported ports
Is the ix86/linux "confirmed" port using libc 5 or glibc 2.x (aka
libc6)? As most major distributions are going to release all new
versions with glibc I think it's prudent to test on both "platforms"
independantly.
-Fred
Show quoted text
Bruce, are you planning on keeping a ToDo list for the 6.3 release
as you have in (at least) the past few releases? That will make sure
that we don't leave something out. As a start:Commit sgml document sources(Thomas)
Commit html documents(Thomas)
Commit postscript documents(Thomas)
Fix aggregates in views reported by Brett
Include subselect regression tests(Thomas, unless someone else wants
it :) Fix crashes from backend collisions reported by Tom H. Fix
isinf.c irix port problem reported by Andrew(Marc) Check triggers
regression test(Vadim) Check select_views regression test Test ecpg
new struct features(Michael) Test big-endian/little-endian
operation(Tatsuo?) I don' know if we need this...Confirm ports for v6.3 (need this soon for docs):
_ aix4.2 - already fixed? what are actual versions??
_ aix3.5
_ bsdi
_ freebsd,etc (I don't know the different bsd variants)
_ 68k/bsdXXX (Macintosh port) never successful? Needed 68k locking
code?? _ dgux _ hpux9.0.x _ hpux10.20 _ alpha/unix - currently
broken? _ alpha/linux - currently broken? _ ppc/mklinux(Tatsuo?)
* ix86/linux(Thomas) - confirmed working
_ ix86/solaris
_ irix5
_ irix6
_ nextstep - not tested? not working??
_ sco
_ sparc/solaris
_ sparc/sunos
_ svr4(which platforms?)
_ ultrix4
_ univelIf a platform does not get on this list, and have a confirmed
compile/regression test, then it will go on the unsupported list for
v6.3 :( The regression tests do not have to pass completely (since
there are a couple of remaining beta problems) but the port should
compile, run, and produce reasonable results for most tests.Can people commit to checking on each platform? (I know some have
been done already...)
Import Notes
Reply to msg id not found: 34E4700D.A117ECDF@alumni.caltech.edu
Is the ix86/linux "confirmed" port using libc 5 or glibc 2.x (aka
libc6)? As most major distributions are going to release all new
versions with glibc I think it's prudent to test on both "platforms"
independently.
Yes, that is a good point. There is a known bug in the glibc2 math
library which breaks the date/time routines:
select '4 hours'::timespan;
---------
@ 4 hours
(1 row)
comes out instead as
tgl=> select '4 hours'::timespan;
----------------------------
@ 3 hours 59 mins 60.00 secs
(1 row)
Oliver was working on patches. Lost his e-mail message; is Oliver still
here? I've got a RH5.0 linux system at work now, and the shipped Postgres
installation has this problem. I'd like to see it fixed...
Bruce, can you add this to the v6.3 ToDo (assuming you agree to take it
on :)
- Tom
Oliver was working on patches. Lost his e-mail message; is Oliver still
here? I've got a RH5.0 linux system at work now, and the shipped Postgres
installation has this problem. I'd like to see it fixed...Bruce, can you add this to the v6.3 ToDo (assuming you agree to take it
on :)
To be honest, I there has been so much going on, I am not sure what to
document, especially with the ports. I don't think I ever did a good
job of tracking which ports did and did not work. I usually
concentrated on show-stopper bugs like crashes and broken features.
--
Bruce Momjian
maillist@candle.pha.pa.us
Oliver was working on patches. Lost his e-mail message; is Oliver still
here? I've got a RH5.0 linux system at work now, and the shipped Postgres
installation has this problem. I'd like to see it fixed...Bruce, can you add this to the v6.3 ToDo (assuming you agree to take it
on :)
Marc and Thomas, there are so many patches going around, I can't even
keep track that they are all getting applied. Thank goodness Marc is on
top of it.
--
Bruce Momjian
maillist@candle.pha.pa.us
On Fri, 13 Feb 1998, Bruce Momjian wrote:
Oliver was working on patches. Lost his e-mail message; is Oliver still
here? I've got a RH5.0 linux system at work now, and the shipped Postgres
installation has this problem. I'd like to see it fixed...Bruce, can you add this to the v6.3 ToDo (assuming you agree to take it
on :)Marc and Thomas, there are so many patches going around, I can't even
keep track that they are all getting applied. Thank goodness Marc is on
top of it.
I'm trying...there are some that I let "slip" I'm uncertain of
them. If *anyone* has submitted a patch recently that hasn't been
applied, it may have slipped through the cracks inadvertantly...please
repost it with a subject that includes "*REPOST*" in it...
Bruce/Thomas/Vadim...if you see one of those go through, please
take a scan as it, cause there is a good chance that I didn't apply it due
to uncertainty...
On Fri, 13 Feb 1998, Bruce Momjian wrote:
Oliver was working on patches. Lost his e-mail message; is Oliver still
here? I've got a RH5.0 linux system at work now, and the shipped Postgres
installation has this problem. I'd like to see it fixed...Bruce, can you add this to the v6.3 ToDo (assuming you agree to take it
on :)Marc and Thomas, there are so many patches going around, I can't even
keep track that they are all getting applied. Thank goodness Marc is on
top of it.I'm trying...there are some that I let "slip" I'm uncertain of
them. If *anyone* has submitted a patch recently that hasn't been
applied, it may have slipped through the cracks inadvertantly...please
repost it with a subject that includes "*REPOST*" in it...Bruce/Thomas/Vadim...if you see one of those go through, please
take a scan as it, cause there is a good chance that I didn't apply it due
to uncertainty...
Problem is, I have never been able to determine what patches you are
uncertain about.
--
Bruce Momjian
maillist@candle.pha.pa.us
On Fri, 13 Feb 1998, Bruce Momjian wrote:
Problem is, I have never been able to determine what patches you are
uncertain about.
Okay, I'll start replying to the list about patches that I'm not
personally comfortable with applying...most look okay, and I'll apply
them, but some of htem...
On Fri, 13 Feb 1998, Bruce Momjian wrote:
Problem is, I have never been able to determine what patches you are
uncertain about.Okay, I'll start replying to the list about patches that I'm not
personally comfortable with applying...most look okay, and I'll apply
them, but some of htem...
Usually we pipe up when we see a bad patch, but not always.
--
Bruce Momjian
maillist@candle.pha.pa.us
On Fri, 13 Feb 1998, Bruce Momjian wrote:
On Fri, 13 Feb 1998, Bruce Momjian wrote:
Problem is, I have never been able to determine what patches you are
uncertain about.Okay, I'll start replying to the list about patches that I'm not
personally comfortable with applying...most look okay, and I'll apply
them, but some of htem...Usually we pipe up when we see a bad patch, but not always.
Hrmmm, so reasonably safe to just apply a patch and expect that if
its a problem, someone will yell at me about it? :)
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
On Fri, 13 Feb 1998, Bruce Momjian wrote:
On Fri, 13 Feb 1998, Bruce Momjian wrote:
Problem is, I have never been able to determine what patches you are
uncertain about.Okay, I'll start replying to the list about patches that I'm not
personally comfortable with applying...most look okay, and I'll apply
them, but some of htem...Usually we pipe up when we see a bad patch, but not always.
Hrmmm, so reasonably safe to just apply a patch and expect that if
its a problem, someone will yell at me about it? :)
Yep.
--
Bruce Momjian
maillist@candle.pha.pa.us