Re: New EXPLAIN option: ALL - Mailing list pgsql-hackers

From Nasby, Jim
Subject Re: New EXPLAIN option: ALL
Date
Msg-id A3658A7F-1BDB-436D-9FE6-AFDEDAE50073@amazon.com
Whole thread Raw
In response to Re: New EXPLAIN option: ALL  (Vik Fearing <vik.fearing@2ndquadrant.com>)
List pgsql-hackers
> On May 8, 2019, at 4:22 PM, Vik Fearing <vik.fearing@2ndquadrant.com> wrote:
> 
> On 07/05/2019 09:30, David Fetter wrote:
>> Folks,
>> 
>> It can get a little tedious turning on (or off) all the boolean
>> options to EXPLAIN, so please find attached a shortcut.
> 
> I would rather have a set of gucs such as default_explain_buffers,
> default_explain_summary, and default_explain_format.
> 
> Of course if you default BUFFERS to on(*) and don't do ANALYZE, that
> should not result in an error.
> 
> (*) Defaulting BUFFERS to on is something I want regardless of anything
> else we do.

I think this, plus Tom’s suggesting of changing what VERBOSE does, is the best way to handle this. Especially since
VERBOSEis IMHO pretty useless...
 

I’m +1 on trying to move away from ANALYZE as well, though I think it’s mostly orthogonal...


pgsql-hackers by date:

Previous
From: "Nasby, Jim"
Date:
Subject: Problems with pg_upgrade and extensions referencing catalogtables/views
Next
From: Peter Geoghegan
Date:
Subject: Re: _bt_split(), and the risk of OOM before its critical section