Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4815F2E2D8D for ; Thu, 13 Dec 2007 11:50:01 -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 04244-02 for ; Thu, 13 Dec 2007 11:49:49 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id DA9712E032D for ; Thu, 13 Dec 2007 11:49:55 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lBDFnW5K012290; Thu, 13 Dec 2007 10:49:32 -0500 (EST) To: "Rolf A. de By" cc: pgsql-sql@postgresql.org Subject: Re: Trigger definition . . . puzzled In-reply-to: <4760DCED.7080805@itc.nl> References: <4760DCED.7080805@itc.nl> Comments: In-reply-to "Rolf A. de By" message dated "Thu, 13 Dec 2007 08:19:09 +0100" Date: Thu, 13 Dec 2007 10:49:32 -0500 Message-ID: <12289.1197560972@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/78 X-Sequence-Number: 29770 "Rolf A. de By" writes: > Thanks for that. There is some misunderstanding here. For this example, > I had taken the sting out of my trigger function and turned it into a > much more concise no-op, with warnings. The actual code of my original > trigger function is irrelevant. The no-op trigger function displays the > same strange behaviour: it works as expected for INSERTs, but not for > UPDATEs. The update goes through! And it shouldn't. Reading between the lines, I gather you have an inheritance setup and are expecting a trigger on the parent table to fire for events occurring in the child tables. Doesn't work like that; you need to put triggers on the child tables. regards, tom lane