aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-10-26 12:12:53 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2012-10-26 12:12:53 -0400
commit5110a96992e508b220a7a6ab303b0501c4237b4a (patch)
tree2e129b032a16480c86103c53aca7e68f54037747 /src/backend/access/gist/gistxlog.c
parentf01936f70b58dec8136399f6258b37d762c3cec3 (diff)
downloadpostgresql-5110a96992e508b220a7a6ab303b0501c4237b4a.tar.gz
postgresql-5110a96992e508b220a7a6ab303b0501c4237b4a.zip
In pg_dump, dump SEQUENCE SET items in the data not pre-data section.
Represent a sequence's current value as a separate TableDataInfo dumpable object, so that it can be dumped within the data section of the archive rather than in pre-data. This fixes an undesirable inconsistency between the meanings of "--data-only" and "--section=data", and also fixes dumping of sequences that are marked as extension configuration tables, as per a report from Marko Kreen back in July. The main cost is that we do one more SQL query per sequence, but that's probably not very meaningful in most databases. Back-patch to 9.1, since it has the extension configuration issue even though not the --section switch.
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions