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

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: explain analyze with 'rows' but not timing
Date: 2011-12-23 23:51:30
Message-ID: 4EF51402.7050803@fuzzy.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dne 23.12.2011 22:37, Pavel Stehule napsal(a):
> 2011/12/23 Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Tomas Vondra<tv(at)fuzzy(dot)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

But that's the purpose of collecting row counts without timing data.

TL is asking about the opposite case - collecting timing data without
row counts. I can't imagine such use case ...

Tomas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-12-24 00:53:17 Representation of index clause lists
Previous Message Tom Lane 2011-12-23 22:02:29 Re: WIP: explain analyze with 'rows' but not timing