pgsql: pg_upgrade: Upgrade sequence data via pg_dump - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: pg_upgrade: Upgrade sequence data via pg_dump
Date
Msg-id E1c67Lu-0001Lz-JH@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
pg_upgrade: Upgrade sequence data via pg_dump

Previously, pg_upgrade migrated sequence data like tables by copying the
on-disk file.  This does not allow any changes in the on-disk format for
sequences.  It's simpler to just have pg_dump set the new sequence
values as it normally does.  To do that, create a hidden submode in
pg_dump that dumps sequence data even when a schema-only dump is
requested, and trigger that submode in binary upgrade mode.  (This new
submode could easily be exposed as a command-line option, but it has
limited use outside of pg_dump and would probably cause some confusion,
so we don't do that at this time.)

Reviewed-by: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>
Reviewed-by: Michael Paquier <michael.paquier@gmail.com>

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/a7e5457db86642c078888bf666cf6b64636bb190

Modified Files
--------------
src/bin/pg_dump/pg_backup.h          |  3 +++
src/bin/pg_dump/pg_backup_archiver.c |  6 +++++-
src/bin/pg_dump/pg_dump.c            | 19 +++++++++++++++----
src/bin/pg_upgrade/info.c            |  2 +-
4 files changed, 24 insertions(+), 6 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Doc: remove obsolete example.
Next
From: Peter Eisentraut
Date:
Subject: pgsql: pg_dump: Separate table and sequence data object types