diff options
| author | Kevin Grittner <kgrittn@postgresql.org> | 2013-11-30 12:06:48 -0600 |
|---|---|---|
| committer | Kevin Grittner <kgrittn@postgresql.org> | 2013-11-30 12:06:48 -0600 |
| commit | 4bdccd8427718f9c468e5e03286252f37ea771b5 (patch) | |
| tree | 89c2126765c214ab880bb40d09d43aabe09adb9e /src/backend/tcop/postgres.c | |
| parent | 9f1e051adefb2f29e757cf426b03db20d3f8a26d (diff) | |
| download | postgresql-4bdccd8427718f9c468e5e03286252f37ea771b5.tar.gz postgresql-4bdccd8427718f9c468e5e03286252f37ea771b5.zip | |
Fix pg_dumpall to work for databases flagged as read-only.
pg_dumpall's charter is to be able to recreate a database cluster's
contents in a virgin installation, but it was failing to honor that
contract if the cluster had any ALTER DATABASE SET
default_transaction_read_only settings. By including a SET command
for the connection for each connection opened by pg_dumpall output,
errors are avoided and the source cluster is successfully
recreated.
There was discussion of whether to also set this for the connection
applying pg_dump output, but it was felt that it was both less
appropriate in that context, and far easier to work around.
Backpatch to all supported branches.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions