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
