I have a table with a FK on itself: in fact a record may depend on
another table (pig's ear :-) I may run into a problem
dumping/restoring using pg_dump, PostgreSQL 7.1.0.
Here's a simplification of the table:
provo=# SELECT version();
version
Tom Lane wrote:
It's not much
harder than your given example to construct cases where dumping the rows
in OID order would be wrong too (just takes some UPDATEs).
Yes, I figured out myself quickly. :-(
like you may have some pre-release copy of pg_dump that gets this wrong
(the comment
Alessio Bragadini [EMAIL PROTECTED] writes:
It should work fine if rows would be dumped according to oid. Can this
be considered a bug?
No; or at least, that solution would be equally buggy. It's not much
harder than your given example to construct cases where dumping the rows
in OID order
Alessio Bragadini [EMAIL PROTECTED] writes:
Is it possible to use pg_dump 7.1 on a 7.0 database?
Tried. Nope.
Current CVS pg_dump (grab the nightly snapshot if you don't use CVS,
or wait for 7.1.1 in a day or two) is alleged to be able to work
against a 7.0 database. Give it a try.
Is it possible to use pg_dump 7.1 on a 7.0 database?
Tried. Nope.
--
Alessio F. Bragadini[EMAIL PROTECTED]
APL Financial Services http://village.albourne.com
Nicosia, Cyprus phone: +357-2-755750
It is more complicated than you think
-- The
