diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-10-26 12:12:42 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-10-26 12:12:42 -0400 |
| commit | 5a39114fe7d19280f6477ce1eb0d88beafda13a4 (patch) | |
| tree | 693285e7246c494af261d47b02232d574c10a27e /src/backend/executor/nodeModifyTable.c | |
| parent | bf01e34b556ff37982ba2d882db424aa484c0d07 (diff) | |
| download | postgresql-5a39114fe7d19280f6477ce1eb0d88beafda13a4.tar.gz postgresql-5a39114fe7d19280f6477ce1eb0d88beafda13a4.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/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions