Re: Index Tuning Features - Mailing list pgsql-hackers

From Robert Treat
Subject Re: Index Tuning Features
Date
Msg-id 200610101856.17786.xzilla@users.sourceforge.net
Whole thread Raw
In response to Re: Index Tuning Features  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Index Tuning Features
List pgsql-hackers
On Tuesday 10 October 2006 12:06, Tom Lane wrote:
> > Similar in usage to an EXPLAIN, the RECOMMEND command would return a
> > list of indexes that need to be added to get the cheapest plan for a
> > particular query (no explain plan result though).
>
> Both of these seem to assume that EXPLAIN results, without EXPLAIN
> ANALYZE results to back them up, are sufficient for tuning.  I find
> this idea a bit dubious, particularly for cases of "marginal" indexes.
>

While I agree with Tom that generally EXPLAIN is not enough for tuning, I also 
know that when your dealing with queries that have run times in multiples of 
hours (and the corresponding hour long index builds) EXPLAIN ANALYZE just 
isn't an option.  Anything that can be done to wheedle down your choices 
before you have to run EXPLAIN ANALYZE is a bonus. 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 8.2beta1 does not compile for me on Solaris 10
Next
From: Tom Lane
Date:
Subject: Re: pg_dump exclusion switches and functions/types