[COMMITTERS] pgsql: Repair out-of-date information in src/backend/storage/buffer/REA

Repair out-of-date information in src/backend/storage/buffer/README. In commit d526575f893c1a4e05ebd307e80203536b213a6d, we changed things so that buffer usage counts are incremented when the buffer is pinned, rather than when it is unpinned, but the README file didn't get the memo. Report by Ami

[COMMITTERS] pgsql: Prevent pg_basebackup when integer_datetimes flag doesn't match.

Prevent pg_basebackup when integer_datetimes flag doesn't match. Magnus Hagander, reviewed by Fujii Masao, with slight wording changes by me. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/304aa339b20df9f9ba6f4d93175e05098f6fd1c1 Modified Files -- src/b

[COMMITTERS] pgsql: Release note improvements.

Release note improvements. Document some more things as incompatibilities, and improve wording of another item. Noah Misch Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/b536458e73a8d9294817228f06961913f6faa551 Modified Files -- doc/src/sgml/release-9.

[COMMITTERS] pgsql: Fix error message for COMMENT/SECURITY LABEL ON COLUMN xxx IS 'y

Fix error message for COMMENT/SECURITY LABEL ON COLUMN xxx IS 'yyy' When the column name is an unqualified name, rather than table.column, the error message complains about too many dotted names, which is wrong. Report by Peter Eisentraut based on examination of the sepgsql regression test output

[COMMITTERS] pgsql: Fix error message for COMMENT/SECURITY LABEL ON COLUMN xxx IS 'y

Fix error message for COMMENT/SECURITY LABEL ON COLUMN xxx IS 'yyy' When the column name is an unqualified name, rather than table.column, the error message complains about too many dotted names, which is wrong. Report by Peter Eisentraut based on examination of the sepgsql regression test output

[COMMITTERS] pgsql: Remove reviewers from 9.2 release notes; improve attributions.

Remove reviewers from 9.2 release notes; improve attributions. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8a46e25189b428e1ff8af5ba19c6f32287277575 Modified Files -- doc/src/sgml/release-9.2.sgml | 231 +++-- 1 fil

[COMMITTERS] pgsql: 9.2 release notes: GiST index improvements are for all geometri

9.2 release notes: GiST index improvements are for all geometric index types, per Alexander Korotkov Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/007522e6b4c32d7ae67a2ff7f568eb2f0bd257f6 Modified Files -- doc/src/sgml/release-9.2.sgml |2 +- 1 file

[COMMITTERS] pgsql: Fix reindexdb manual page to say --maintenance-db controls what

Fix reindexdb manual page to say --maintenance-db controls what is reindexed, not vacuumed (typo). Per report from Thomas REISS Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/e6b7170c33b4795cc519137528523bd3c4933edb Modified Files -- doc/src/sgml/ref/re

[COMMITTERS] pgsql: Fix markup for HISTORY generation.

Fix markup for HISTORY generation. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/0013a665b75a62f6110bff99273b1015b4aa60fe Modified Files -- doc/src/sgml/release-9.2.sgml |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-c

[COMMITTERS] pgsql: Add small example about pg_archivecleanup -x option

Add small example about pg_archivecleanup -x option Every time I read this I had doubts about whether the argument to the -x option should include the dot (yes). A small example should clarify this. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/92a953fbf8c90c3b316

[COMMITTERS] pgsql: Ensure that seqscans check for interrupts at least once per page

Ensure that seqscans check for interrupts at least once per page. If a seqscan encounters many consecutive pages containing only dead tuples, it can remain in the loop in heapgettup for a long time, and there was no CHECK_FOR_INTERRUPTS anywhere in that loop. This meant there were real-world situ

[COMMITTERS] pgsql: Ensure that seqscans check for interrupts at least once per page

Ensure that seqscans check for interrupts at least once per page. If a seqscan encounters many consecutive pages containing only dead tuples, it can remain in the loop in heapgettup for a long time, and there was no CHECK_FOR_INTERRUPTS anywhere in that loop. This meant there were real-world situ

[COMMITTERS] pgsql: Ensure that seqscans check for interrupts at least once per page

Ensure that seqscans check for interrupts at least once per page. If a seqscan encounters many consecutive pages containing only dead tuples, it can remain in the loop in heapgettup for a long time, and there was no CHECK_FOR_INTERRUPTS anywhere in that loop. This meant there were real-world situ

[COMMITTERS] pgsql: Ensure that seqscans check for interrupts at least once per page

Ensure that seqscans check for interrupts at least once per page. If a seqscan encounters many consecutive pages containing only dead tuples, it can remain in the loop in heapgettup for a long time, and there was no CHECK_FOR_INTERRUPTS anywhere in that loop. This meant there were real-world situ

[COMMITTERS] pgsql: Ensure that seqscans check for interrupts at least once per page

Ensure that seqscans check for interrupts at least once per page. If a seqscan encounters many consecutive pages containing only dead tuples, it can remain in the loop in heapgettup for a long time, and there was no CHECK_FOR_INTERRUPTS anywhere in that loop. This meant there were real-world situ

[COMMITTERS] pgsql: Add 9.2 release note authorship mentions for Heikki and Alexande

Add 9.2 release note authorship mentions for Heikki and Alexander Korotkov, per Alexander Korotkov. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/b9c895ee6f336084048f4c8cc76b81afb4535e58 Modified Files -- doc/src/sgml/release-9.2.sgml |5 +++-- 1 fil