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

From Tom Lane
Subject Re: New EXPLAIN option: ALL
Date
Msg-id 5221.1557267912@sss.pgh.pa.us
Whole thread Raw
In response to Re: New EXPLAIN option: ALL  (Stephen Frost <sfrost@snowman.net>)
Responses Re: New EXPLAIN option: ALL  (Stephen Frost <sfrost@snowman.net>)
Re: New EXPLAIN option: ALL  (Robert Haas <robertmhaas@gmail.com>)
Re: New EXPLAIN option: ALL  (David Fetter <david@fetter.org>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> I'm generally in favor of doing something like what Tom is suggesting
> with VERBOSE, but I also feel like it should be the default for formats
> like JSON.  If you're asking for the output in JSON, then we really
> should include everything that a flag like VERBOSE would contain because
> you're pretty clearly planning to copy/paste that output into something
> else to read it anyway.

Meh --- I don't especially care for non-orthogonal behaviors like that.
If you wanted JSON but *not* all of the additional info, how would you
specify that?  (The implementation I had in mind would make VERBOSE OFF
more or less a no-op, so that wouldn't get you there.)

>> I do feel that it's a good idea to keep ANALYZE separate. "Execute
>> the query or not" is a mighty fundamental thing.  I've never liked
>> that name for the option though --- maybe we could deprecate it
>> in favor of EXECUTE?

> Let's not fool ourselves by saying we'd 'deprecate' it because that
> implies, at least to me, that there's some intention of later on
> removing it

True, the odds of ever actually removing it are small :-(.  I meant
mostly changing all of our docs to use the other spelling, except
for some footnote.  Maybe we could call ANALYZE a "legacy spelling"
of EXECUTE.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: New EXPLAIN option: ALL
Next
From: Heikki Linnakangas
Date:
Subject: Re: Failure in contrib test _int on loach