Re: pg_dump and sequences - RFC - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump and sequences - RFC
Date
Msg-id 26047.970154256@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump and sequences - RFC  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: pg_dump and sequences - RFC
List pgsql-hackers
Philip Warner <pjw@rhyme.com.au> writes:
> At 11:01 28/09/00 -0400, Tom Lane wrote:
>> A data-only reload
>> would fail to make that guarantee unless you drop and recreate
>> the sequence.

> Will this cause problems in an existing database because the sequence OID
> changes?

Hmm, good point.  There isn't any real easy way to refer to a sequence
by OID --- the sequence functions only accept names --- but I suppose
someone out there might be doing something with sequence OIDs.

Perhaps the real answer is to extend the set of sequence functions so
that it's possible to set/clear is_called directly.  Perhaps a variant
setval() with an additional, boolean argument?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: sys_nerr, sys_errlist
Next
From: Philip Warner
Date:
Subject: Re: pg_dump and sequences - RFC