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-29 16:10:01
Message-ID: CAO+WgCaoYNRX9zskK1f0f0tt8Ux=vxh4NYimu33qHdJAyOJ5_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 28, 2011 at 4:57 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Donald 2011-12-29 16:13:33 Re: PostgreSQL 9.1 pg_dump setval() sets wrong value
Previous Message Gabriele Bartolini 2011-12-29 14:49:36 Re: Postgresql Replication Comparison Required