Re: Some queries starting to hang

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Some queries starting to hang
Date: 2006-06-06 15:37:46
Message-ID: 87ejy29tx1.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message A.M. 2006-06-06 15:37:58 Re: Some queries starting to hang
Previous Message Andrew Sullivan 2006-06-06 15:29:49 Re: Some queries starting to hang