Re: WIP: explain analyze with 'rows' but not timing - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: WIP: explain analyze with 'rows' but not timing
Date
Msg-id CAFj8pRCdHvm0zv3i2JDrA-Rt+nddGiiSUNapCHc-=7WPFTL3pA@mail.gmail.com
Whole thread Raw
In response to Re: WIP: explain analyze with 'rows' but not timing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2011/12/23 Tom Lane <tgl@sss.pgh.pa.us>:
> 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.

sorry, I didn't understand to question.

Using only time is not practical

Regards

Pavel

>
>                        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Representation of index clause lists
Next
From: Fujii Masao
Date:
Subject: Re: Moving more work outside WALInsertLock