Re: explain analyze rows=%.0f - Mailing list pgsql-hackers

From Tom Lane
Subject Re: explain analyze rows=%.0f
Date
Msg-id 21013.1243618236@sss.pgh.pa.us
Whole thread Raw
In response to Re: explain analyze rows=%.0f  (Joshua Tolley <eggyknap@gmail.com>)
Responses Re: explain analyze rows=%.0f  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Joshua Tolley <eggyknap@gmail.com> writes:
> On Thu, May 28, 2009 at 11:12:42PM -0400, Robert Haas wrote:
>> On Thu, May 28, 2009 at 11:00 PM, Euler Taveira de Oliveira
>>> Don't you think is too strange having, for example, 6.67 rows?
>> 
>> No stranger than having it say 7 when it's really not.  Actually mine
>> mostly come out 1 when the real value is somewhere between 0.5 and
>> 1.49.  :-(

> +1. It would help users realize more quickly that some of the values in the
> EXPLAIN output are, for instance, *average* number of rows *per iteration* of a
> nested loop, say, rather than total rows found in all loops.

I think it would only be sensible to show fractional digits if nloops is
greater than 1.  Otherwise the value must in fact be an integer, and
you're just going to confuse people more by suggesting that it might not
be.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Kevin Field
Date:
Subject: Re: plperl error format vs plpgsql error format vs pgTAP
Next
From: Josh Berkus
Date:
Subject: Re: search_path vs extensions