X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A342552A5F for ; Mon, 28 Mar 2005 18:36:52 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 18341-07 for ; Mon, 28 Mar 2005 17:36:49 +0000 (GMT) Received: from mir3-fs.mir3.com (unknown [216.74.11.46]) by svr1.postgresql.org (Postfix) with ESMTP id F296452A3E for ; Mon, 28 Mar 2005 18:36:46 +0100 (BST) Received: from amateljan.mirlogic.com ([172.16.2.68]) by mir3-fs.mir3.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 28 Mar 2005 09:37:51 -0800 Subject: Re: Delete query takes exorbitant amount of time From: Mark Lewis To: Tom Lane Cc: pgsql-performance@postgresql.org In-Reply-To: <4009.1111717976@sss.pgh.pa.us> References: <1111709457.9085.127.camel@k2.cet.nau.edu> <2630.1111711927@sss.pgh.pa.us> <1111713798.23412.3.camel@amateljan.mirlogic.com> <4009.1111717976@sss.pgh.pa.us> Content-Type: text/plain Organization: MIR3, Inc. Message-Id: <1112031350.23412.131.camel@amateljan.mirlogic.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 (1.4.4-3) Date: Mon, 28 Mar 2005 09:35:50 -0800 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Mar 2005 17:37:52.0130 (UTC) FILETIME=[DDFF6E20:01C533BC] X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200503/604 X-Sequence-Number: 11309 Tom Lane Wrote: > Hmm ... I wonder how hard it would be to teach EXPLAIN ANALYZE to show > the runtime expended in each trigger when the statement is of a kind > that has triggers. We couldn't break down the time *within* the > triggers, but even this info would help a lot in terms of finger > pointing ... > > Seq Scan on ... (nn.nnn ms) > Trigger foo: nn.mmm ms > Trigger bar: nn.mmm ms > Total time: nn.mmm ms So I got the latest from CVS on Friday night to see how hard it would be to implement this, but it turns out that Tom has already committed the improvement, so I'm in Tom's fan club today. I imported my test dataset and was almost immediately able to track down the cause of my performance problem. Thanks! Mark Lewis