Skip site navigation (1) Skip section navigation (2)

Re: Query progress indication - an implementation

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Scara Maccai <m_lists(at)yahoo(dot)it>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Query progress indication - an implementation
Date: 2009-06-29 20:58:47
Message-ID: 1246309127.4038.473.camel@dn-x300-willij (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, 2009-06-29 at 14:07 -0400, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > So, while an actual % completed indicator would be perfect, a "query 
> > steps completed, current step =" would still be very useful and a large 
> > improvement over what we have now.
> 
> I think this is pretty much nonsense --- most queries run all their plan
> nodes concurrently to some extent.  You can't usefully say that a query
> is "on" some node, nor measure progress by whether some node is "done".

The requirement is not nonsense, even if the detail was slightly off.

We can regard plans as acting in phases with each blocking node
separating the plan. We know which nodes those are, so we can report
that.

For each phase, it may be very hard to say what percentage is truly
complete, but we could at least report how much work has been done and
provide a percentage against planned numbers.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-06-29 22:43:35
Subject: Re: Multi-Dimensional Histograms
Previous:From: Filip RembiaƂkowskiDate: 2009-06-29 20:48:45
Subject: Re: facing problem with createdb.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group