Received: from localhost (unknown [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id 30FFC2E360E
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 13 Dec 2007 16:22:12 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024)
	with ESMTP id 10626-03 for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 13 Dec 2007 16:21:57 -0400 (AST)
Received: from smtp01.itc.nl (smtp01.itc.nl [192.87.16.12])
	by postgresql.org (Postfix) with ESMTP id 251A52E2ECA
	for <pgsql-sql@postgresql.org>; Thu, 13 Dec 2007 16:22:05 -0400 (AST)
Received: from itcnt09.itc.nl (Not Verified[172.16.2.9]) by smtp01.itc.nl with
	MailMarshal (v6, 2, 2, 3503)
	id <B476194680000>; Thu, 13 Dec 2007 21:22:00 +0100
Received: from [192.168.1.103] ([217.123.141.251]) by itcnt09.itc.nl with
	Microsoft SMTPSVC(6.0.3790.3959); Thu, 13 Dec 2007 21:22:00 +0100
Message-ID: <47619476.9060100@itc.nl>
Date: Thu, 13 Dec 2007 21:22:14 +0100
From: "Rolf A. de By" <deby@itc.nl>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
CC: pgsql-sql@postgresql.org
Subject: Re: Trigger definition . . . puzzled
References: <4760DCED.7080805@itc.nl> <12289.1197560972@sss.pgh.pa.us>
	<476156EF.8080901@itc.nl> <13236.1197563633@sss.pgh.pa.us>
In-Reply-To: <13236.1197563633@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Dec 2007 20:22:00.0489 (UTC)
	FILETIME=[D1084190:01C83DC5]
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200712/81
X-Sequence-Number: 29773

Ouch, that hurts!  It suddenly dawns on me . . . Big difference on table 
that you specify and table where it
actually takes effect.  Confusing at first.   Thanks a million, Tom.
> "Rolf A. de By" <deby@itc.nl> writes:
>   
>> Yes, this is an inheritance set-up.  But actually no: I am executing all 
>> my data changes against the parent table, and want the trigger on that 
>> parent table to fire for an insert on the parent table as it does.  But 
>> I also want the trigger to fire when an update on the parent table is 
>> executed, and this does not happen.
>>     
>
> There is no update on any row in the parent table.  The update is on a
> row in a child table.
>
> 			regards, tom lane
>