Skip site navigation (1) Skip section navigation (2)

Re: explain analyze rows=%.0f

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: explain analyze rows=%.0f
Date: 2009-05-29 03:12:42
Message-ID: 603c8f070905282012h7eb2210btb808f623a2757de0@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, May 28, 2009 at 11:00 PM, Euler Taveira de Oliveira
<euler(at)timbira(dot)com> wrote:
> Robert Haas escreveu:
>> I have always assumed that there is some very good reason why EXPLAIN
>> ANALYZE reports the number of rows as an integer rather than a
>> floating point value, but in reading explain.c it seems that the
>> reason is just that we decided to round to zero decimal places.  Any
>> chance we could reconsider this decision?  I often find myself wanting
>> to know the value that is here called ntuples, but rounding
>> ntuples/nloops off to the nearest integer loses too much precision.
>>
> 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.  :-(

...Robert

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2009-05-29 03:31:23
Subject: Re: Unicode string literals versus the world
Previous:From: Euler Taveira de OliveiraDate: 2009-05-29 03:00:37
Subject: Re: explain analyze rows=%.0f

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group