On Mar5, 2014, at 23:49 , Tom Lane <t...@sss.pgh.pa.us> wrote:
> Florian Pflug <f...@phlo.org> writes:
>> On Mar5, 2014, at 18:37 , Tom Lane <t...@sss.pgh.pa.us> wrote:
>>> My advice is to lose the EXPLAIN output entirely.  If the authors of
>>> the patch can't agree on what it means, what hope have everyday users
>>> got of making sense of it?
>> The question isn't what the current output means, but whether it's a
>> good metric to report or not.
> If you can't agree, then it isn't.

Probably, yes, so let's find something that *is* a good metric.

(BTW, it's not the authors who disagree here. It was me who put the EXPLAIN
feature in, and Dean reviewed it and found it confusing. The original
author David seems to run out of time to work on this, and AFAIK hasn't
weighted in on that particular feature at all)

>> If we don't report anything, then how would a user check whether a query
>> is slow because of O(n^2) behaviour of a windowed aggregate, or because
>> of some other reasons?
> [ shrug... ]  They can see whether the Window plan node is where the time
> is going.  It's not apparent to me that the extra numbers you propose to
> report will edify anybody.

By the same line of reasoning, every metric except execution time is
superfluous. Comparing execution times really is a horrible way to measure
this - not only does it include all kinds of thing that have nothing to do
with the restart behaviour of aggregates, you'd also have to construct a
base-line query first which is guaranteed to not restart.

best regards,
Florian Pflug

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to