[COMMITTERS] pgsql: Fix name of syslog_ident GUC in docs.

2014-03-07 Thread Heikki Linnakangas
Fix name of syslog_ident GUC in docs. Michael Paquier Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/6f529325ad269fe5f76160779d1d41799c6524c9 Modified Files -- doc/src/sgml/config.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --

[COMMITTERS] pgsql: Fix name of syslog_ident GUC in docs.

2014-03-07 Thread Heikki Linnakangas
Fix name of syslog_ident GUC in docs. Michael Paquier Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/fb61ff85e16636e82fa6ad01f8e106b14b84844f Modified Files -- doc/src/sgml/config.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --

[COMMITTERS] pgsql: Fix name of syslog_ident GUC in docs.

2014-03-07 Thread Heikki Linnakangas
Fix name of syslog_ident GUC in docs. Michael Paquier Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ff2e0e1f96ae412d06d0d10551161ca027d897fd Modified Files -- doc/src/sgml/config.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --

[COMMITTERS] pgsql: Fix typo in comment.

2014-03-07 Thread Heikki Linnakangas
Fix typo in comment. Forgot to "git add" it earlier. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ec3cb1ca2a07abb1f26033f124df438ca816be6f Modified Files -- src/backend/replication/walsender.c |2 +- 1 file changed, 1 insertion(+), 1 deletio

[COMMITTERS] pgsql: Fix name of syslog_ident GUC in docs.

2014-03-07 Thread Heikki Linnakangas
Fix name of syslog_ident GUC in docs. Michael Paquier Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/762c1436822304e8acbe79f32e05f852d653431f Modified Files -- doc/src/sgml/config.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --

[COMMITTERS] pgsql: Fix name of syslog_ident GUC in docs.

2014-03-07 Thread Heikki Linnakangas
Fix name of syslog_ident GUC in docs. Michael Paquier Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/2b8483d69d1be9700abae0dc7c48c5b7edb77498 Modified Files -- doc/src/sgml/config.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent v

[COMMITTERS] pgsql: Fix name of syslog_ident GUC in docs.

2014-03-07 Thread Heikki Linnakangas
Fix name of syslog_ident GUC in docs. Michael Paquier Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/886c4ebfa3d935ff031f668b845a7c2463fd9acd Modified Files -- doc/src/sgml/config.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --

[COMMITTERS] pgsql: Avoid memcpy() with same source and destination address.

2014-03-07 Thread Heikki Linnakangas
Avoid memcpy() with same source and destination address. The behavior of that is undefined, although unlikely to lead to problems in practice. Found by running regression tests with Valgrind. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/c7a186e392d4654148a

[COMMITTERS] pgsql: Avoid memcpy() with same source and destination address.

2014-03-07 Thread Heikki Linnakangas
Avoid memcpy() with same source and destination address. The behavior of that is undefined, although unlikely to lead to problems in practice. Found by running regression tests with Valgrind. Branch -- REL8_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/ff9d757c67786b389f1

[COMMITTERS] pgsql: Fix dangling smgr_owner pointer when a fake relcache entry is fr

2014-03-07 Thread Heikki Linnakangas
Fix dangling smgr_owner pointer when a fake relcache entry is freed. A fake relcache entry can "own" a SmgrRelation object, like a regular relcache entry. But when it was free'd, the owner field in SmgrRelation was not cleared, so it was left pointing to free'd memory. Amazingly this apparently h

[COMMITTERS] pgsql: Fix dangling smgr_owner pointer when a fake relcache entry is fr

2014-03-07 Thread Heikki Linnakangas
Fix dangling smgr_owner pointer when a fake relcache entry is freed. A fake relcache entry can "own" a SmgrRelation object, like a regular relcache entry. But when it was free'd, the owner field in SmgrRelation was not cleared, so it was left pointing to free'd memory. Amazingly this apparently h

[COMMITTERS] pgsql: Avoid memcpy() with same source and destination address.

2014-03-07 Thread Heikki Linnakangas
Avoid memcpy() with same source and destination address. The behavior of that is undefined, although unlikely to lead to problems in practice. Found by running regression tests with Valgrind. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/8332fe76b559dd7d0a6

[COMMITTERS] pgsql: Avoid memcpy() with same source and destination address.

2014-03-07 Thread Heikki Linnakangas
Avoid memcpy() with same source and destination address. The behavior of that is undefined, although unlikely to lead to problems in practice. Found by running regression tests with Valgrind. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/d8f2858b884c4b9c77a

[COMMITTERS] pgsql: Avoid memcpy() with same source and destination address.

2014-03-07 Thread Heikki Linnakangas
Avoid memcpy() with same source and destination address. The behavior of that is undefined, although unlikely to lead to problems in practice. Found by running regression tests with Valgrind. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/4afc3f0faa3b1f86c23

[COMMITTERS] pgsql: Fix dangling smgr_owner pointer when a fake relcache entry is fr

2014-03-07 Thread Heikki Linnakangas
Fix dangling smgr_owner pointer when a fake relcache entry is freed. A fake relcache entry can "own" a SmgrRelation object, like a regular relcache entry. But when it was free'd, the owner field in SmgrRelation was not cleared, so it was left pointing to free'd memory. Amazingly this apparently h

[COMMITTERS] pgsql: Fix dangling smgr_owner pointer when a fake relcache entry is fr

2014-03-07 Thread Heikki Linnakangas
Fix dangling smgr_owner pointer when a fake relcache entry is freed. A fake relcache entry can "own" a SmgrRelation object, like a regular relcache entry. But when it was free'd, the owner field in SmgrRelation was not cleared, so it was left pointing to free'd memory. Amazingly this apparently h

