Insertion order violates Foreign keys
Posted: Sun 22 Nov 2009 18:17
Hi all,
I did a backup with pgdump as dmData option and while restoring the database a Foreign key violation occurs, despite the creation order was respected when I first created the db manually. So, is there an option to respect the creation order?
Another thing I figured out, why when dumping the whole database all the sequences become owned by "postres" while thery were originnaly owned by "public", is there an option for that, thanks for your reply.
I did a backup with pgdump as dmData option and while restoring the database a Foreign key violation occurs, despite the creation order was respected when I first created the db manually. So, is there an option to respect the creation order?
Another thing I figured out, why when dumping the whole database all the sequences become owned by "postres" while thery were originnaly owned by "public", is there an option for that, thanks for your reply.