From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | chester c young <chestercyoung(at)yahoo(dot)com> |
Cc: | sql pgsql <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: apparent RI bug |
Date: | 2008-04-03 18:33:05 |
Message-ID: | 20080403113003.Q17782@megazone.bigpanda.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Thu, 3 Apr 2008, chester c young wrote:
>
> Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> wrote:
>
> > On Wed, 2 Apr 2008, chester c young wrote:
> >
> > > it appears I have a broken RI in my db.
>
> > Yeah, that looks pretty broken. Can you reproduce this from a clean
> > start repeatedly or is this a one off? Do you ever turn off triggers,
> > perhaps by modifying the pg_class row's reltriggers (I'd guess the
> > answer is no, but it'd be good to make sure)?
>
> only one error. unable to duplicate so far.
>
> this is a development db - triggers are frequently dropped and created,
> but I don't think ever concurrently with db activity.
Is it possible you ever had a before delete trigger that just did a return
NULL rather than raising an exception? IIRC, explicitly telling the
system to ignore the delete will work on the referential actions.
From | Date | Subject | |
---|---|---|---|
Next Message | Marcin Krawczyk | 2008-04-03 19:26:52 | Re: connections between servers |
Previous Message | chester c young | 2008-04-03 18:13:13 | Re: apparent RI bug |