| From: | ow <oneway_111(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <pg(at)rbt(dot)ca> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Anyone working on pg_dump dependency ordering? |
| Date: | 2003-11-24 02:11:57 |
| Message-ID: | 20031124021157.72911.qmail@web21402.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> FK, primary, and unique constraints are already split out from the
> CREATE TABLE for performance reasons. We could think about folding them
> back in in a schema-only dump, but in a full dump I don't think it's
> negotiable --- you really want to load the table data before you install
> these constraints.
IMHO, not only data need to loaded before FK constraints are created but also
there has got to be a feature to allow creation of an FK constraint WITHOUT
doing the verification that all loaded/existing records satisfy the FK
constraint. The ability to create a FK constraint without verification of
existing records should exist by itself (maybe only to superuser) and also as
an option in pg_restore.
More details:
http://archives.postgresql.org/pgsql-admin/2003-11/msg00308.php
http://archives.postgresql.org/pgsql-admin/2003-11/msg00323.php
Thanks
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-11-24 04:06:59 | Re: Executable files in CVS |
| Previous Message | Marc G. Fournier | 2003-11-24 02:10:12 | Re: Executable files in CVS |