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 f2KIDtN19630 for ; Tue, 20 Mar 2001 13:13: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 f2KIDrt11747; Tue, 20 Mar 2001 13:13:53 -0500 (EST) To: Cedar Cox cc: pgsql-interfaces@postgresql.org Subject: Re: triggered data change violation In-reply-to: References: Comments: In-reply-to Cedar Cox message dated "Tue, 20 Mar 2001 20:43:59 +0200" Date: Tue, 20 Mar 2001 13:13:53 -0500 Message-ID: <11744.985112033@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/156 X-Sequence-Number: 1317 Cedar Cox writes: > ERROR: triggered data change violation on relation "tblstsc2options" > What is this? It doesn't happen unless I'm in a transaction. I'm > INSERTing a record and then DELETEing it (in the same transaction) and on > delete I get this error. That's exactly what it's unhappy about ... but I'm not too clear on just *why* that should be considered an uncool thing to do when you have an AFTER trigger on the table. You're asking in the wrong list though; try pgsql-hackers or pgsql-sql to see if someone knows why this is bad. regards, tom lane