Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

From: Greg Donald <gdonald(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Date: 2011-12-28 15:18:01
Message-ID: CAO+WgCYgCcr3HrR9CmZM1jDkX4ZhW-HLAj8RwNiWANBdNORGBg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 28, 2011 at 9:07 AM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2011-12-28 15:30:29 Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Previous Message Adrian Klaver 2011-12-28 15:07:31 Re: PostgreSQL 9.1 pg_dump setval() sets wrong value