Re: WIP: explain analyze with 'rows' but not timing

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Tomas Vondra <tv@fuzzy.cz>, pgsql-hackers@postgresql.org
Date: 2011-12-23T22:02:29Z
Lists: pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> 2011/12/23 Tom Lane <tgl@sss.pgh.pa.us>:
>> Tomas Vondra <tv@fuzzy.cz> writes:
>>> The motivation for this patch was that collection timing data often
>>> causes performance issues and in some cases it's not needed. But is this
>>> true for row counts?

>> Perhaps more to the point, is there a use case for collecting timing
>> data without row counts?  I find it hard to visualize a valid reason.

> yes - a searching of bad prediction

No, because timing alone proves nothing at all.  The machine could just
have been overloaded.

			regards, tom lane