From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: explain analyze rows=%.0f |
Date: | 2009-05-29 04:16:23 |
Message-ID: | 20090529041623.GE15201@eddie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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. That's an
important distinction that isn't immediately clear to the novice EXPLAIN
reader, but would become so very quickly as users tried to figure out how a
scan could come up with a fractional row.
- Josh / eggyknap
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wanner | 2009-05-29 05:53:20 | Re: PostgreSQL Developer meeting minutes up |
Previous Message | Bruce Momjian | 2009-05-29 03:31:23 | Re: Unicode string literals versus the world |