From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Some queries starting to hang
Date: Tue, 06 Jun 2006 10:43:25 -0400
Message-ID: <17148.1149605005@sss.pgh.pa.us> (raw)
In-Reply-To: <1149604741.2621.487.camel@localhost.localdomain>
References: <1149534308.3583.56.camel@bg002441.pro-unlimited.com>
<22706.1149538039@sss.pgh.pa.us>
<20060605203851.GB7071@phlogiston.dyndns.org>
<23915.1149541591@sss.pgh.pa.us>
<1149604741.2621.487.camel@localhost.localdomain>
Simon Riggs <simon@2ndquadrant.com> writes:
> On Mon, 2006-06-05 at 17:06 -0400, Tom Lane wrote:
>> Well, it's a big query. If it ought to take a second or two, and
>> instead is taking an hour or two (1800 times the expected runtime), that
>> might be close enough to "never" to exhaust Chris' patience. Besides,
>> we don't know whether the 1800 might itself be an underestimate (too bad
>> Chris didn't provide EXPLAIN ANALYZE results).
> This is a good example of a case where the inefficiency of EXPLAIN
> ANALYZE would be a contributory factor to it not actually being
> available for diagnosing a problem.
Huh? The problem is the inefficiency of the underlying query.
regards, tom lane
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: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, ajs@crankycanuck.ca
Subject: Re: Some queries starting to hang
In-Reply-To: <17148.1149605005@sss.pgh.pa.us>
* 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