Re: sequences and pg_upgrade

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: sequences and pg_upgrade
Date: 2016-09-23 18:06:54
Message-ID: 6a5bda7b-26f2-4ca3-5462-56de3c615331@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
v2-0001-pg_dump-Separate-table-and-sequence-data-object-t.patch invalid/octet-stream 6.0 KB
v2-0002-pg_upgrade-Upgrade-sequence-data-via-pg_dump.patch invalid/octet-stream 5.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-09-23 18:12:10 Re: pg_basebackup creates a corrupt file for pg_stat_tmp and pg_replslot on a backup location
Previous Message Breen Hagan 2016-09-23 17:55:14 Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled