Re: pg_dump and ALTER TABLE / ADD FOREIGN KEY

From: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
To: "Rod Taylor" <rbt(at)zort(dot)ca>, "Hackers List" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump and ALTER TABLE / ADD FOREIGN KEY
Date: 2002-06-22 22:32:39
Message-ID: 200206221832.39171.matthew@zeut.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-06-22 23:17:11 Re: Index Scans become Seq Scans after VACUUM ANALYSE
Previous Message J. R. Nield 2002-06-22 22:22:58 Re: Index Scans become Seq Scans after VACUUM ANALYSE