pgsql: Fix unused-variable warning.

2018-11-04 Thread Tom Lane
Fix unused-variable warning. Discussion: https://postgr.es/m/CAMkU=1xthks6d0iptcwykhc1xrh3lbic_gzdo3jzdyru815...@mail.gmail.com Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/6f4e01c7d289ee39d08317f12ef979805bcbba00 Modified Files -- src/backen

pgsql: Fix unused-variable warning.

2018-11-04 Thread Tom Lane
Fix unused-variable warning. Discussion: https://postgr.es/m/CAMkU=1xthks6d0iptcwykhc1xrh3lbic_gzdo3jzdyru815...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3e0b05a75673f0ad73d5487efe814485a9fcf68f Modified Files -- src/backend/execu

pgsql: Fix bugs in plpgsql's handling of CALL argument lists.

2018-11-04 Thread Tom Lane
Fix bugs in plpgsql's handling of CALL argument lists. exec_stmt_call() tried to extract information out of a CALL statement's argument list without using expand_function_arguments(), apparently in the hope of saving a few nanoseconds by not processing defaulted arguments. It got that quite wrong

pgsql: Fix bugs in plpgsql's handling of CALL argument lists.

2018-11-04 Thread Tom Lane
Fix bugs in plpgsql's handling of CALL argument lists. exec_stmt_call() tried to extract information out of a CALL statement's argument list without using expand_function_arguments(), apparently in the hope of saving a few nanoseconds by not processing defaulted arguments. It got that quite wrong

pgsql: Fix ExecuteCallStmt to not scribble on the passed-in parse tree.

2018-11-04 Thread Tom Lane
Fix ExecuteCallStmt to not scribble on the passed-in parse tree. Modifying the parse tree at execution time is, or at least ought to be, verboten. It seems quite difficult to actually cause a crash this way in v11 (although you can exhibit it pretty easily in HEAD by messing with plan_cache_mode)

pgsql: Fix ExecuteCallStmt to not scribble on the passed-in parse tree.

2018-11-04 Thread Tom Lane
Fix ExecuteCallStmt to not scribble on the passed-in parse tree. Modifying the parse tree at execution time is, or at least ought to be, verboten. It seems quite difficult to actually cause a crash this way in v11 (although you can exhibit it pretty easily in HEAD by messing with plan_cache_mode)

pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.

2018-11-04 Thread Tom Lane
Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/fa534b411c86d2e7441852282ea9f1a491a090a6 Modified Files -- doc/src/sgml/release-10.sgml | 1318 + doc/sr

pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.

2018-11-04 Thread Tom Lane
Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/84010b9989d92bd7fb4a4b7c0e96dbe81ef101f4 Modified Files -- doc/src/sgml/release-10.sgml | 1322 -

pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.

2018-11-04 Thread Tom Lane
Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/89c563f1bbc0540e38d6c81680c4caa1bb20545b Modified Files -- doc/src/sgml/release-9.3.sgml | 466 ++

pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.

2018-11-04 Thread Tom Lane
Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1d00f275f1601ab6974123b8750a2487e630a185 Modified Files -- doc/src/sgml/release-9.3.sgml | 466 ++ doc/src/sgm

pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.

2018-11-04 Thread Tom Lane
Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/94c53b73a7f6a5cae1534c8aa6dbb4ea05c64e00 Modified Files -- doc/src/sgml/release-9.3.sgml | 466 + doc/src/sgml

pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.

2018-11-04 Thread Tom Lane
Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d7c3719298e631cfd73e385a031c86efc11ab726 Modified Files -- doc/src/sgml/release-10.sgml | 1322 -

pgsql: Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25.

2018-11-04 Thread Tom Lane
Release notes for 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, 9.3.25. Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/8bc709b37411ba7ad0fd0f1f79c354714424af3d Modified Files -- doc/src/sgml/release-9.3.sgml | 466 ++ doc

pgsql: Ignore partitioned tables when processing ON COMMIT DELETE ROWS

2018-11-04 Thread Michael Paquier
Ignore partitioned tables when processing ON COMMIT DELETE ROWS Those tables have no physical storage, making this option unusable with partition trees as at commit time an actual truncation was attempted. There are still issues with the way ON COMMIT actions are done when mixing several action ty

pgsql: Ignore partitioned tables when processing ON COMMIT DELETE ROWS

2018-11-04 Thread Michael Paquier
Ignore partitioned tables when processing ON COMMIT DELETE ROWS Those tables have no physical storage, making this option unusable with partition trees as at commit time an actual truncation was attempted. There are still issues with the way ON COMMIT actions are done when mixing several action ty

pgsql: Ignore partitioned tables when processing ON COMMIT DELETE ROWS

2018-11-04 Thread Michael Paquier
Ignore partitioned tables when processing ON COMMIT DELETE ROWS Those tables have no physical storage, making this option unusable with partition trees as at commit time an actual truncation was attempted. There are still issues with the way ON COMMIT actions are done when mixing several action ty

pgsql: Block creation of partitions with open references to its parent

2018-11-04 Thread Michael Paquier
Block creation of partitions with open references to its parent When a partition is created as part of a trigger processing, it is possible that the partition which just gets created changes the properties of the table the executor of the ongoing command relies on, causing a subsequent crash. Thi

pgsql: Block creation of partitions with open references to its parent

2018-11-04 Thread Michael Paquier
Block creation of partitions with open references to its parent When a partition is created as part of a trigger processing, it is possible that the partition which just gets created changes the properties of the table the executor of the ongoing command relies on, causing a subsequent crash. Thi

pgsql: Block creation of partitions with open references to its parent

2018-11-04 Thread Michael Paquier
Block creation of partitions with open references to its parent When a partition is created as part of a trigger processing, it is possible that the partition which just gets created changes the properties of the table the executor of the ongoing command relies on, causing a subsequent crash. Thi