[COMMITTERS] pgsql: Document the "replication" option in StartupMessage.

2017-04-10 Thread Heikki Linnakangas
Document the "replication" option in StartupMessage. It is documented in the Streaming Replication Protocol section, but was missing from the list of options in StartupMessage description. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6c4ad8b7bf420a6f598e4b45560cff

[COMMITTERS] pgsql: Fix indentation.

2017-04-10 Thread Heikki Linnakangas
Fix indentation. Oops, I forgot to "git add" this to previous commit. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9cf5c31964315181e475fc37a5e9ad2204fe3484 Modified Files -- doc/src/sgml/protocol.sgml | 13 +++-- 1 file changed, 7 insertions(+)

[COMMITTERS] pgsql: Move isolationtester's is-blocked query into C code for speed.

2017-04-10 Thread Tom Lane
Move isolationtester's is-blocked query into C code for speed. Commit 4deb41381 modified isolationtester's query to see whether a session is blocked to also check for waits occurring in GetSafeSnapshot. However, it did that in a way that enormously increased the query's runtime under CLOBBER_CACHE

[COMMITTERS] pgsql: Fix whitespace

2017-04-10 Thread Peter Eisentraut
Fix whitespace Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/244f1c89070c1a661623bf1eaddf1307f8f598a3 Modified Files -- contrib/sepgsql/expected/dml.out | 4 ++-- contrib/sepgsql/sql/dml.sql | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)

[COMMITTERS] pgsql: Fix reporting of violations in ExecConstraints, again.

2017-04-10 Thread Robert Haas
Fix reporting of violations in ExecConstraints, again. We decided in f1b4c771ea74f42447dccaed42ffcdcccf3aa694 to pass the original slot to ExecConstraints(), but that breaks when there are BEFORE ROW triggers involved. So we need to do reverse-map the tuples back to the original descriptor instea

[COMMITTERS] pgsql: Fix typo in comment

2017-04-10 Thread Peter Eisentraut
Fix typo in comment Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/56dd8e85c40fef3e3c2c10afa186ee30416ec507 Modified Files -- src/backend/replication/logical/tablesync.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers

[COMMITTERS] pgsql: Support configuration reload in logical replication workers

2017-04-10 Thread Peter Eisentraut
Support configuration reload in logical replication workers Author: Michael Paquier Reviewed-by: Petr Jelinek Reported-by: Fujii Masao Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/26ad194cb0a6b955e155d44fb52a74212ce85759 Modified Files -- src/backe

[COMMITTERS] pgsql: Improve castNode notation by introducing list-extraction-specifi

2017-04-10 Thread Tom Lane
Improve castNode notation by introducing list-extraction-specific variants. This extends the castNode() notation introduced by commit 5bcab1114 to provide, in one step, extraction of a list cell's pointer and coercion to a concrete node type. For example, "lfirst_node(Foo, lc)" is the same as "ca

[COMMITTERS] pgsql: Improve castNode notation by introducing list-extraction-specifi

2017-04-10 Thread Tom Lane
Improve castNode notation by introducing list-extraction-specific variants. This extends the castNode() notation introduced by commit 5bcab1114 to provide, in one step, extraction of a list cell's pointer and coercion to a concrete node type. For example, "lfirst_node(Foo, lc)" is the same as "ca

[COMMITTERS] pgsql: Improve castNode notation by introducing list-extraction-specifi

2017-04-10 Thread Tom Lane
Improve castNode notation by introducing list-extraction-specific variants. This extends the castNode() notation introduced by commit 5bcab1114 to provide, in one step, extraction of a list cell's pointer and coercion to a concrete node type. For example, "lfirst_node(Foo, lc)" is the same as "ca

[COMMITTERS] pgsql: Improve castNode notation by introducing list-extraction-specifi

2017-04-10 Thread Tom Lane
Improve castNode notation by introducing list-extraction-specific variants. This extends the castNode() notation introduced by commit 5bcab1114 to provide, in one step, extraction of a list cell's pointer and coercion to a concrete node type. For example, "lfirst_node(Foo, lc)" is the same as "ca

[COMMITTERS] pgsql: Improve castNode notation by introducing list-extraction-specifi

2017-04-10 Thread Tom Lane
Improve castNode notation by introducing list-extraction-specific variants. This extends the castNode() notation introduced by commit 5bcab1114 to provide, in one step, extraction of a list cell's pointer and coercion to a concrete node type. For example, "lfirst_node(Foo, lc)" is the same as "ca

[COMMITTERS] pgsql: Improve castNode notation by introducing list-extraction-specifi

2017-04-10 Thread Tom Lane
Improve castNode notation by introducing list-extraction-specific variants. This extends the castNode() notation introduced by commit 5bcab1114 to provide, in one step, extraction of a list cell's pointer and coercion to a concrete node type. For example, "lfirst_node(Foo, lc)" is the same as "ca

[COMMITTERS] pgsql: Fix initialization of dsa.c free area counter.

2017-04-10 Thread Andres Freund
Fix initialization of dsa.c free area counter. The backend local copy of dsa_area_control->freed_segment_counter was not properly initialized / maintained. This could, if unlucky, lead to keeping attached to a segment for too long. Found via valgrind bleat on buildfarm animal skink. Author: Tho

[COMMITTERS] pgsql: Use weaker locks when updating pg_subscription_rel

2017-04-10 Thread Peter Eisentraut
Use weaker locks when updating pg_subscription_rel The previously used ShareRowExclusiveLock, while technically probably more correct, led to deadlocks during seemingly unrelated operations and thus a poor experience. Use RowExclusiveLock, like for most similar catalog operations. In some care c

[COMMITTERS] pgsql: Run most pg_dump and pg_dumpall tests with --no-sync

2017-04-10 Thread Andrew Dunstan
Run most pg_dump and pg_dumpall tests with --no-sync Commit 96a7128b made pg_dump and pg_dumpall sync their output by default. However, there's no great need for that in testing, and it could impose a performance penalty, so we add the --no-sync flag to most of the test cases. Michael Paquier Br