aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorKevin Grittner <kgrittn@postgresql.org>2013-11-30 11:24:56 -0600
committerKevin Grittner <kgrittn@postgresql.org>2013-11-30 11:24:56 -0600
commit4bd371f6f886446b6c0886f088992e6f3d4ab4a2 (patch)
tree37808842e87b5552235b0cf144447887a60ddb0e /src/backend/access/gist/gist.c
parent34fa72ec9cfc1f5c4b11b67b2ce7eac6caca9fa5 (diff)
downloadpostgresql-4bd371f6f886446b6c0886f088992e6f3d4ab4a2.tar.gz
postgresql-4bd371f6f886446b6c0886f088992e6f3d4ab4a2.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/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions