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+WgCaoYNRX9zskK1f0f0tt8Ux=vxh4NYimu33qHdJAyOJ5_w@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL 9.1 pg_dump setval() sets wrong value  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

I have one schema and one database on that one database server.

And like I said, it worked fine until 9.1.  If it was any of those
reasons you suggest, would I not have experienced the same problem
back in 8.4?  I would think so.


--
Greg Donald

pgsql-general by date:

Previous
From: Gabriele Bartolini
Date:
Subject: Re: Postgresql Replication Comparison Required
Next
From: Greg Donald
Date:
Subject: Re: PostgreSQL 9.1 pg_dump setval() sets wrong value