Re: Allow auto_explain to log plans before queries are executed - Mailing list pgsql-hackers

From David Steele
Subject Re: Allow auto_explain to log plans before queries are executed
Date
Msg-id 6de4356c-f18e-7c87-49bc-0bfa4b57a067@pgmasters.net
Whole thread Raw
In response to Re: Allow auto_explain to log plans before queries are executed  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On 3/5/20 8:46 AM, Julien Rouhaud wrote:
> On Thu, Feb 27, 2020 at 7:31 AM Julien Rouhaud <rjuju123@gmail.com> wrote:
>>
>> On Thu, Feb 27, 2020 at 7:12 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:
>>>
>>> čt 27. 2. 2020 v 7:01 odesílatel Yugo NAGATA <nagata@sraoss.co.jp> napsal:
>>>>   I think "query debugger" feature you proposed is out of scope of
>>>> auto_explain module. I also think the feature to analyze running
>>>> query online is great, but we will need another discussion on a new
>>>> module or eature for it.
>>>
>>>
>>> sure. My note was about using auto_explain like query_debugger. It has not too sense, and from this perspective,
theoriginal proposal to log plan before execution has more sense.
 
>>>
>>> you can log every plan with higher cost than some constant.
>>
>> Yes I thought about that too.  If you're not in an OLAP environment
>> (or with a specific user running few expensive queries), setup an
>> auto_explain.log_before_execution_min_cost.
> 
> There was some discussion but no clear consensus on what should really
> be done.  I'm marking the patch as waiting on author which seems more
> accurate.  Feel free to switch it back if that's a wrong move.

There does seem to be any progress towards a consensus so I'm marking 
this Returned with Feedback.

Regards,
-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Improving connection scalability: GetSnapshotData()
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: Improving connection scalability: GetSnapshotData()