| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sequences and pg_upgrade |
| Date: | 2016-08-30 15:26:59 |
| Message-ID: | 20160830152659.GB21961@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 30, 2016 at 08:46:48AM -0400, Peter Eisentraut wrote:
> I think the other solution mentioned in that thread would also work:
> Have pg_upgrade treat sequences more like system catalogs, whose format
> changes between major releases, and transferred them via the
> dump/restore route. So instead of copying the disk files, issue a
> setval call, and the sequence should be all set up.
>
> Am I missing anything?
Looks straight-forward to me.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-08-30 17:06:33 | Re: pageinspect: Hash index support |
| Previous Message | Tom Lane | 2016-08-30 15:10:46 | Re: GIN logging GIN_SEGMENT_UNMODIFIED actions? |