[COMMITTERS] pgsql: Move pthread.h test up to use PTHREAD_CFLAGS.

Log Message: --- Move pthread.h test up to use PTHREAD_CFLAGS. Kris Jurka Modified Files: -- pgsql: configure (r1.405 -> r1.406) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.405&r2=1.406) configure.in (r1.383 -> r1.384)

[COMMITTERS] pgsql: fixed bug in segfault REVOKE statement

Log Message: --- fixed bug in segfault REVOKE statement Modified Files: -- pgsql/src/interfaces/ecpg/preproc: preproc.y (r1.298 -> r1.299) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/preproc.y.diff?r1=1.298&r2=1.299) -

[COMMITTERS] pgsql: fixed bug in REVOKE statement cat_str only has 8 arguments

Log Message: --- fixed bug in REVOKE statement cat_str only has 8 arguments Tags: REL7_4_STABLE Modified Files: -- pgsql/src/interfaces/ecpg/preproc: preproc.y (r1.263.2.17 -> r1.263.2.18) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfac

[COMMITTERS] pgsql: Add comment to postmaster.c that get_progname() will call exit if

Log Message: --- Add comment to postmaster.c that get_progname() will call exit if it can't strdup(). Modified Files: -- pgsql/src/backend/postmaster: postmaster.c (r1.435 -> r1.436) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/p

[COMMITTERS] pgsql: Add comment about memory failure of get_progname exiting the

Log Message: --- Add comment about memory failure of get_progname exiting the postmaster: exit(1);/* This could exit the postmaster */ Modified Files: -- pgsql/src/port: path.c (r1.40 -> r1.41) (http://developer.postgresql.org/cvsweb.cgi/pg

[COMMITTERS] pgsql: timestamptz_trunc() should only recalculate the timezone when

Log Message: --- timestamptz_trunc() should only recalculate the timezone when truncating to DAY precision or coarser; leave the timezone alone when precision is HOUR or less. This avoids surprises for inputs near a DST transition time, as per example from Matthew Gabeler-Lee. (The only r

[COMMITTERS] pgsql: Invent pg_next_dst_boundary() and rewrite

Log Message: --- Invent pg_next_dst_boundary() and rewrite DetermineLocalTimeZone() to use it, as per my proposal of yesterday. This gives us a means of determining the zone offset to impute to an unlabeled timestamp that is both efficient and reliable, unlike all our previous tries involv

[COMMITTERS] pginstaller - pginst: Bump version number

Log Message: --- Bump version number Modified Files: -- pginst: Makefile.config (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/Makefile.config.diff?r1=1.16&r2=1.17) ---(end of broadcast)

[COMMITTERS] pginstaller - pginst: Write the bindir path for pgAdmin to pick up.

Log Message: --- Write the bindir path for pgAdmin to pick up. Modified Files: -- pginst/wxs: pginst.wxs (r1.85 -> r1.86) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/wxs/pginst.wxs.diff?r1=1.85&r2=1.86) ---(end o

[COMMITTERS] pgsql: That's just the lovely way windows handles a "segfault".

Log Message: --- That's just the lovely way windows handles a "segfault". Gotta be really interesting for MS to catch all those dumps... Anyway. Oops. Seems I ran my regression tests with the old psql, and just managed to update the backend, when I tested that patch. Turns out there are co

Re: [COMMITTERS] pgsql: Clarify coding of .exe patch

Neil Conway <[EMAIL PROTECTED]> writes: > Regarding __builtin_constant_p(), it is obviously the case that we need > to ensure the code compiles on a wide variety of C compilers. But I > don't see the harm in using GCC-specific features where (a) they can be > easily #ifdef'd away when not using GCC

[COMMITTERS] pgsql: Update comment to point to proper file.

Log Message: --- Update comment to point to proper file. Modified Files: -- pgsql/src/backend/utils/adt: formatting.c (r1.80 -> r1.81) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c.diff?r1=1.80&r2=1.81) --

Re: [COMMITTERS] pgsql: Clarify coding of .exe patch

Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> writes: > > While I still think we're on pretty solid ground assuming this > > optimization is going to be made, I'm fine with defining something like > > const_strlen() that uses sizeof(). Also, we can guard against programmer > > mistakes via __bu

[COMMITTERS] pgsql: Trivial fixes for English grammar in contrib/btree_gist and

Log Message: --- Trivial fixes for English grammar in contrib/btree_gist and contrib/rtree_gist documentation. Modified Files: -- pgsql/contrib/btree_gist: README.btree_gist (r1.4 -> r1.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist