Re: PostgreSQL 9.1 pg_dump setval() sets wrong value

On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> < 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.

Those grep calls prove my old backups with 8.4 pg_dump were good to go
and now they are not with 9.1 pg_dump.

> I remain unclear as to what state is actually in the
> database, or what is being dumped,

The whole thing is being dumped.  One command /usr/bin/pg_dump cp,
that's it, nothing special.


--
Greg Donald