From: | "Peter Koczan" <pjkoczan(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Legacy foreign keys |
Date: | 2007-12-12 17:40:33 |
Message-ID: | 4544e0330712120940i413e3ad6y867fc2a8744f623b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Dec 11, 2007 9:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Peter Koczan" <pjkoczan(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Medi Montaseri | 2007-12-12 22:25:16 | WHERE clause OR vs IN |
Previous Message | Listaccount | 2007-12-12 17:01:52 | Re: Dangerous hint in the PostgreSQL manual |