Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martin Pitt <mpitt(at)debian(dot)org>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: 9.2beta1 regression: pg_restore --data-only does not set sequence values any more
Date: 2012-05-16 13:08:26
Message-ID: 23209.1337173706@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
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 ...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-05-16 13:25:13
Subject: Re: Missing optimization when filters are applied after window functions
Previous:From: Florian PflugDate: 2012-05-16 13:01:00
Subject: Re: Avoiding execution of some functions by query rewriting

pgsql-bugs by date

Next:From: kwalbrechtDate: 2012-05-16 14:19:53
Subject: BUG #6644: Query give wrong results when 'is not null' is applied inwhere clause
Previous:From: Tomonari KatsumataDate: 2012-05-16 11:35:44
Subject: Re: BUG #6643: [PostgreSQL9.2beta1] COPY after changing fillfactor gets a PANIC.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group