From: Nasby, Jim <nasbyj@amazon.com>
To: Vik Fearing <vik.fearing@2ndquadrant.com>
Cc: David Fetter <david@fetter.org>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: New EXPLAIN option: ALL
Date: Wed, 8 May 2019 22:31:15 +0000
Message-ID: <A3658A7F-1BDB-436D-9FE6-AFDEDAE50073@amazon.com> (raw)
In-Reply-To: <eff3ba2d-b92c-60ad-3456-a0902f5d18f7@2ndquadrant.com>
References: <20190507073046.GI28936@fetter.org>
<eff3ba2d-b92c-60ad-3456-a0902f5d18f7@2ndquadrant.com>
> 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 VERBOSE is IMHO pretty useless...
I’m +1 on trying to move away from ANALYZE as well, though I think it’s mostly orthogonal...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: nasbyj@amazon.com, vik.fearing@2ndquadrant.com, david@fetter.org
Subject: Re: New EXPLAIN option: ALL
In-Reply-To: <A3658A7F-1BDB-436D-9FE6-AFDEDAE50073@amazon.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox