regarding pg_dump: where there some changes from b3 to rc1 that would
explain the resulting rc1 pg_dump output (-c) being half as big as with
b3?
No...
regards, tom lane
well, it was 300mb before rc1, and now its only 188mb. inbetween i did a
vacuum full on one table. that shoulnd't affect
"Thomas H." <[EMAIL PROTECTED]> writes:
> regarding pg_dump: where there some changes from b3 to rc1 that would
> explain the resulting rc1 pg_dump output (-c) being half as big as with b3?
No...
regards, tom lane
---(end of broadcast)---
We have never promised backward compatibility of pg_dump output to older
server versions.
regarding pg_dump: where there some changes from b3 to rc1 that would
explain the resulting rc1 pg_dump output (-c) being half as big as with b3?
i've rerun pg_dump several times with the same result, and
"Greg Peters" <[EMAIL PROTECTED]> 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
The following bug has been logged online:
Bug reference: 2781
Logged by: Greg Peters
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1/8.2beta3
Operating system: WInXP
Description:database dump/restore problems
Details:
Hello,
I recently performed a database
