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

From Tom Lane
Subject Re: Query progress indication - an implementation
Date
Msg-id 1282.1246315794@sss.pgh.pa.us
Whole thread Raw
In response to Re: Query progress indication - an implementation  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Query progress indication - an implementation  (Greg Stark <gsstark@mit.edu>)
Re: Query progress indication - an implementation  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Mon, 2009-06-29 at 14:07 -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".

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

I was applying the word "nonsense" to the proposed implementation,
not the desire to have query progress indications ...

> 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.

[ shrug... ] You can regard them that way, but you won't get
particularly helpful results for a large fraction of real queries.
The system is generally set up to prefer "streaming" evaluation
as much as it can.  Even in nominally blocking nodes like Sort and Hash,
there are operational modes that look more like streaming, or at least
chunking.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Multi-Dimensional Histograms
Next
From: David Fetter
Date:
Subject: Re: Multi-Dimensional Histograms