From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Make pg_dump error cleanly with -j against hot standby |
Date: | 2016-05-26 20:22:45 |
Message-ID: | E1b61np-0007gR-Ef@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
------
REL9_5_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/47e59697679a0877e0525c565b1be437487604a7
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(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-05-27 14:40:39 | pgsql: Be more predictable about reporting "lock timeout" vs "statement |
Previous Message | Tom Lane | 2016-05-26 18:52:43 | pgsql: Disable physical tlist if any Var would need multiple sortgroupr |