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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | kwalbrecht | 2012-05-16 14:19:53 | BUG #6644: Query give wrong results when 'is not null' is applied in where clause |
Previous Message | Tomonari Katsumata | 2012-05-16 11:35:44 | Re: BUG #6643: [PostgreSQL9.2beta1] COPY after changing fillfactor gets a PANIC. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-05-16 13:25:13 | Re: Missing optimization when filters are applied after window functions |
Previous Message | Florian Pflug | 2012-05-16 13:01:00 | Re: Avoiding execution of some functions by query rewriting |