DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=cxnsLWAOVpyw21+RYiVXCoGMHGFJXJWvSOUh/QQ0mjd+dLNfuXty3Jj8GBo1IWFjZK
	Kj3wyq2WGZFRtM6CfqlfU5yjNUXRHK5MA/ySffu3CZUPM5RgYCjYXrMfz5ed78k9iF67
	uNc9wmJgLi3yf9X8LakOtBy5BnRJx4e4G2h7w=
MIME-Version: 1.0
In-Reply-To: <4A1F4FD5.7060204@timbira.com>
References: <603c8f070905281830g2e5419c4xad2946d149e21f9d@mail.gmail.com>
	<4A1F4FD5.7060204@timbira.com>
Date: Thu, 28 May 2009 23:12:42 -0400
Message-ID: <603c8f070905282012h7eb2210btb808f623a2757de0@mail.gmail.com>
Subject: Re: explain analyze rows=%.0f
From: Robert Haas <robertmhaas@gmail.com>
To: Euler Taveira de Oliveira <euler@timbira.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, May 28, 2009 at 11:00 PM, Euler Taveira de Oliveira
<euler@timbira.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. =A0Any
>> chance we could reconsider this decision? =A0I 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