Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE - Mailing list pgsql-hackers

From David Rowley
Subject Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE
Date
Msg-id CAApHDvov847_KpLwV6f3PPKq5QzNrk9uFbGa9W4--Fd72G84=w@mail.gmail.com
Whole thread Raw
In response to Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE  (Greg Sabino Mullane <htamfids@gmail.com>)
Responses Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE
List pgsql-hackers
On Wed, 20 Nov 2024 at 13:13, Greg Sabino Mullane <htamfids@gmail.com> wrote:
>> It defaults to <literal>TRUE</literal> when <literal>ANALYZE</literal> is also enabled. Otherwise, it defaults to
<literal>FALSE</literal>.
>
> Is that second sentence really needed? Because "BUFFERS ON" will never be needed anymore (save as a no-op to allow
thesame explain queries to run cross-version), and BUFFERS OFF outside of analyze is meaningless.
 

"BUFFERS ON" will be needed if the user wants to see the buffer usage
in the planner when ANALYZE isn't specified. You'll see the planner
access buffers when the caches are not fully populated and for
get_actual_variable_range() work.

Maybe the wording could just be based on the wording for the SUMMARY
option, i.e. "Summary information is included by default when ANALYZE
is used but otherwise is not included by default".

David



pgsql-hackers by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: [PATCH] Add support for displaying database service in psql prompt
Next
From: Noah Misch
Date:
Subject: Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation