Skip site navigation (1) Skip section navigation (2)

Re: pg_dump and sequences - RFC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump and sequences - RFC
Date: 2000-09-28 15:17:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Philip Warner <pjw(at)rhyme(dot)com(dot)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

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2000-09-28 15:29:42
Subject: Re: pg_dump and sequences - RFC
Previous:From: Tom LaneDate: 2000-09-28 15:12:25
Subject: Re: sys_nerr, sys_errlist

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group