Re: explain analyze rows=%.0f
Euler Taveira <euler@timbira.com>
From: Euler Taveira de Oliveira <euler@timbira.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2009-05-29T03:00:37Z
Lists: pgsql-hackers
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? I would confuse users and programs that parses the EXPLAIN output. However, I wouldn't object to add ntuples to an extended explain output (as discussed in the other thread). -- Euler Taveira de Oliveira http://www.timbira.com/
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