Re: BUG #2290: Incorrect sequence increment after backup/restore

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oleg Mamontov <oleg(at)mamontov(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2290: Incorrect sequence increment after backup/restore
Date: 2006-03-06 05:16:37
Message-ID: 200603060516.k265GcH16054@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> "Oleg Mamontov" <oleg(at)mamontov(dot)net> writes:
> > If after CREATE TABLE with SERIAL column i'll change sequence increment to 2
> > or some other value (with ALTER SEQUENCE) then always work correctly (all
> > inserted rows will have values incremented by 2).
>
> We currently consider that a serial column is a "black box" and you
> should not mess with its underlying sequence directly. If you want
> nondefault properties for the sequence, create it as an independent
> sequence object and then just declare the column as "integer
> default nextval('seq')".

Added to TODO:

* %Disallow changing sequence characteristics like INCREMENT for
SERIAL columns

--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2006-03-06 05:23:28 Re: BUG #2290: Incorrect sequence increment after backup/restore
Previous Message Klein Balázs 2006-03-05 20:35:54 Re: BUG #2301: xml2 library not running on the Win Pg 8.1