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

From David Fetter
Subject Re: New EXPLAIN option: ALL
Date
Msg-id 20190521173857.GH28936@fetter.org
Whole thread Raw
In response to Re: New EXPLAIN option: ALL  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: New EXPLAIN option: ALL  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: New EXPLAIN option: ALL  (Robert Haas <robertmhaas@gmail.com>)
Re: New EXPLAIN option: ALL  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, May 21, 2019 at 12:32:21PM -0400, Robert Haas wrote:
> 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.

Would this be worth back-patching? I ask because adding it will cause
fairly large (if mechanical) churn in the regression tests.

Best,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: POC: Cleaning up orphaned files using undo logs
Next
From: Tom Lane
Date:
Subject: Re: New EXPLAIN option: ALL