[COMMITTERS] pgpool - pgpool: fix memory leak
Log Message: --- fix memory leak Modified Files: -- pgpool: pool_error.c (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpool/pgpool/pool_error.c.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgpool - pgpool: fix malloc size (not harmfull actually)
Log Message: --- fix malloc size (not harmfull actually) Modified Files: -- pgpool: main.c (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpool/pgpool/main.c.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Add comment on C locale test for upper/lower/initcap().
Log Message: --- Add comment on C locale test for upper/lower/initcap(). Modified Files: -- pgsql/src/backend/utils/adt: oracle_compat.c (r1.59 -> r1.60) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/oracle_compat.c.diff?r1=1.59&r2=1.60) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Add description: < Currently locale can only be set during
Log Message: --- Add description: < Currently locale can only be set during initdb. > Currently locale can only be set during initdb. No global tables have > locale-aware columns. However, the database template used during > database creation might have locale-aware indexes. The indexes would > need to be reindexed to match the new locale. Modified Files: -- pgsql/doc: TODO (r1.1521 -> r1.1522) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1521&r2=1.1522) pgsql/doc/src/FAQ: TODO.html (r1.28 -> r1.29) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.28&r2=1.29) ---(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 case in which a debug printout would print already-pfreed
Log Message: --- Fix case in which a debug printout would print already-pfreed data. Modified Files: -- pgsql/src/backend/access/transam: multixact.c (r1.2 -> r1.3) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/multixact.c.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Adjust time qual checking code so that we always check
Log Message: --- Adjust time qual checking code so that we always check TransactionIdIsInProgress before we check commit/abort status. Formerly this was done in some paths but not all, with the result that a transaction might be considered committed for some purposes before it became committed for others. Per example found by Jan Wieck. Modified Files: -- pgsql/src/backend/utils/time: tqual.c (r1.87 -> r1.88) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c.diff?r1=1.87&r2=1.88) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Adjust time qual checking code so that we always check
Log Message: --- Adjust time qual checking code so that we always check TransactionIdIsInProgress before we check commit/abort status. Formerly this was done in some paths but not all, with the result that a transaction might be considered committed for some purposes before it became committed for others. Per example found by Jan Wieck. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/utils/time: tqual.c (r1.81 -> r1.81.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c.diff?r1=1.81&r2=1.81.4.1) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Adjust time qual checking code so that we always check
Log Message: --- Adjust time qual checking code so that we always check TransactionIdIsInProgress before we check commit/abort status. Formerly this was done in some paths but not all, with the result that a transaction might be considered committed for some purposes before it became committed for others. Per example found by Jan Wieck. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/utils/time: tqual.c (r1.70 -> r1.70.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c.diff?r1=1.70&r2=1.70.2.1) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Adjust time qual checking code so that we always check
Log Message: --- Adjust time qual checking code so that we always check TransactionIdIsInProgress before we check commit/abort status. Formerly this was done in some paths but not all, with the result that a transaction might be considered committed for some purposes before it became committed for others. Per example found by Jan Wieck. Tags: REL7_2_STABLE Modified Files: -- pgsql/src/backend/utils/time: tqual.c (r1.49 -> r1.49.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c.diff?r1=1.49&r2=1.49.2.1) ---(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: Adjust time qual checking code so that we always check
Log Message: --- Adjust time qual checking code so that we always check TransactionIdIsInProgress before we check commit/abort status. Formerly this was done in some paths but not all, with the result that a transaction might be considered committed for some purposes before it became committed for others. Per example found by Jan Wieck. Tags: REL7_3_STABLE Modified Files: -- pgsql/src/backend/utils/time: tqual.c (r1.61 -> r1.61.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/time/tqual.c.diff?r1=1.61&r2=1.61.2.1) ---(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: Repair very-low-probability race condition between relation
Log Message: --- Repair very-low-probability race condition between relation extension and VACUUM: in the interval between adding a new page to the relation and formatting it, it was possible for VACUUM to come along and decide it should format the page too. Though not harmful in itself, this would cause data loss if a third transaction were able to insert tuples into the vacuumed page before the original extender got control back. Modified Files: -- pgsql/src/backend/access/heap: hio.c (r1.55 -> r1.56) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/hio.c.diff?r1=1.55&r2=1.56) pgsql/src/backend/access/nbtree: nbtpage.c (r1.83 -> r1.84) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtpage.c.diff?r1=1.83&r2=1.84) nbtree.c (r1.128 -> r1.129) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.128&r2=1.129) pgsql/src/backend/commands: vacuumlazy.c (r1.52 -> r1.53) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.52&r2=1.53) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Repair very-low-probability race condition between relation
Log Message: --- Repair very-low-probability race condition between relation extension and VACUUM: in the interval between adding a new page to the relation and formatting it, it was possible for VACUUM to come along and decide it should format the page too. Though not harmful in itself, this would cause data loss if a third transaction were able to insert tuples into the vacuumed page before the original extender got control back. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/access/heap: hio.c (r1.50 -> r1.50.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/hio.c.diff?r1=1.50&r2=1.50.2.1) pgsql/src/backend/access/nbtree: nbtpage.c (r1.72 -> r1.72.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtpage.c.diff?r1=1.72&r2=1.72.2.1) nbtree.c (r1.106 -> r1.106.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.106&r2=1.106.2.1) pgsql/src/backend/commands: vacuumlazy.c (r1.32 -> r1.32.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.32&r2=1.32.2.1) ---(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: Repair very-low-probability race condition between relation
Log Message: --- Repair very-low-probability race condition between relation extension and VACUUM: in the interval between adding a new page to the relation and formatting it, it was possible for VACUUM to come along and decide it should format the page too. Though not harmful in itself, this would cause data loss if a third transaction were able to insert tuples into the vacuumed page before the original extender got control back. Tags: REL7_2_STABLE Modified Files: -- pgsql/src/backend/access/heap: hio.c (r1.43 -> r1.43.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/hio.c.diff?r1=1.43&r2=1.43.2.1) pgsql/src/backend/commands: vacuumlazy.c (r1.11 -> r1.11.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.11&r2=1.11.2.1) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Repair very-low-probability race condition between relation
Log Message: --- Repair very-low-probability race condition between relation extension and VACUUM: in the interval between adding a new page to the relation and formatting it, it was possible for VACUUM to come along and decide it should format the page too. Though not harmful in itself, this would cause data loss if a third transaction were able to insert tuples into the vacuumed page before the original extender got control back. Tags: REL7_3_STABLE Modified Files: -- pgsql/src/backend/access/heap: hio.c (r1.46 -> r1.46.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/hio.c.diff?r1=1.46&r2=1.46.2.1) pgsql/src/backend/commands: vacuumlazy.c (r1.20 -> r1.20.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.20&r2=1.20.2.1) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Repair very-low-probability race condition between relation
Log Message: --- Repair very-low-probability race condition between relation extension and VACUUM: in the interval between adding a new page to the relation and formatting it, it was possible for VACUUM to come along and decide it should format the page too. Though not harmful in itself, this would cause data loss if a third transaction were able to insert tuples into the vacuumed page before the original extender got control back. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/access/heap: hio.c (r1.54 -> r1.54.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/hio.c.diff?r1=1.54&r2=1.54.4.1) pgsql/src/backend/access/nbtree: nbtpage.c (r1.81 -> r1.81.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtpage.c.diff?r1=1.81&r2=1.81.4.1) nbtree.c (r1.124 -> r1.124.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.124&r2=1.124.4.1) pgsql/src/backend/commands: vacuumlazy.c (r1.50.4.1 -> r1.50.4.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.50.4.1&r2=1.50.4.2) ---(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: Documentation adjustments.
Log Message: --- Documentation adjustments. Vladimir Chukharev Modified Files: -- pgsql/doc/src/sgml: queries.sgml (r1.33 -> r1.34) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/queries.sgml.diff?r1=1.33&r2=1.34) pgsql/doc/src/sgml/ref: select.sgml (r1.86 -> r1.87) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select.sgml.diff?r1=1.86&r2=1.87) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Add encryption section to documentation.
Log Message: --- Add encryption section to documentation. Christopher Browne Modified Files: -- pgsql/doc/src/sgml: runtime.sgml (r1.315 -> r1.316) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml.diff?r1=1.315&r2=1.316) ---(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
