aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-09-08 13:12:01 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-09-08 13:12:01 -0400
commit31eb14504de311c98db2d1306ac61427bcdad863 (patch)
tree52f4f09abdd0ba6eca7b7d2250a1f276dcc239af /src/backend/access/gist/gistproc.c
parenta88cee90fdfb2c125d56cb08164ca9a9ca39a75d (diff)
downloadpostgresql-31eb14504de311c98db2d1306ac61427bcdad863.tar.gz
postgresql-31eb14504de311c98db2d1306ac61427bcdad863.zip
Allow pg_dump to dump non-extension members of an extension-owned schema.
Previously, if a schema was created by an extension, a normal pg_dump run (not --binary-upgrade) would summarily skip every object in that schema. In a case where an extension creates a schema and then users create other objects within that schema, this does the wrong thing: we want pg_dump to skip the schema but still create the non-extension-owned objects. There's no easy way to fix this pre-9.6, because in earlier versions the "dump" status for a schema is just a bool and there's no way to distinguish "dump me" from "dump my members". However, as of 9.6 we do have enough state to represent that, so this is a simple correction of the logic in selectDumpableNamespace. In passing, make some cosmetic fixes in nearby code. Martín Marqués, reviewed by Michael Paquier Discussion: <99581032-71de-6466-c325-069861f1947d@2ndquadrant.com>
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions