Re: [GENERAL] pg_migrator not setting values of sequences? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [GENERAL] pg_migrator not setting values of sequences?
Date
Msg-id 15194.1247717712@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] pg_migrator not setting values of sequences?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [GENERAL] pg_migrator not setting values of sequences?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> The most effective solution might be to revert the change in pg_migrator
>> and instead have pg_dump interpret --binary-upgrade --schema-only to
>> include the data for sequences.  It seems ugly as sin though :-(

> Uh, how is this going to behave in 8.5?  Do we still dump sequences, and
> if so, aren't we heading down the road of dumping stuff only because a
> previous release needed it?

In 8.5 we'll probably have it go over to treating sequences the same as
other user tables.  What, do you think that'll be the only change
required in pg_migrator's behavior between 8.4 and 8.5?  I think it'll
more likely be down in the noise ...

> Can we run a query that just shifts columns around in the sequence heap
> files we migrated?

Nope.  That's not exposed at the SQL level, even if we allowed ALTER
TABLE on sequences (which I sure hope we don't).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] SE-PgSQL/lite rev.2163
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] pg_migrator not setting values of sequences?