Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Greg Donald <gdonald(at)gmail(dot)com>
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Date: 2011-12-28 15:30:29
Message-ID: 201112280730.29932.adrian.klaver@gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Wednesday, December 28, 2011 7:18:01 am Greg Donald wrote:
> 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.


Wonder if it is related to this:
http://archives.postgresql.org/pgsql-bugs/2011-11/msg00098.php

Might want to file bug report:
http://www.postgresql.org/support/submitbug/

In the meantime what about using 8.4 pg_dump to create dump file and then using 
that file to load 9.1 server.

-- 
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

pgsql-general by date

Next:From: Greg DonaldDate: 2011-12-28 15:51:24
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Previous:From: Greg DonaldDate: 2011-12-28 15:18:01
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group