Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE - Mailing list pgsql-hackers

From Nikolay Samokhvalov
Subject Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE
Date
Msg-id CANNMO+KhK3VxK+RNtCOca+81QZXmr51dG1c2xrX=-GXJXqAsyg@mail.gmail.com
Whole thread Raw
In response to Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE
List pgsql-hackers


On Tue, Nov 5, 2024 at 10:16 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Nikolay Samokhvalov <samokhvalov@gmail.com> writes:
> 1) EXPLAIN ANALYZE Is sometimes very confusing (because there is ANALYZE).
> Let's rename it to EXPLAIN EXECUTE?

This has got far too many years of history to be renamed now.

This is a really, really strange argument. Postgres keeps receiving new audiences at larger and larger scale. And they are confused.

It's better late than never. I didn't believe we would have "quit" working in psql.
 

> 2) VERBOSE doesn't include BUFFERS, and doesn't include SETTINGS; it might
> be also confusing sometimes. Let's include them so VERBOSE would be really
> verbose?

This is not likely to fly for compatibility reasons.

Can you elaborate?
 

> 3) small thing about grammar: allow omitting parentheses, so EXPLAIN
> EXECUTE VERBOSE would work.

The reason for the parens is that the other way would require reserving
all these options as keywords.

turns out, EXPLAIN ANALYZE VERBOSE already working (it's just not as verbose as one might expect_:

test=# explain analyze verbose select;
                QUERY PLAN
------------------------------------------
 Result  (cost=0.00..0.01 rows=1 width=0)
(1 row) 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE
Next
From: Robert Haas
Date:
Subject: Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE