| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pg_dump --sequence-data option |
| Date: | 2017-03-24 03:46:36 |
| Message-ID: | 87915366-4c1c-3c95-4043-b3f7ef57dd0b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At the conclusion of
<f6ed028e-ac25-e849-aec6-8d69416f0090(at)2ndquadrant(dot)com>, pg_upgrade was
changed to upgrade sequences "logically". We initially did that by
adding a pg_dump option --sequence-data that would dump sequence data
(setval calls) in spite of --schema-only. Later, that option was
removed as a separate option and made automatic in --binary-upgrade,
because we didn't think it was useful independently.
For logical replication, sequence data is not replicated at the moment.
So it could be useful in some cases to have a simple way to dump just
the sequence data. So I think it would be worth adding that option back.
Comments?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-03-24 03:51:16 | Re: pageinspect and hash indexes |
| Previous Message | Peter Eisentraut | 2017-03-24 03:28:47 | Re: Allow pg_dumpall to work without pg_authid |