Re: auto_explain WAS: RFC: Timing Events

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: auto_explain WAS: RFC: Timing Events
Дата
Msg-id CAMkU=1xGZuMbu4vhnmcFFZh7nz=4Z8rkYgq3b__=ecodHXCN=w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: auto_explain WAS: RFC: Timing Events  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: auto_explain WAS: RFC: Timing Events  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-hackers
On Wed, Nov 7, 2012 at 4:55 PM, Josh Berkus <josh@agliodbs.com> wrote:
>
>> What prevents you from doing so?  The performance impact?  The volume
>> of logs generated?
>
> Yes and yes.

I've never noticed a performance impact, unless you are having it
analyze, or having it log every query.  How do you measure the impact?

For the log volume, would it help if there was some "unexpectedness"
threshold?  That is, if a statement exceeds the duration threshold, it
gets explained,  But then it only gets logged if the actual duration
divided by the cost estimate exceeds some threshold.

Cheers,

Jeff



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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: auto_explain WAS: RFC: Timing Events
Следующее
От: Bruce Momjian
Дата:
Сообщение: Further pg_upgrade analysis for many tables