| From: | Wes <wespvp(at)syntegra(dot)com> |
|---|---|
| To: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, louis gonzales <gonzales(at)linuxlouis(dot)net> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Adding foreign key constraints without integrity |
| Date: | 2006-06-20 14:18:08 |
| Message-ID: | C0BD6DD0.28944%wespvp@syntegra.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/20/06 5:07 AM, "Florian G. Pflug" <fgp(at)phlo(dot)org> wrote:
> My suggestion was to create the fk _before_ loading the data, and disable it
> similarly to what "--disable-triggers" doest. It turned out, however, that a
> FK always depends on a unique index (be it a primary key, or not), which
> prevents
> my plan from working :-(
That was a great idea - too bad it didn't pan out.
I don't suppose there's any (reasonable) way to directly insert into the
system tables to create the constraint? I could knock almost 2 days off of
the almost 4 days to reload if I could solve this.
Wes
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoffrey | 2006-06-20 14:20:19 | Re: help with error message from perl Pg |
| Previous Message | Tom Lane | 2006-06-20 14:11:51 | Re: DocBook 4.2 detecting at configure time |