X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 47E7CD1B9AA for ; Fri, 5 Sep 2003 04:34:51 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 87516-10 for ; Fri, 5 Sep 2003 01:34:41 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id AAC94D1B8D1 for ; Fri, 5 Sep 2003 01:34:39 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h854Y7c03834; Fri, 5 Sep 2003 00:34:07 -0400 (EDT) From: Bruce Momjian Message-Id: <200309050434.h854Y7c03834@candle.pha.pa.us> Subject: Re: Query too slow In-Reply-To: <27125.1061913692@sss.pgh.pa.us> To: Tom Lane Date: Fri, 5 Sep 2003 00:34:06 -0400 (EDT) Cc: Stephan Szabo , Ang Chin Han , Rhaoni Chiu Pereira , PostgreSQL Performance X-Mailer: ELM [version 2.4ME+ PL106 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/87 X-Sequence-Number: 3453 Tom Lane wrote: > Stephan Szabo writes: > > On Tue, 26 Aug 2003, Ang Chin Han wrote: > >> Veering aside a bit, since we usually pinpoint performance problems by > >> looking at EXPLAIN ANALYZE's differences between the planner's > >> estimation and actual execution's stats, what's involved in parsing the > >> EXPLAIN ANALYZE results, and highlighting the places where they are way > >> different? Bold, underline, or put some asterisks in front of those steps. > > > The hardest part is determining where it matters I think. You can use the > > row counts as the base for that, but going from 1 row to 50 is not > > necessarily going to be an issue, but it might be if a nested loop is > > chosen. > > We've been chatting about this idea among the Red Hat group. The RHDB > Visual Explain tool (get it at http://sources.redhat.com/rhdb/) already > computes the percent of total runtime represented by each plan node. > It seems like we could highlight nodes based on a large difference > between estimated and actual percentage, or just highlight the nodes > that are more than X percent of the runtime. Is there a TODO here? Perhaps: o Have EXPLAIN ANALYZE highlight poor optimizer estimates -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073