Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBKH9Jm67357 for ; Thu, 20 Dec 2001 12:09:19 -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.4/8.11.4) with ESMTP id fBKH9Bi09264; Thu, 20 Dec 2001 12:09:11 -0500 (EST) To: "Josh Berkus" cc: "Glenn MacGregor" , pgsql-sql@postgresql.org Subject: Re: Transaction and cascade problem In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Thu, 20 Dec 2001 08:08:14 -0800" Date: Thu, 20 Dec 2001 12:09:11 -0500 Message-ID: <9261.1008868151@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/220 X-Sequence-Number: 6042 "Josh Berkus" writes: >> ERROR: triggered data change violation on relation "groups" > Yes. For some technical reason ( I'm not clear on this ) you cannot > both add and delete the same row within a PostgreSQL transaction. This > is a known issue in 7.1.x; I do not know if it is fixed in 7.2. Actually, we've just removed that error check in 7.2. The discussion concluded that we'd misinterpreted the spec in treating this condition as an error. You can simply dike out the error call (it's in src/backend/commands/trigger.c, IIRC) if it's getting in your way in 7.1. regards, tom lane