From: | "Nasby, Jim" <nasbyj(at)amazon(dot)com> |
---|---|
To: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New EXPLAIN option: ALL |
Date: | 2019-05-08 22:31:15 |
Message-ID: | A3658A7F-1BDB-436D-9FE6-AFDEDAE50073@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On May 8, 2019, at 4:22 PM, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)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 VERBOSE is IMHO pretty useless...
I’m +1 on trying to move away from ANALYZE as well, though I think it’s mostly orthogonal...
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2019-05-08 22:37:50 | Re: _bt_split(), and the risk of OOM before its critical section |
Previous Message | Nasby, Jim | 2019-05-08 22:07:23 | Problems with pg_upgrade and extensions referencing catalog tables/views |