Date: Wed, 11 Jul 2007 13:01:57 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: TIMING A QUERY ???
Message-ID: <20070711170157.GX1241@phlogiston.dyndns.org>
References: <11542393.post@talk.nabble.com>
	<20070711153911.GQ1241@phlogiston.dyndns.org>
	<26707.1184170255@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <26707.1184170255@sss.pgh.pa.us>
User-Agent: Mutt/1.5.9i

On Wed, Jul 11, 2007 at 12:10:55PM -0400, Tom Lane wrote:
> Well, on some platforms (ie consumer-grade PCs) explain analyze can be a
> lot slower than just running the query, 

Yes, I suppose I exaggerated when I said "can't get any faster", but
given that the OP was talking on the order of hours for the EXPLAIN
ANALYSE to return, I assumed that the problem is one of impatience and
not clock cycles.  After all, the gettimeofday() additional overhead
is still not going to come in on the order of minutes without a
_bursting_ huge query plan.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
Unfortunately reformatting the Internet is a little more painful 
than reformatting your hard drive when it gets out of whack.
		--Scott Morris