Re: sequences and pg_upgrade - Mailing list pgsql-hackers

From Andres Freund
Subject Re: sequences and pg_upgrade
Date
Msg-id 20160830181520.7cxbap6kvneixgew@alap3.anarazel.de
Whole thread Raw
In response to sequences and pg_upgrade  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: sequences and pg_upgrade  (Anastasia Lubennikova <lubennikovaav@gmail.com>)
List pgsql-hackers
On 2016-08-30 08:46:48 -0400, Peter Eisentraut wrote:
> I was toying with a couple of ideas that would involve changing the
> storage of sequences.  (Say, for the sake of discussion, removing the
> problematic/useless sequence_name field.)

I'd be quite interested to know what changes that are...


> 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.

+1.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Pinning a buffer in TupleTableSlot is unnecessary
Next
From: Greg Stark
Date:
Subject: Re: Pinning a buffer in TupleTableSlot is unnecessary