Message-ID: <435902DC.3000807@gmail.com>
Date: Fri, 21 Oct 2005 17:01:48 +0200
From: Wiebe Cazemier <halfgaar@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050729)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Delete rule chain stops unexpectedly
References: <4358F79B.1000409@gmail.com> <21436.1129905772@sss.pgh.pa.us>
In-Reply-To: <21436.1129905772@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
 > The rule that actually deletes the rows from the underlying has to fire
 > last, since the rows are gone from the view (and hence from OLD) the
 > moment you delete them.

A quote from the postgresql manual:

"But for ON UPDATE and ON DELETE rules, the original query is done after the 
actions added by rules. This ensures that the actions can see the to-be-updated 
or to-be-deleted rows"

So, the actual delete should be done after all the rules. And even if it does 
delete before anything else, that does not explain why "step2" is not inserted 
into the debuglog table. Or, that all the rules _are_ executed when I call the 
query with "explain analayze".