From: Greg Stark <gsstark@mit.edu>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-performance@postgresql.org
Subject: Re: Some queries starting to hang
Date: 06 Jun 2006 11:37:46 -0400
Message-ID: <87ejy29tx1.fsf@stark.xeocode.com> (raw)
In-Reply-To: <1149605576.2621.502.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>
<17148.1149605005@sss.pgh.pa.us>
<1149605576.2621.502.camel@localhost.localdomain>
Simon Riggs <simon@2ndquadrant.com> writes:
> The idea I just had was: why do we need EXPLAIN ANALYZE to run to
> completion? In severe cases like this thread, we might be able to
> discover the root cause by a *partial* execution of the plan, as long as
> it was properly instrumented. That way, the OP might have been able to
> discover the root cause himself...
An alternate approach would be to implement a SIGINFO handler that prints out
the explain analyze output for the data built up so far. You would be able to
keep hitting C-t and keep getting updates until the query completes or you
decided to hit C-c.
I'm not sure how easy this would be to implement but it sure would be nice
from a user's point of view. Much nicer than having to specify some arbitrary
limit before running the query.
--
greg
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: gsstark@mit.edu, simon@2ndquadrant.com, tgl@sss.pgh.pa.us, ajs@crankycanuck.ca
Subject: Re: Some queries starting to hang
In-Reply-To: <87ejy29tx1.fsf@stark.xeocode.com>
* 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