Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0G5g1V13232 for ; Wed, 16 Jan 2002 00:42:01 -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 g0G5g5g07543; Wed, 16 Jan 2002 00:42:06 -0500 (EST) To: jboes@nexcerpt.com (Jeff Boes) cc: pgsql-sql@postgresql.org Subject: Re: Long-running DELETE In-reply-to: References: Comments: In-reply-to jboes@nexcerpt.com (Jeff Boes) message dated "15 Jan 2002 11:02:22 -0800" Date: Wed, 16 Jan 2002 00:42:05 -0500 Message-ID: <7540.1011159725@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/175 X-Sequence-Number: 6261 jboes@nexcerpt.com (Jeff Boes) writes: > I've turned off every trigger in the database: > update pg_triggers set tgenabled=false; AFAIR, tgenabled isn't really supported; it's not tested for AFTER triggers, which is what foreign keys use. Your debug trace certainly shows that the FK triggers are still live. pg_dump knows how to disable triggers for real; I think it involves setting pg_class.reltriggers to zero. regards, tom lane