Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0GFEOV14188 for ; Wed, 16 Jan 2002 10:14:24 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 8D049D5F3; Wed, 16 Jan 2002 07:14:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 82B615BF4; Wed, 16 Jan 2002 07:14:24 -0800 (PST) Date: Wed, 16 Jan 2002 07:14:24 -0800 (PST) From: Stephan Szabo To: Jeff Boes Cc: Subject: Re: Long-running DELETE In-Reply-To: <20020116083828.2b323ec7.jboes@nexcerpt.com> Message-ID: <20020116071240.U43837-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200201/182 X-Sequence-Number: 6268 On Wed, 16 Jan 2002, Jeff Boes wrote: > On Tue, 15 Jan 2002 21:13:49 -0800 (PST) > Stephan Szabo wrote: > > > > > On 15 Jan 2002, Jeff Boes wrote: > > > > > update pg_triggers set tgenabled=false; > > > > I don't think tgenabled works. You'll probably need to set reltriggers to > > 0 on the pg_class row for the table (and then reset it to the correct > > value afterwards). > > > > I can't confirm that one, but I did find that things got a lot faster > when I also did > > update pg_trigger > set tgenabled=false, > tgdeferrable=true, > tginitdeferred=true > > for each of the associated triggers. Hmm, that'd make the actual trigger calls wait till end of transaction. If you were running the deletes in a transaction, that'd make the delete parts go faster, but the commit should take a while.