Re: 9.2beta1 regression: pg_restore --data-only does not set sequence values any more - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: 9.2beta1 regression: pg_restore --data-only does not set sequence values any more
Date
Msg-id CAD5tBc+L3=MEz3KCjwrgcR82hU7qrm6qUZdCs89VGyQj-WgPiw@mail.gmail.com
Whole thread Raw
In response to Re: 9.2beta1 regression: pg_restore --data-only does not set sequence values any more  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 9.2beta1 regression: pg_restore --data-only does not set sequence values any more  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-bugs
On Wed, May 16, 2012 at 9:08 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Martin Pitt <mpitt@debian.org> writes:
> > while packaging 9.2 beta 1 for Debian/Ubuntu the postgresql-common
> > test suite noticed a regression: It seems that pg_restore --data-only
> > now skips the current value of sequences, so that in the upgraded
> > database the sequence counter is back to the default.
>
> I believe this is a consequence of commit
> a4cd6abcc901c1a8009c62a27f78696717bb8fe1, which introduced the entirely
> false assumption that --schema-only and --data-only have something to
> do with the order that entries appear in the archive ...
>
>
>

Darn, will investigate.

cheers

andrew

pgsql-bugs by date:

Previous
From: chris@cdrbill.com
Date:
Subject: BUG #6641: uuid.h warning during configure
Next
From: me@evancarroll.com
Date:
Subject: BUG #6645: Getting an error with “ERROR: PL/Perl function must return reference to hash or array”?