Re: ON DELETE CASCADE with multiple paths - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: ON DELETE CASCADE with multiple paths
Date
Msg-id 20070517090941.X9014@megazone.bigpanda.com
Whole thread Raw
In response to Re: ON DELETE CASCADE with multiple paths  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ON DELETE CASCADE with multiple paths  (Max Khon <mkhon@swsoft.com>)
Re: ON DELETE CASCADE with multiple paths  (Max Khon <mkhon@swsoft.com>)
List pgsql-bugs
On Thu, 17 May 2007, Tom Lane wrote:

> Max Khon <mkhon@swsoft.com> writes:
> > "delete from foo" fails:
>
> > ERROR: update or delete on table "bar" violates foreign key constraint
> > "foobar_fk0" on table "foobar"
> > SQL state: 23503
> > Detail: Key (bar_id)=(1) is still referenced from table "foobar".
> > Context: SQL statement "DELETE FROM ONLY "public"."bar" WHERE "foo_id" = $1"
>
> I see no bug here.  There is no guarantee about the order in which
> constraints are applied.

Except that SQL92 at least does seem to say in 11.8 that "All rows that
are marked for deletion are effectively deleted at the end of the
SQL-statement, prior to the checking of any integrity constraints." I
think that likely makes our behavior wrong, but I'm not really sure how to
get there from what we have now.

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #3266: SSL broken pipes kill the machine and fill the disk
Next
From: Andrew Sullivan
Date:
Subject: Re: strange problem with ip6