Re: PostgreSQL 9.1 pg_dump setval() sets wrong value - Mailing list pgsql-general

From Greg Donald
Subject Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Date
Msg-id CAO+WgCYgCcr3HrR9CmZM1jDkX4ZhW-HLAj8RwNiWANBdNORGBg@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL 9.1 pg_dump setval() sets wrong value  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: PostgreSQL 9.1 pg_dump setval() sets wrong value  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
On Wed, Dec 28, 2011 at 9:07 AM, Adrian Klaver <adrian.klaver@gmail.com> wrote:
> So how are the sequences being tied to the tables? In your previous post the
> table definitions did not show a SERIAL type or a default of nextval().

The id columns were created using "id serial NOT NULL".

I've gone back this morning and pulled older backups, from when I was
using pg_dump that came with my PostgreSQL 8.4 install.  Those backups
look fine to me, all the setval() calls are there and correct.  So it
looks like a problem with the new pg_dump best I can tell.


--
Greg Donald

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Next
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value