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

From Robert Haas
Subject Re: New EXPLAIN option: ALL
Date
Msg-id CA+TgmoYxzEp1ejykNHJ95t1nJ8q63yPDeboi74GRzXceaJGMUw@mail.gmail.com
Whole thread Raw
In response to Re: New EXPLAIN option: ALL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: New EXPLAIN option: ALL  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Wed, May 15, 2019 at 1:53 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> That seems too confusing.
>
> > Ok.  Are you voting for using EXEC as a keyword to replace ANALYZE?
>
> FWIW, given the conflict against "EXPLAIN EXECUTE prepared_stmt_name",
> we should probably just drop the whole idea.  It seemed like a great
> idea at the time, but it's going to confuse people not just Bison.

+1.  I think trying to replace ANALYZE with something else is setting
ourselves up for years, possibly decades, worth of confusion.  And
without any real benefit.

Defaulting BUFFERS to ON is probably a reasonable change, thuogh.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Minimal logical decoding on standbys
Next
From: Andres Freund
Date:
Subject: Re: A few more opportunities to use TupleTableSlotOps fields