X-Original-To: pgsql-general@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 151154760CC for ; Tue, 18 Mar 2003 09:34:23 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2IEYLub019095; Tue, 18 Mar 2003 09:34:21 -0500 (EST) To: miguel@ipatimup.pt Cc: pgsql-general@postgresql.org Subject: Re: Trigger issue, bug? on 7.2.1 In-reply-to: <2108.213.13.176.13.1047995196.squirrel@www.ipatimup.pt> References: <2108.213.13.176.13.1047995196.squirrel@www.ipatimup.pt> Comments: In-reply-to "Miguel Carvalho" message dated "Tue, 18 Mar 2003 13:46:36 +0000" Date: Tue, 18 Mar 2003 09:34:20 -0500 Message-ID: <19094.1047998060@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/852 X-Sequence-Number: 39344 "Miguel Carvalho" writes: > The trigger code will force another trigger fire because of the changes > in the record. I'm i right? No, altering the NEW record doesn't cause any additional trigger firings. If it did, such a trigger would be infinitely recursive. Your DELETE issued by the trigger would cause firing of ON DELETE triggers, but not another firing of ON UPDATE. regards, tom lane