diff options
| author | Kevin Grittner <kgrittn@postgresql.org> | 2013-11-30 11:33:54 -0600 |
|---|---|---|
| committer | Kevin Grittner <kgrittn@postgresql.org> | 2013-11-30 11:33:54 -0600 |
| commit | 27b33245a5f505794a0e8dd4cdb9342f8cf2cc0a (patch) | |
| tree | d5cc51032561749c391ed1ca23b4cd317e38bbf2 /src/backend/utils/adt/json.c | |
| parent | 8f8c666144226860d8d766054f6c8f3d78862e8b (diff) | |
| download | postgresql-27b33245a5f505794a0e8dd4cdb9342f8cf2cc0a.tar.gz postgresql-27b33245a5f505794a0e8dd4cdb9342f8cf2cc0a.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/utils/adt/json.c')
0 files changed, 0 insertions, 0 deletions