Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fBT3sWm42730 for ; Fri, 28 Dec 2001 22:54:32 -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 fBT3sSg16732; Fri, 28 Dec 2001 22:54:28 -0500 (EST) To: Marc Spitzer cc: pgsql-sql@postgresql.org Subject: Re: Begin/Commit In-reply-to: <20011228204717.A15342@oscar.eng.cv.net> References: <20011228222730.555C0197395@jamie.edmonton.computalog.com> <16091.1009585573@sss.pgh.pa.us> <20011228204717.A15342@oscar.eng.cv.net> Comments: In-reply-to Marc Spitzer message dated "Fri, 28 Dec 2001 20:47:17 -0500" Date: Fri, 28 Dec 2001 22:54:28 -0500 Message-ID: <16729.1009598068@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/260 X-Sequence-Number: 6082 Marc Spitzer writes: > Would one of these conditions include deleting a row where there is > a field that is used as a foreign-key in another table? [ thinks ... ] Yes, I think so. The cases I'm familiar with involve inserts and updates, but probably a delete on the referenced table would fire triggers as well. With enough pending triggers, 7.0 and 7.1 will get slow. See discussions of 'triggered data change violation' error in the archives. regards, tom lane