Date: Thu, 3 Apr 2008 11:33:05 -0700 (PDT)
From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: chester c young <chestercyoung@yahoo.com>
Cc: sql pgsql <pgsql-sql@postgresql.org>
Subject: Re: apparent RI bug
In-Reply-To: <702370.31991.qm@web54301.mail.re2.yahoo.com>
Message-ID: <20080403113003.Q17782@megazone.bigpanda.com>
References: <702370.31991.qm@web54301.mail.re2.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 3 Apr 2008, chester c young wrote:

>
> Stephan Szabo <sszabo@megazone.bigpanda.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.