Re: [HACKERS] Any more "must fix" issues for 7.4?
Bruce Momjian schrieb: Peter Eisentraut wrote: Bruce Momjian writes: Oh, I forgot about that. This leaves datetime.h and decimal.h in /pgsql/include. I don't see how 7.4.1 can fix that because people will not be using initdb. This has nothing to do with initdb. Right. I mean install isn't going to remove those files in /include. If you use a packaged version (.deb/.rpm etc) it will remove them. So no problem for most(?) users. Christof ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Any more "must fix" issues for 7.4?
Peter Eisentraut wrote: > Bruce Momjian writes: > > > Oh, I forgot about that. This leaves datetime.h and decimal.h in > > /pgsql/include. I don't see how 7.4.1 can fix that because people will > > not be using initdb. > > This has nothing to do with initdb. Right. I mean install isn't going to remove those files in /include. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] Any more "must fix" issues for 7.4?
Bruce Momjian writes: > Oh, I forgot about that. This leaves datetime.h and decimal.h in > /pgsql/include. I don't see how 7.4.1 can fix that because people will > not be using initdb. This has nothing to do with initdb. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Any more "must fix" issues for 7.4?
Peter Eisentraut wrote: > Tom Lane writes: > > > Barring surprises, we will institute a code freeze in the 7.4 branch > > tonight with an eye to wrapping the release Sunday. Is anyone aware > > of critical loose ends that still need to be dealt with? > > The only thing I had left was the installation locations for the Informix > compatibility headers of ECPG. But we need some more information from > Informix users about that. It will have to wait for 7.4.1. Oh, I forgot about that. This leaves datetime.h and decimal.h in /pgsql/include. I don't see how 7.4.1 can fix that because people will not be using initdb. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] Any more "must fix" issues for 7.4?
Tom Lane writes: > Barring surprises, we will institute a code freeze in the 7.4 branch > tonight with an eye to wrapping the release Sunday. Is anyone aware > of critical loose ends that still need to be dealt with? The only thing I had left was the installation locations for the Informix compatibility headers of ECPG. But we need some more information from Informix users about that. It will have to wait for 7.4.1. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Any more "must fix" issues for 7.4?
--On Thursday, November 13, 2003 13:18:31 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Larry Rosenman <[EMAIL PROTECTED]> writes: The only thing I'm aware of is the setsockopt() issue on OpenServer. We have no proposed patch for that, either, so it will also have to wait for 7.4.1. modulo the unacceptable one. I'm aware of that. We may want to note it somewhere... regards, tom lane -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: [HACKERS] Any more "must fix" issues for 7.4?
Larry Rosenman <[EMAIL PROTECTED]> writes: > The only thing I'm aware of is the setsockopt() issue on OpenServer. We have no proposed patch for that, either, so it will also have to wait for 7.4.1. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] Any more "must fix" issues for 7.4?
--On Thursday, November 13, 2003 12:43:37 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: Barring surprises, we will institute a code freeze in the 7.4 branch tonight with an eye to wrapping the release Sunday. Is anyone aware of critical loose ends that still need to be dealt with? The only thing on my own radar screen is a couple of reports of the stats collector failing to start on Solaris; but it is not yet clear whether that's our bug or a misconfiguration problem on those boxes, and I don't want to hold up the release while we find out. The only thing I'm aware of is the setsockopt() issue on OpenServer. LER regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
[HACKERS] Any more "must fix" issues for 7.4?
Barring surprises, we will institute a code freeze in the 7.4 branch tonight with an eye to wrapping the release Sunday. Is anyone aware of critical loose ends that still need to be dealt with? The only thing on my own radar screen is a couple of reports of the stats collector failing to start on Solaris; but it is not yet clear whether that's our bug or a misconfiguration problem on those boxes, and I don't want to hold up the release while we find out. regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
