Postgres Pro
Downloads
Home   >   mailing lists

Re: auto_explain WAS: RFC: Timing Events - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: auto_explain WAS: RFC: Timing Events
Date
Msg-id CAMkU=1xGZuMbu4vhnmcFFZh7nz=4Z8rkYgq3b__=ecodHXCN=w@mail.gmail.com
Whole thread Raw
In response to Re: auto_explain WAS: RFC: Timing Events  (Josh Berkus <josh@agliodbs.com>)
Responses Re: auto_explain WAS: RFC: Timing Events  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Josh Berkus
Date:
Subject: Re: auto_explain WAS: RFC: Timing Events
Next
From: Bruce Momjian
Date:
Subject: Further pg_upgrade analysis for many tables