BUG #2290: Incorrect sequence increment after backup/restore - Mailing list pgsql-bugs

From Oleg Mamontov
Subject BUG #2290: Incorrect sequence increment after backup/restore
Date
Msg-id 20060228124349.5E8DFF0B03@svr2.postgresql.org
Whole thread Raw
Responses Re: BUG #2290: Incorrect sequence increment after backup/restore
List pgsql-bugs
The following bug has been logged online:

Bug reference:      2290
Logged by:          Oleg Mamontov
Email address:      oleg@mamontov.net
PostgreSQL version: 8.0.x/8.1.x
Operating system:   FreeBSD 4.x,5.x,6.x
Description:        Incorrect sequence increment after backup/restore
Details:

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).
But after database backup/restore (with pg_dump) this ALTER will not
restored and all next inserted rows will have values incremented by 1
(default for SERIAL data type).
It's seems like a bug...
Changing increment value often used with replication (master database
inserts has odd values and slave database inserts has even) and other
situations.

Sorry for my poor English.

pgsql-bugs by date:

Previous
From: David Sauer
Date:
Subject: Re: BUG #2286: Wrong index creation with cs_CZ locales and
Next
From: Michael Fuhr
Date:
Subject: Re: BUG #2289: insert into tables not working