From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: TIMING A QUERY ???
Date: Wed, 11 Jul 2007 13:01:57 -0400
Message-ID: <20070711170157.GX1241@phlogiston.dyndns.org> (raw)
In-Reply-To: <26707.1184170255@sss.pgh.pa.us>
References: <11542393.post@talk.nabble.com>
<20070711153911.GQ1241@phlogiston.dyndns.org>
<26707.1184170255@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: TIMING A QUERY ???
In-Reply-To: <20070711170157.GX1241@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox