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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martin Pitt <mpitt(at)debian(dot)org>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: 9.2beta1 regression: pg_restore --data-only does not set sequence values any more
Date: 2012-05-16 14:23:07
Message-ID: CAD5tBc+L3=MEz3KCjwrgcR82hU7qrm6qUZdCs89VGyQj-WgPiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, May 16, 2012 at 9:08 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Martin Pitt <mpitt(at)debian(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message me 2012-05-16 16:47:49 BUG #6645: Getting an error with “ERROR: PL/Perl function must return reference to hash or array”?
Previous Message kwalbrecht 2012-05-16 14:19:53 BUG #6644: Query give wrong results when 'is not null' is applied in where clause

Browse pgsql-hackers by date

  From Date Subject
Next Message Hitoshi Harada 2012-05-16 14:23:39 Re: Missing optimization when filters are applied after window functions
Previous Message Tom Lane 2012-05-16 13:51:26 Re: read() returns ERANGE in Mac OS X