Re: pg_dump and ALTER TABLE / ADD FOREIGN KEY - Mailing list pgsql-hackers

From Matthew T. O'Connor
Subject Re: pg_dump and ALTER TABLE / ADD FOREIGN KEY
Date
Msg-id 200206221832.39171.matthew@zeut.net
Whole thread Raw
In response to pg_dump and ALTER TABLE / ADD FOREIGN KEY  ("Rod Taylor" <rbt@zort.ca>)
Responses Re: pg_dump and ALTER TABLE / ADD FOREIGN KEY
List pgsql-hackers
> However, others don't believe constraints other than foreign keys
> should go unchecked.
>
> That said, is this functionality wanted outside of pg_dump /
> pg_restore?

pg_dump should reload a database as it was stored in the previous database.  
If  your old data is not clean, pg_dump / restore is not a very good tool for 
cleaning it up.  I think ignoring contrains is a good thing if it will load 
the data faster (at least when you are doing a database backup / restore).  
Why can't we do all alter table commands (that add constraints) after we load 
the data, that way we don't need to alter syntax at all.


pgsql-hackers by date:

Previous
From: "J. R. Nield"
Date:
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE
Next
From: Bruce Momjian
Date:
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE