Re: sequences and pg_upgrade - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: sequences and pg_upgrade
Date
Msg-id 6a5bda7b-26f2-4ca3-5462-56de3c615331@2ndquadrant.com
Whole thread Raw
In response to Re: sequences and pg_upgrade  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
Responses Re: sequences and pg_upgrade  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
List pgsql-hackers
Here is an updated patch set.  Compared to the initial set, I have
changed pg_dump's sorting priorities so that sequence data is always
after table data.  This would otherwise have introduced a problem
because sortDataAndIndexObjectsBySize() only considers consecutive
DO_TABLE_DATA entries.  Also, I have removed the separate
--sequence-data switch from pg_dump and made it implicit in
--binary-upgrade.  (So the previous patches 0002 and 0003 have been
combined, because it's no longer a separate feature.)

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pg_upgrade vs user created range type extension
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location