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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: WIP: explain analyze with 'rows' but not timing
Дата
Msg-id 8630.1324677749@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: WIP: explain analyze with 'rows' but not timing  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: WIP: explain analyze with 'rows' but not timing  (Pavel Stehule <pavel.stehule@gmail.com>)
Список 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: patch: bytea_agg
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: WIP: explain analyze with 'rows' but not timing