[COMMITTERS] pgsql: Fix dangling smgr_owner pointer when a fake relcache entry is fr

2014-03-07 Thread Heikki Linnakangas
Fix dangling smgr_owner pointer when a fake relcache entry is freed. A fake relcache entry can "own" a SmgrRelation object, like a regular relcache entry. But when it was free'd, the owner field in SmgrRelation was not cleared, so it was left pointing to free'd memory. Amazingly this apparently h

[COMMITTERS] pgsql: Avoid memcpy() with same source and destination address.

2014-03-07 Thread Heikki Linnakangas
Avoid memcpy() with same source and destination address. The behavior of that is undefined, although unlikely to lead to problems in practice. Found by running regression tests with Valgrind. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/ad7b48ea08d6c33bae0a33c5f2

[COMMITTERS] pgsql: Fix dangling smgr_owner pointer when a fake relcache entry is fr

2014-03-07 Thread Heikki Linnakangas
Fix dangling smgr_owner pointer when a fake relcache entry is freed. A fake relcache entry can "own" a SmgrRelation object, like a regular relcache entry. But when it was free'd, the owner field in SmgrRelation was not cleared, so it was left pointing to free'd memory. Amazingly this apparently h

[COMMITTERS] pgsql: fix ReplicationSlotsCountDBSlots for dropping unrelated database

2014-03-07 Thread Bruce Momjian
fix ReplicationSlotsCountDBSlots for dropping unrelated databases YAMAMOTO Takashi Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/91d9de97518b26a1e0d601b2c1580f5225030e56 Modified Files -- src/backend/replication/slot.c |1 + 1 file changed, 1 insert

[COMMITTERS] pgsql: release notes: add item missed in 9.2.5 release

2014-03-07 Thread Bruce Momjian
release notes: add item missed in 9.2.5 release Item is "Prevent errors in WAL replay due to references to uninitialized empty pages". Report and text by Andres Freund Backpatch through 9.2. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/2570d936ff2e03cc4e

[COMMITTERS] pgsql: release notes: add item missed in 9.2.5 release

2014-03-07 Thread Bruce Momjian
release notes: add item missed in 9.2.5 release Item is "Prevent errors in WAL replay due to references to uninitialized empty pages". Report and text by Andres Freund Backpatch through 9.2. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4ea2e2d47449dac509327c2c0

[COMMITTERS] pgsql: release notes: add item missed in 9.2.5 release

2014-03-07 Thread Bruce Momjian
release notes: add item missed in 9.2.5 release Item is "Prevent errors in WAL replay due to references to uninitialized empty pages". Report and text by Andres Freund Backpatch through 9.2. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/28d92026f0855061ac

Re: [COMMITTERS] pgsql: Ensure that XLOG_HEAP2_VISIBLE always targets an initialized pag

2014-03-07 Thread Bruce Momjian
On Fri, Nov 22, 2013 at 08:04:07PM +0100, Stefan Kaltenbrunner wrote: > On 11/18/2013 10:40 PM, Andres Freund wrote: > > On 2013-11-18 16:33:25 -0500, Bruce Momjian wrote: > >> On Sun, Nov 10, 2013 at 11:51:06PM +0100, Andres Freund wrote: > >>> Hi, > >>> > >>> On 2013-06-06 14:22:12 +, Robert

[COMMITTERS] pgsql: Fix contrib/postgres_fdw to handle multiple join conditions prop

2014-03-07 Thread Tom Lane
Fix contrib/postgres_fdw to handle multiple join conditions properly. The previous coding supposed that it could consider just a single join condition in any one parameterized path for the foreign table. But in reality, the parameterized-path machinery forces all join clauses that are "movable to

[COMMITTERS] pgsql: Fix contrib/postgres_fdw to handle multiple join conditions prop

2014-03-07 Thread Tom Lane
Fix contrib/postgres_fdw to handle multiple join conditions properly. The previous coding supposed that it could consider just a single join condition in any one parameterized path for the foreign table. But in reality, the parameterized-path machinery forces all join clauses that are "movable to

[COMMITTERS] pgsql: Remove unportable use of anonymous unions from reorderbuffer.h.

2014-03-07 Thread Tom Lane
Remove unportable use of anonymous unions from reorderbuffer.h. In b89e151054a I had assumed it was ok to use anonymous unions as struct members, but while a longstanding extension in many compilers, it's only been standardized in C11. To fix, remove one of the anonymous unions which tried to hid

[COMMITTERS] pgsql: docs: improve TABLE command by showing supported clauses

2014-03-07 Thread Bruce Momjian
docs: improve TABLE command by showing supported clauses Initial patch by Colin 't Hart Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/b0cb40f93a85fd15e930828d9336e9f999ca3224 Modified Files -- doc/src/sgml/ref/select.sgml | 11 --- 1 file cha

[COMMITTERS] pgsql: doc: improve server's keepalive description

2014-03-07 Thread Bruce Momjian
doc: improve server's keepalive description Use superior libpq keepalive description for the server-level parameters. Per report by Tatsuo Ishii and Marko Tiikkaja Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/ea43af38dc90d1656e67d7fbdbc809385c380435 Modified Fil

[COMMITTERS] pgsql: pg_upgrade: document delete problems with tablespaces inside the

2014-03-07 Thread Bruce Momjian
pg_upgrade: document delete problems with tablespaces inside the cluster directory Per report by Marc Mamin Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8879fa09ee7aa6232097198b66c3376184b0de06 Modified Files -- doc/src/sgml/pgupgrade.sgml |3 ++-