pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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, 6 Jun 2006 10:14:17 -0500
Message-ID: <20060606151416.GD53487@pervasive.com> (raw)
In-Reply-To: <17426.1149606369@sss.pgh.pa.us>
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>
	<17426.1149606369@sss.pgh.pa.us>

On Tue, Jun 06, 2006 at 11:06:09AM -0400, Tom Lane wrote:
> > 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...
> 
> I don't think that helps, as it just replaces one uncertainty by
> another: how far did the EXPLAIN really get towards completion of the
> plan?  You still don't have any hard data.

Does that really matter, though? The point is to find the node where the
estimate proved to be fantasy. It might even make sense to highlight
that node in the output, so that users don't have to wade through a sea
of numbers to find it.

If it is important to report how far along the query got, it seems that
could always be added to the explain output.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (28+ messages)  latest in thread

Message-ID: <20060606151416.GD53487@pervasive.com>
Permalink:  ../20060606151416.GD53487@pervasive.com/
Also on:    postgresql.org/message-id/20060606151416.GD53487@pervasive.com

 · 

reply

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: jnasby@pervasive.com, tgl@sss.pgh.pa.us, simon@2ndquadrant.com, ajs@crankycanuck.ca
  Subject: Re: Some queries starting to hang
  In-Reply-To: <20060606151416.GD53487@pervasive.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