Re: [COMMITTERS] pgsql: Allow Win32 to support the O_SYNC open flag

2005-03-01 Thread Christopher Kings-Lynne
I think this should be back ported for 8.0.2... Chris Bruce Momjian wrote: Log Message: --- Allow Win32 to support the O_SYNC open flag as an wal_sync_method method. Magnus Hagander Modified Files: -- pgsql/src/include: port.h (r1.69 -> r1.70) (http://develo

[COMMITTERS] pgsql: Prevent large allocation in snprintf to hold positional

2005-03-01 Thread Bruce Momjian
Log Message: --- Prevent large allocation in snprintf to hold positional parameters. Allocated size based on format string. Modified Files: -- pgsql/src/port: snprintf.c (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/snprintf.c

[COMMITTERS] pgsql: Another go at making pred_test() handle all reasonable

2005-03-01 Thread Tom Lane
Log Message: --- Another go at making pred_test() handle all reasonable combinations of AND and OR clauses. The key point here is that an OR on the predicate side has to be treated gingerly: we may be able to prove that the OR is implied even when no one of its components is implied. For e

[COMMITTERS] pgsql: Fix snprintf on Win32: * If vsnprintf() is not before

2005-03-01 Thread Bruce Momjian
Log Message: --- Fix snprintf on Win32: * If vsnprintf() is not before snprintf() in this file, snprintf() * will call the system vsnprintf() on MinGW. Modified Files: -- pgsql/src/port: snprintf.c (r1.10 -> r1.11) (http://developer.postgresql.org/cvsw

[COMMITTERS] pgsql: Make port snprintf.c finally thread-safe.

2005-03-01 Thread Bruce Momjian
Log Message: --- Make port snprintf.c finally thread-safe. Modified Files: -- pgsql/src/port: snprintf.c (r1.9 -> r1.10) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/snprintf.c.diff?r1=1.9&r2=1.10) ---(end of broadcast

[COMMITTERS] pgsql: SGML improvements to the DML chapter.

2005-03-01 Thread Neil Conway
Log Message: --- SGML improvements to the DML chapter. Modified Files: -- pgsql/doc/src/sgml: dml.sgml (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/dml.sgml.diff?r1=1.10&r2=1.11) ---(end of broadca

[COMMITTERS] pgsql: Release proclock immediately in RemoveFromWaitQueue() if it

2005-03-01 Thread Tom Lane
Log Message: --- Release proclock immediately in RemoveFromWaitQueue() if it represents no held locks. This maintains the invariant that proclocks are present only for procs that are holding or awaiting a lock; when this is not true, LockRelease will fail. Per report from Stephen Clouse.

[COMMITTERS] pgsql: Release proclock immediately in RemoveFromWaitQueue() if it

2005-03-01 Thread Tom Lane
Log Message: --- Release proclock immediately in RemoveFromWaitQueue() if it represents no held locks. This maintains the invariant that proclocks are present only for procs that are holding or awaiting a lock; when this is not true, LockRelease will fail. Per report from Stephen Clouse.

[COMMITTERS] pgsql: Release proclock immediately in RemoveFromWaitQueue() if it

2005-03-01 Thread Tom Lane
Log Message: --- Release proclock immediately in RemoveFromWaitQueue() if it represents no held locks. This maintains the invariant that proclocks are present only for procs that are holding or awaiting a lock; when this is not true, LockRelease will fail. Per report from Stephen Clouse.

[COMMITTERS] pgsql: Allow Trace_lock_oidmin to be set to zero; this is a reasonable

2005-03-01 Thread Tom Lane
Log Message: --- Allow Trace_lock_oidmin to be set to zero; this is a reasonable representation of not wanting tracing to be limited by object OID. Modified Files: -- pgsql/src/backend/utils/misc: guc.c (r1.252 -> r1.253) (http://developer.postgresql.org/cv

[COMMITTERS] pgsql: Simplify/clean up code for varlena types

2005-03-01 Thread Teodor Sigaev
Log Message: --- Simplify/clean up code for varlena types Modified Files: -- pgsql/contrib/btree_gist: btree_bit.c (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_bit.c.diff?r1=1.2&r2=1.3) btree_bytea.c (r1.