Date: Tue, 18 Jun 2019 23:15:25 +0200
From: David Fetter <david@fetter.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>,
	Alvaro Herrera <alvherre@2ndquadrant.com>,
	Stephen Frost <sfrost@snowman.net>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: New EXPLAIN option: ALL
Message-ID: <20190618211524.GA29683@fetter.org>
References: <20190515170529.GA18938@alvherre.pgsql>
 <11598.1557942806@sss.pgh.pa.us>
 <20190515175806.qciblz6rhi4rzu6y@alap3.anarazel.de>
 <55c4eff5-23d7-3eeb-a4a4-7d6c8753bf5d@2ndquadrant.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <55c4eff5-23d7-3eeb-a4a4-7d6c8753bf5d@2ndquadrant.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On Tue, Jun 18, 2019 at 11:08:31PM +0200, Peter Eisentraut wrote:
> On 2019-05-15 19:58, Andres Freund wrote:
> > On 2019-05-15 13:53:26 -0400, Tom Lane wrote:
> >> 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.
> > I'm not particularly invested in the idea of renaming ANALYZE - but I
> > think we might be able to come up with something less ambiguous than
> > EXECUTE. Even EXECUTION might be better.
> 
> The GQL draft uses PROFILE as a separate top-level command, so it would be
> 
>     PROFILE SELECT ...
> 
> That seems nice and clear.

Are you proposing something along the lines of this?

PROFILE [statement]; /* Shows the plan */
PROFILE RUN [statement]; /* Actually executes the query */

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