Re: Some belated patch review for "Buffers" explain analyze patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Some belated patch review for "Buffers" explain analyze patch
Date
Msg-id 603c8f071002091354pc79b125t35ad2ef5e505a710@mail.gmail.com
Whole thread Raw
In response to Re: Some belated patch review for "Buffers" explain analyze patch  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Some belated patch review for "Buffers" explain analyze patch
List pgsql-hackers
On Tue, Feb 9, 2010 at 3:26 PM, Josh Berkus <josh@agliodbs.com> wrote:
> On 2/9/10 11:50 AM, Greg Stark wrote:
>> Secondly, I think it's printing the total buffer usage for that node
>> across the whole query -- not the average per iteration. I agree that
>> the average is probably more confusing but it's what we do for every
>> other stat. Do we want to be consistent? Call out the inconsistency
>> somehow, perhaps by tagging it "Total Buffer Usage:" or something like
>> that?
>
> I'd prefer to have the average; it's very confusing to have an explain
> row which has the cost per iteration, but the buffer usage per node.

The cost per iteration thing is IMO one of the most confusing parts of
the EXPLAIN output; I'm not really eager to see us replicate that
elsewhere.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Listen / Notify - what to do when the queue is full
Next
From: Tom Lane
Date:
Subject: Re: Some belated patch review for "Buffers" explain analyze patch