Re: Query progress indication - an implementation - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Query progress indication - an implementation
Date
Msg-id 200907020132.n621WJf11666@momjian.us
Whole thread Raw
In response to Re: Query progress indication - an implementation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Query progress indication - an implementation
List pgsql-hackers
Tom Lane wrote:
> Joshua Tolley <eggyknap@gmail.com> writes:
> > On Mon, Jun 29, 2009 at 02:07:23PM -0400, Tom Lane wrote:
> >> 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".
> 
> > What about showing the outermost node where work has started?
> 
> That's always the outermost node; what would it tell you?

[ Repost ]

I think the only resonable solution would be to consider the estimated
cost of each node and then compute what percentage complete each node
is.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: pg_migrator versus inherited columns
Next
From: "Fly.Li"
Date:
Subject: Re: gin--a rule for function parameter