[COMMITTERS] pgsql: Fix typo

2017-10-30 Thread Magnus Hagander
Fix typo Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/0f1fbe7122208f4734dcb285594d06e7ebd07b10 Modified Files -- doc/src/sgml/charset.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list

[COMMITTERS] pgsql: Fix typo

2017-10-30 Thread Magnus Hagander
Fix typo Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/77954f996cdb31ead2718aa3a9b4878da382e385 Modified Files -- doc/src/sgml/charset.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list

[COMMITTERS] pgsql: Fix typo in comment

2017-10-30 Thread Magnus Hagander
Fix typo in comment Etsuro Fujita Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/854b643c8eb476ab957d83d562c8bfa10586d123 Modified Files -- src/backend/catalog/partition.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via

[COMMITTERS] pgsql: Fix autovacuum work item error handling

2017-10-30 Thread Alvaro Herrera
Fix autovacuum work item error handling In autovacuum's "work item" processing, a few strings were allocated in the current transaction's memory context, which goes away during error handling; if an error happened during execution of the work item, the pfree() calls to clean up afterwards would

[COMMITTERS] pgsql: Fix autovacuum work item error handling

2017-10-30 Thread Alvaro Herrera
Fix autovacuum work item error handling In autovacuum's "work item" processing, a few strings were allocated in the current transaction's memory context, which goes away during error handling; if an error happened during execution of the work item, the pfree() calls to clean up afterwards would

[COMMITTERS] pgsql: Add sanity check for pg_proc.provariadic

2017-10-30 Thread Robert Haas
Add sanity check for pg_proc.provariadic Check that the values from pg_proc.h match what ProcedureCreate would have done. Robert Haas and Amul Sul Discussion: http://postgr.es/m/ca+tgmoz_ugxfq5ygeddmdusj4j_vx7nfnjc6mfy6bgoj3qz...@mail.gmail.com Branch -- master Details ---

[COMMITTERS] pgsql: Doc: call out UPDATE syntax change as a v10 compatibility issue.

2017-10-30 Thread Tom Lane
Doc: call out UPDATE syntax change as a v10 compatibility issue. The change made by commit 906bfcad7 means that if you're writing a parenthesized column list in UPDATE ... SET, but that column list is only one column, you now need to write ROW(expression) on the righthand side, not just a

[COMMITTERS] pgsql: Doc: call out UPDATE syntax change as a v10 compatibility issue.

2017-10-30 Thread Tom Lane
Doc: call out UPDATE syntax change as a v10 compatibility issue. The change made by commit 906bfcad7 means that if you're writing a parenthesized column list in UPDATE ... SET, but that column list is only one column, you now need to write ROW(expression) on the righthand side, not just a