aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-09-08 10:48:03 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-09-08 10:48:03 -0400
commita88cee90fdfb2c125d56cb08164ca9a9ca39a75d (patch)
tree4cf02fd0626cf16e9609b4e486e13febe5dd2bca /src/backend/access/gist/gist.c
parentd7c45172a673be1fc9e51e98e45a44c14d1ee78d (diff)
downloadpostgresql-a88cee90fdfb2c125d56cb08164ca9a9ca39a75d.tar.gz
postgresql-a88cee90fdfb2c125d56cb08164ca9a9ca39a75d.zip
Don't print database's tablespace in pg_dump -C --no-tablespaces output.
If the database has a non-default tablespace, we emitted a TABLESPACE clause in the CREATE DATABASE command emitted by -C, even if --no-tablespaces was also specified. This seems wrong, and it's inconsistent with what pg_dumpall does, so change it. Per bug #14315 from Danylo Hlynskyi. Back-patch to 9.5. The bug is much older, but it'd be a more invasive change before 9.5 because dumpDatabase() hasn't got an easy way to get to the outputNoTablespaces flag. Doesn't seem worth the work given the lack of previous complaints. Report: <20160908081953.1402.75347@wrigleys.postgresql.org>
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions