| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Greg Peters" <gregpeters79(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #2781: database dump/restore problems |
| Date: | 2006-11-28 02:56:50 |
| Message-ID: | 27567.1164682610@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Greg Peters" <gregpeters79(at)gmail(dot)com> writes:
> As you can see, the primary key is exported as a bigint, with a separate
> section for the sequence. This differs to the way 8.1 dumps the same table
> below:
This is an intentional change that fixes a lot of corner cases such as
renamed sequences. The former behavior looked simple, perhaps, but it
failed outright in too many scenarios. See
http://archives.postgresql.org/pgsql-committers/2006-08/msg00376.php
and preceding discussions in pgsql-hackers.
> I then tried to restore the DB dumped by 8.2b3 into 8.1, with no success. It
> didn't like the sequence part. This probably isn't so much a bug, but more a
> backwards compatibility issue.
We have never promised backward compatibility of pg_dump output to older
server versions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-28 02:59:06 | Re: BUG #2784: Performance serious degrades over a period of a month |
| Previous Message | Jeff Davis | 2006-11-28 02:22:41 | Re: [BUGS] Out of memory error causes Abort, Abort tries |