Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2KKdtH85126; Tue, 20 Mar 2001 15:39:55 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2KKdrt12539; Tue, 20 Mar 2001 15:39:53 -0500 (EST) To: Cedar Cox cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [HACKERS] triggered data change violation In-reply-to: References: Comments: In-reply-to Cedar Cox message dated "Tue, 20 Mar 2001 23:13:14 +0200" Date: Tue, 20 Mar 2001 15:39:53 -0500 Message-ID: <12536.985120793@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/394 X-Sequence-Number: 2062 Cedar Cox writes: > Added note: The trigger is a BEFORE trigger. AFAIK the "triggered data change" message comes out of the AFTER trigger code. You sure you don't have any AFTER triggers on the table? Perhaps ones added implicitly by a foreign-key constraint? regards, tom lane