Re: explain analyze rows=%.0f
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Euler Taveira de Oliveira <euler@timbira.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2009-05-29T03:12:42Z
Lists: pgsql-hackers
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. 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
Commits
-
EXPLAIN: Always use two fractional digits for row counts.
- 95dbd827f2ed 18.0 landed
-
Adjust EXPLAIN test case to filter out "Actual Rows" values.
- 44cbba9a7f51 18.0 cited
-
Allow EXPLAIN to indicate fractional rows.
- ddb17e387aa2 18.0 landed
-
Fix pgbench performance issue induced by commit af35fe501.
- fb056564ec5b 18.0 cited