[COMMITTERS] pgsql: Simplify/clean up code for varlena types
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.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_bytea.c.diff?r1=1.2&r2=1.3) btree_gist.sql.in (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_gist.sql.in.diff?r1=1.11&r2=1.12) btree_numeric.c (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_numeric.c.diff?r1=1.2&r2=1.3) btree_text.c (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_text.c.diff?r1=1.3&r2=1.4) btree_utils_var.c (r1.5 -> r1.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/btree_gist/btree_utils_var.c.diff?r1=1.5&r2=1.6) ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql: Allow Trace_lock_oidmin to be set to zero; this is a reasonable
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/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.252&r2=1.253) ---(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
[COMMITTERS] pgsql: Release proclock immediately in RemoveFromWaitQueue() if it
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. Modified Files: -- pgsql/src/backend/storage/lmgr: lock.c (r1.146 -> r1.147) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lock.c.diff?r1=1.146&r2=1.147) ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql: Release proclock immediately in RemoveFromWaitQueue() if it
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. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/storage/lmgr: lock.c (r1.145 -> r1.145.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lock.c.diff?r1=1.145&r2=1.145.4.1) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] pgsql: Release proclock immediately in RemoveFromWaitQueue() if it
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. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/storage/lmgr: lock.c (r1.128 -> r1.128.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lock.c.diff?r1=1.128&r2=1.128.2.1) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: SGML improvements to the DML chapter.
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 broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Make port snprintf.c finally thread-safe.
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)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] pgsql: Fix snprintf on Win32: * If vsnprintf() is not before
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/cvsweb.cgi/pgsql/src/port/snprintf.c.diff?r1=1.10&r2=1.11) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Another go at making pred_test() handle all reasonable
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 example (x OR y) implies (x OR y OR z) even though no one of x, y, or z can be individually proven. This code handles both the example shown recently by Sergey Koshcheyev and the one shown last October by Dawid Kuroczko. Modified Files: -- pgsql/src/backend/optimizer/path: indxpath.c (r1.168 -> r1.169) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c.diff?r1=1.168&r2=1.169) ---(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
[COMMITTERS] pgsql: Prevent large allocation in snprintf to hold positional
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.diff?r1=1.11&r2=1.12) ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [COMMITTERS] pgsql: Allow Win32 to support the O_SYNC open flag
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://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/port.h.diff?r1=1.69&r2=1.70) pgsql/src/include/port: win32.h (r1.42 -> r1.43) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/port/win32.h.diff?r1=1.42&r2=1.43) pgsql/src/port: open.c (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/open.c.diff?r1=1.7&r2=1.8) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
