Re: [BUGS] BUG #2781: database dump/restore problems
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 backup size, should it? i'll restore one of the new backups later on to be sure all data is still there. - thomas ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #2781: database dump/restore problems
"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)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #2781: database dump/restore problems
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 no error messages. - thomas ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [BUGS] BUG #2781: database dump/restore problems
"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 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 ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
