pgsql: Make pg_dump error cleanly with -j against hot standby - Mailing list pgsql-committers

From Magnus Hagander
Subject pgsql: Make pg_dump error cleanly with -j against hot standby
Date
Msg-id E1b61np-0007gQ-Ec@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Make pg_dump error cleanly with -j against hot standby

Getting a synchronized snapshot is not supported on a hot standby node,
and is by default taken when using -j with multiple sessions. Trying to
do so still failed, but with a server error that would also go in the
log. Instead, proprely detect this case and give a better error message.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/d74048defcb1f48c5cc5a1b2a8aa0f7da8663394

Modified Files
--------------
src/bin/pg_dump/pg_backup.h    |  1 +
src/bin/pg_dump/pg_backup_db.c | 38 ++++++++++++++++++++++++++++++
src/bin/pg_dump/pg_backup_db.h |  1 +
src/bin/pg_dump/pg_dump.c      | 53 +++++++++++-------------------------------
4 files changed, 53 insertions(+), 40 deletions(-)


pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: pgsql: Make pg_dump error cleanly with -j against hot standby
Next
From: Tom Lane
Date:
Subject: pgsql: Be more predictable about reporting "lock timeout" vs "statement