pgsql: Improve vacuum error context handling.

2020-06-30 Thread Amit Kapila
Improve vacuum error context handling. Use separate functions to save and restore error context information as that made code easier to understand.  Also, make it clear that the index information required for error context is sane. Author: Andres Freund, Justin Pryzby, Amit Kapila Backpatch-throu

pgsql: Improve vacuum error context handling.

2020-06-30 Thread Amit Kapila
Improve vacuum error context handling. Use separate functions to save and restore error context information as that made code easier to understand.  Also, make it clear that the index information required for error context is sane. Author: Andres Freund, Justin Pryzby, Amit Kapila Backpatch-throu

pgsql: Refactor creation of normal dependency records when creating ext

2020-06-30 Thread Michael Paquier
Refactor creation of normal dependency records when creating extension When creating an extension, the same type of dependency is used when registering a dependency to a schema and required extensions. This improves the code so as those dependencies are not recorded one-by-one, but grouped togeth

pgsql: Fix removal of files generated by TAP tests for SSL

2020-06-30 Thread Michael Paquier
Fix removal of files generated by TAP tests for SSL 001_ssltests.pl and 002_scram.pl both generated an extra file for a client key used in the tests that were not removed. In Debian, this causes repeated builds to fail. The code refactoring done in 4dc6355 broke the cleanup done in 001_ssltests.

pgsql: Fix removal of files generated by TAP tests for SSL

2020-06-30 Thread Michael Paquier
Fix removal of files generated by TAP tests for SSL 001_ssltests.pl and 002_scram.pl both generated an extra file for a client key used in the tests that were not removed. In Debian, this causes repeated builds to fail. The code refactoring done in 4dc6355 broke the cleanup done in 001_ssltests.

pgsql: Further adjustments to Hashagg EXPLAIN ANALYZE output

2020-06-30 Thread David Rowley
Further adjustments to Hashagg EXPLAIN ANALYZE output The "Disk Usage" and "HashAgg Batches" properties in the EXPLAIN ANALYZE output for HashAgg were previously only shown if the number of batches was greater than 0. Here we change this so that these properties are always shown for EXPLAIN ANALY

pgsql: Further adjustments to Hashagg EXPLAIN ANALYZE output

2020-06-30 Thread David Rowley
Further adjustments to Hashagg EXPLAIN ANALYZE output The "Disk Usage" and "HashAgg Batches" properties in the EXPLAIN ANALYZE output for HashAgg were previously only shown if the number of batches was greater than 0. Here we change this so that these properties are always shown for EXPLAIN ANALY

pgsql: Fix ecpg crash with bytea and cursor variables.

2020-06-30 Thread Michael Meskes
Fix ecpg crash with bytea and cursor variables. Author: Jehan-Guillaume de Rorthais Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/70dc45e8cb76e0c612648ccefc433b7fb2b16c2b Modified Files -- src/interfaces/ecpg/preproc/ecpg.header|

pgsql: Fix ecpg crash with bytea and cursor variables.

2020-06-30 Thread Michael Meskes
Fix ecpg crash with bytea and cursor variables. Author: Jehan-Guillaume de Rorthais Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/6425d6f6aa1af8b2db94ade64107fb268a7f114c Modified Files -- src/interfaces/ecpg/preproc/ecpg.header|

pgsql: Fix ecpg crash with bytea and cursor variables.

2020-06-30 Thread Michael Meskes
Fix ecpg crash with bytea and cursor variables. Author: Jehan-Guillaume de Rorthais Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e576f71fbe713d9357d1b480b4993043f7fcc73a Modified Files -- src/interfaces/ecpg/preproc/ecpg.header| 9 +- s

pgsql: doc: clarify that storage parameter values are optional

2020-06-30 Thread Bruce Momjian
doc: clarify that storage parameter values are optional In a few cases, the documented syntax specified storage parameter values as required. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5

pgsql: doc: clarify that storage parameter values are optional

2020-06-30 Thread Bruce Momjian
doc: clarify that storage parameter values are optional In a few cases, the documented syntax specified storage parameter values as required. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5

pgsql: doc: clarify that storage parameter values are optional

2020-06-30 Thread Bruce Momjian
doc: clarify that storage parameter values are optional In a few cases, the documented syntax specified storage parameter values as required. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5

pgsql: doc: clarify that storage parameter values are optional

2020-06-30 Thread Bruce Momjian
doc: clarify that storage parameter values are optional In a few cases, the documented syntax specified storage parameter values as required. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5

pgsql: doc: clarify that storage parameter values are optional

2020-06-30 Thread Bruce Momjian
doc: clarify that storage parameter values are optional In a few cases, the documented syntax specified storage parameter values as required. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5

pgsql: doc: clarify that storage parameter values are optional

2020-06-30 Thread Bruce Momjian
doc: clarify that storage parameter values are optional In a few cases, the documented syntax specified storage parameter values as required. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5

pgsql: doc: clarify that storage parameter values are optional

2020-06-30 Thread Bruce Momjian
doc: clarify that storage parameter values are optional In a few cases, the documented syntax specified storage parameter values as required. Reported-by: [email protected] Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5

pgsql: doc: change pg_upgrade wal_level to be not minimal

2020-06-30 Thread Bruce Momjian
doc: change pg_upgrade wal_level to be not minimal Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/2a06cb86dbacdf19a19d5bfd00d51

pgsql: doc: change pg_upgrade wal_level to be not minimal

2020-06-30 Thread Bruce Momjian
doc: change pg_upgrade wal_level to be not minimal Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d0a642fdc37066a4f29cd9

pgsql: doc: change pg_upgrade wal_level to be not minimal

2020-06-30 Thread Bruce Momjian
doc: change pg_upgrade wal_level to be not minimal Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/457942e18853f168f03c4b

pgsql: doc: change pg_upgrade wal_level to be not minimal

2020-06-30 Thread Bruce Momjian
doc: change pg_upgrade wal_level to be not minimal Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/35d5f698396043fbb252a9

pgsql: doc: change pg_upgrade wal_level to be not minimal

2020-06-30 Thread Bruce Momjian
doc: change pg_upgrade wal_level to be not minimal Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c7ff80ffaa933d26298ce2

pgsql: doc: change pg_upgrade wal_level to be not minimal

2020-06-30 Thread Bruce Momjian
doc: change pg_upgrade wal_level to be not minimal Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/41c0166317988d1eb0d8d4

pgsql: doc: change pg_upgrade wal_level to be not minimal

2020-06-30 Thread Bruce Momjian
doc: change pg_upgrade wal_level to be not minimal Previously it was specified to be only replica. Discussion: https://postgr.es/m/[email protected] Backpatch-through: 9.5 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1c76a141f32918dff4e1f5

pgsql: Add +(pg_lsn,numeric) and -(pg_lsn,numeric) operators.

2020-06-30 Thread Fujii Masao
Add +(pg_lsn,numeric) and -(pg_lsn,numeric) operators. By using these operators, the number of bytes can be added into and subtracted from LSN. Bump catalog version. Author: Fujii Masao Reviewed-by: Kyotaro Horiguchi, Michael Paquier, Asif Rehman Discussion: https://postgr.es/m/ed9f7f74-e996-67