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: Wed, 12 Dec 2007 11:40:33 -0600
Message-ID: <4544e0330712120940i413e3ad6y867fc2a8744f623b@mail.gmail.com> (raw)
In-Reply-To: <10859.1197428770@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>
On Dec 11, 2007 9:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Peter Koczan" <pjkoczan@gmail.com> writes:
> >> No, pg_dump isn't involved --- the new smarts are inside the server,
> >> in CREATE CONSTRAINT TRIGGER. It sounds like Peter has a case that is
> >> confusing that new code. Could we see a complete example?
>
> > Sure, here's the command:
>
> [ squint... ] Which 8.3beta are you testing, exactly? This was dealt
> with in beta3.
>
> If it is beta3 or later, please send the output of "pg_dump -s -t wspolicy"
> from the 8.2 database.
*lightbulb* beta2. I haven't had much time to dedicate to testing new
betas yet (I was just trying to get a test 8.3 server up and running),
but I will do so. Thanks.
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: <4544e0330712120940i413e3ad6y867fc2a8744f623b@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