From: Peter Koczan <pjkoczan@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: Legacy foreign keys
Date: Fri, 1 Feb 2008 12:30:02 -0600
Message-ID: <4544e0330802011030l477b0d8ek57909e75ff367128@mail.gmail.com> (raw)
In-Reply-To: <18279.1201845349@sss.pgh.pa.us>
References: <4544e0330712101112r6aeccfcckef378a7ea1795e07@mail.gmail.com>
<20071210195046.GE27126@alvh.no-ip.org>
<20427.1197324492@sss.pgh.pa.us>
<4544e0330712111901k1fa50c5dgb26287aff018e98c@mail.gmail.com>
<10859.1197428770@sss.pgh.pa.us>
<4544e0330712120940i413e3ad6y867fc2a8744f623b@mail.gmail.com>
<4544e0330801311613t5cc6741cx1464947c2215f198@mail.gmail.com>
<18279.1201845349@sss.pgh.pa.us>
> > I finally found more time to test this more extensively. i'm still
> > running into an issue with this, although it's different this time.
> > There are no errors printed to the terminal, but neither the foreign
> > key nor the trigger get made.
>
> It looks like you are trying to restore from a selective dump (-t
> switch) that includes only one of the two tables involved in the FK
> constraint. The backend logic for converting triggers to proper FK
> constraints can only work if it sees both tables (and their triggers)
> created during a single session.
I see what you're saying, but the weird thing is that this happened
even when I did a full dump/restore of that database. I'll try out a
few different things (like restoring the tables, then restoring the
triggers). Hopefully I'll be able to suss out the issue or at least
find a workaround.
Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pjkoczan@gmail.com, tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org
Subject: Re: Legacy foreign keys
In-Reply-To: <4544e0330802011030l477b0d8ek57909e75ff367128@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox