Updated wording:
* %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump
does not dump the changes
---------------------------------------------------------------------------
Bruce Momjian wrote:
> Tom Lane wrote:
> > "Oleg Mamontov" <[EMAIL PROTECTED]> 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. +
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
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. +
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
