[COMMITTERS] pgsql: Update doc text to reflect new column in MVCC phenomena table.

2016-05-25 Thread Kevin Grittner
Update doc text to reflect new column in MVCC phenomena table. Scott Wehrenberg Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/627e360358e3beb67cd2f54393835f979c5e30b7 Modified Files -- doc/src/sgml/mvcc.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 d

[COMMITTERS] pgsql: Fix broken error handling in parallel pg_dump/pg_restore.

2016-05-25 Thread Tom Lane
Fix broken error handling in parallel pg_dump/pg_restore. In the original design for parallel dump, worker processes reported errors by sending them up to the master process, which would print the messages. This is unworkably fragile for a couple of reasons: it risks deadlock if a worker sends an

[COMMITTERS] pgsql: Fix broken error handling in parallel pg_dump/pg_restore.

2016-05-25 Thread Tom Lane
Fix broken error handling in parallel pg_dump/pg_restore. In the original design for parallel dump, worker processes reported errors by sending them up to the master process, which would print the messages. This is unworkably fragile for a couple of reasons: it risks deadlock if a worker sends an

[COMMITTERS] pgsql: Fix broken error handling in parallel pg_dump/pg_restore.

2016-05-25 Thread Tom Lane
Fix broken error handling in parallel pg_dump/pg_restore. In the original design for parallel dump, worker processes reported errors by sending them up to the master process, which would print the messages. This is unworkably fragile for a couple of reasons: it risks deadlock if a worker sends an

[COMMITTERS] pgsql: Fix broken error handling in parallel pg_dump/pg_restore.

2016-05-25 Thread Tom Lane
Fix broken error handling in parallel pg_dump/pg_restore. In the original design for parallel dump, worker processes reported errors by sending them up to the master process, which would print the messages. This is unworkably fragile for a couple of reasons: it risks deadlock if a worker sends an

[COMMITTERS] pgsql: Ensure that backends see up-to-date statistics for shared catalo

2016-05-25 Thread Tom Lane
Ensure that backends see up-to-date statistics for shared catalogs. Ever since we split the statistics collector's reports into per-database files (commit 187492b6c2e8cafc), backends have been seeing stale statistics for shared catalogs. This is because the inquiry message only prompts the collec

[COMMITTERS] pgsql: Ensure that backends see up-to-date statistics for shared catalo

2016-05-25 Thread Tom Lane
Ensure that backends see up-to-date statistics for shared catalogs. Ever since we split the statistics collector's reports into per-database files (commit 187492b6c2e8cafc), backends have been seeing stale statistics for shared catalogs. This is because the inquiry message only prompts the collec

[COMMITTERS] pgsql: Ensure that backends see up-to-date statistics for shared catalo

2016-05-25 Thread Tom Lane
Ensure that backends see up-to-date statistics for shared catalogs. Ever since we split the statistics collector's reports into per-database files (commit 187492b6c2e8cafc), backends have been seeing stale statistics for shared catalogs. This is because the inquiry message only prompts the collec

[COMMITTERS] pgsql: Ensure that backends see up-to-date statistics for shared catalo

2016-05-25 Thread Tom Lane
Ensure that backends see up-to-date statistics for shared catalogs. Ever since we split the statistics collector's reports into per-database files (commit 187492b6c2e8cafc), backends have been seeing stale statistics for shared catalogs. This is because the inquiry message only prompts the collec

[COMMITTERS] pgsql: Remove option to write USING before opclass name in CREATE INDEX

2016-05-25 Thread Tom Lane
Remove option to write USING before opclass name in CREATE INDEX. Dating back to commit f10b63923, our grammar has allowed "USING" to optionally appear before an opclass name in CREATE INDEX (and, lately, some related places such as ON CONFLICT specifications). Nikolay Shaplov noticed that this s

[COMMITTERS] pgsql: Avoid hot standby cancels from VAC FREEZE

2016-05-25 Thread Alvaro Herrera
Avoid hot standby cancels from VAC FREEZE VACUUM FREEZE generated false cancelations of standby queries on an otherwise idle master. Caused by an off-by-one error on cutoff_xid which goes back to original commit. Analysis and report by Marco Nenciarini Bug fix by Simon Riggs This is a correct b

[COMMITTERS] pgsql: Avoid hot standby cancels from VAC FREEZE

2016-05-25 Thread Alvaro Herrera
Avoid hot standby cancels from VAC FREEZE VACUUM FREEZE generated false cancelations of standby queries on an otherwise idle master. Caused by an off-by-one error on cutoff_xid which goes back to original commit. Analysis and report by Marco Nenciarini Bug fix by Simon Riggs This is a correct b

[COMMITTERS] pgsql: Avoid hot standby cancels from VAC FREEZE

2016-05-25 Thread Alvaro Herrera
Avoid hot standby cancels from VAC FREEZE VACUUM FREEZE generated false cancelations of standby queries on an otherwise idle master. Caused by an off-by-one error on cutoff_xid which goes back to original commit. Analysis and report by Marco Nenciarini Bug fix by Simon Riggs This is a correct b

[COMMITTERS] pgsql: Avoid hot standby cancels from VAC FREEZE

2016-05-25 Thread Alvaro Herrera
Avoid hot standby cancels from VAC FREEZE VACUUM FREEZE generated false cancelations of standby queries on an otherwise idle master. Caused by an off-by-one error on cutoff_xid which goes back to original commit. Analysis and report by Marco Nenciarini Bug fix by Simon Riggs This is a correct b