Re: [PATCHES] [HACKERS] [BUGS] 7.4 beta 1: SET log_statement=false

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Yes, I have been thinking of that. The big question is whether a > > non-super user can control the reset value? > > He could (via PGOPTIONS) ... but since he can only increase it, there is > nothing to fear. I have followed your su

[PATCHES] improve runtime config docs

This patch makes a number of improvements to the runtime config documentation. -Neil Index: doc/src/sgml/runtime.sgml === RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/runtime.sgml,v retrieving revision 1.201 diff -c -r1.201 runti

Re: [PATCHES] [BUGS] PgSQL74b2: initdb fails (max_connections)

Janko Richter <[EMAIL PROTECTED]> writes: > On FreeBSD 5.1 using PgSQL 7.4b2 initdb failed with: Yeah, it's broken on any system with shmmax too small for the defaults :-(. My fault. > This patch solves the problem: It's fixed in a different way in CVS tip. regards, tom

Re: [PATCHES] [BUGS] PgSQL74b2: initdb fails (max_connections)

We just fixed this so our next beta will be correct. CVS already has the fix. --- Janko Richter wrote: > On FreeBSD 5.1 using PgSQL 7.4b2 initdb failed with: > > su-2.05b$ ./initdb -D /data/pgsql > The files belonging to t

[PATCHES] allow any ip4 or ip6 loopback address to match in default pg_hba.conf

Here's a patch that does what has been discussed on Hackers to allow a default setting in pg_hba.conf for loopback addresses, and should cause no problems no matter what style of ipv6 is or isn't configured. If it's wanted I'll document it, if not I won't :-) BTW, I notice that the sample doesn

Re: [PATCHES] 7.3: [BUGS] to_timestamp not stable if date string shorter than

Karel Zak <[EMAIL PROTECTED]> writes: >>> Hmm.. but the patch fix another small bug which I found today. >> >> Okay. Please send a patch against 7.3 tip and I'll throw it in. > The patch for REL7_3_4 is attached. Applied, thanks. regards, tom lane ---

[PATCHES] IPV4 addresses on IPV6 machines in pg_hba.conf

This was discussed in [HACKERS] TCP/IP with 7.4 beta2 broken? I created a patch to hba.c which uses IPV4 entries as IPV6 entries if running on a IPV6 system (which is detected from a port coming in as AF_INET6). 192.168.0.0/24 -> :::102.168.0/120 192.168.0.0 255.255.255.0 ->

[PATCHES] 7.3: [BUGS] to_timestamp not stable if date string shorter than

On Wed, Sep 03, 2003 at 11:53:35AM -0400, Tom Lane wrote: > Karel Zak <[EMAIL PROTECTED]> writes: > > Hmm.. but the patch fix another small bug which I found today. > > Okay. Please send a patch against 7.3 tip and I'll throw it in. The patch for REL7_3_4 is attached. Karel --

Re: [PATCHES] [BUGS] to_timestamp not stable if date string shorter than

On Wed, Sep 03, 2003 at 11:10:33AM -0400, Tom Lane wrote: > Karel Zak <[EMAIL PROTECTED]> writes: > > Fixed. All tests passed. My court is without ball now. The patch is > > attached. > > Applied to CVS HEAD. I also applied just the > > + if (flag == FROM_CHAR && *s=='\0') > +

Re: [PATCHES] [BUGS] to_timestamp not stable if date string shorter than

Karel Zak <[EMAIL PROTECTED]> writes: > Hmm.. but the patch fix another small bug which I found today. Okay. Please send a patch against 7.3 tip and I'll throw it in. regards, tom lane ---(end of broadcast)--- TIP

Re: [PATCHES] [BUGS] to_timestamp not stable if date string shorter than

Karel Zak <[EMAIL PROTECTED]> writes: > Fixed. All tests passed. My court is without ball now. The patch is > attached. Applied to CVS HEAD. I also applied just the + if (flag == FROM_CHAR && *s=='\0') + break; part to the 7.3 branch --- the rest of the

Re: [PATCHES] [BUGS] to_timestamp not stable if date string shorter than

On Wed, Sep 03, 2003 at 12:15:47AM -0400, Tom Lane wrote: > that as a full fix. Karel, the ball's in your court ... Fixed. All tests passed. My court is without ball now. The patch is attached. Thanks, it was good find! Karel -- Karel Zak <[EMAIL PROTECTED]> http://home.zf.jcu