Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Donald <gdonald(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Date: 2011-12-28 22:57:55
Message-ID: 7487.1325113075@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greg Donald <gdonald(at)gmail(dot)com> writes:
> My pg_dump backups from before 9.1.1 were correct, now they are not:

> diff backup_20111212031701.sql backup_20111223013539.sql | grep setval
> | grep state_id

> < SELECT pg_catalog.setval('cp_state_id_seq', 52, true);
> > SELECT pg_catalog.setval('cp_state_id_seq', 1, false);

These "grep" calls are showing just exactly not enough to prove
anything. I remain unclear as to what state is actually in the
database, or what is being dumped, but I suspect at this point that you
may have multiple sequences of the same names in different schemas.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2011-12-28 22:58:46 Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Previous Message Greg Donald 2011-12-28 21:02:39 Re: PostgreSQL 9.1 pg_dump setval() sets wrong value