BUG #2290: Incorrect sequence increment after backup/restore

From: "Oleg Mamontov" <oleg(at)mamontov(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2290: Incorrect sequence increment after backup/restore
Date: 2006-02-28 12:43:49
Message-ID: 20060228124349.5E8DFF0B03@svr2.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 2290
Logged by: Oleg Mamontov
Email address: oleg(at)mamontov(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Fuhr 2006-02-28 15:39:52 Re: BUG #2289: insert into tables not working
Previous Message David Sauer 2006-02-28 09:48:19 Re: BUG #2286: Wrong index creation with cs_CZ locales and