pg_overexplain extension name

Started by Bruce Momjian9 months ago5 messageshackers
Jump to latest
#1Bruce Momjian
bruce@momjian.us

I was thinking about the name of our new PG 18 pg_overexplain extension.
"Over-explain" has a negative connotation, like how can over-explaining
something be useful? Do we want that as the name of this new extension?

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

#2Aleksander Alekseev
aleksander@timescale.com
In reply to: Bruce Momjian (#1)
Re: pg_overexplain extension name

Hi Bruce,

I was thinking about the name of our new PG 18 pg_overexplain extension.
"Over-explain" has a negative connotation, like how can over-explaining
something be useful? Do we want that as the name of this new extension?

I think it was an intended pun and to my ears it's sort of funny. This
being said I can imagine how it might confuse a user or two, so +0.5
from me.

Here are several more neutral options:

* pg_explain_extra
* pg_explain_ext / _extended
* pg_explain_more

In reply to: Bruce Momjian (#1)
Re: pg_overexplain extension name

On Mon, Jul 14, 2025 at 5:23 AM Bruce Momjian <bruce@momjian.us> wrote:

I was thinking about the name of our new PG 18 pg_overexplain extension.
"Over-explain" has a negative connotation, like how can over-explaining
something be useful?

Over-explaining something can be somewhat useful if the person doing
the explaining doesn't exactly know which parts are relevant ahead of
time. If that person tells you everything that they know, you have
some chance of figuring out which parts are truly relevant.

"Over-explain" does have a slightly negative connotation, but I don't
find that inappropriate.

Do we want that as the name of this new extension?

Personally, I think it's fine. We ought to discourage the idea that
this is just "explain, but better".

--
Peter Geoghegan

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Geoghegan (#3)
Re: pg_overexplain extension name

Peter Geoghegan <pg@bowt.ie> writes:

On Mon, Jul 14, 2025 at 5:23 AM Bruce Momjian <bruce@momjian.us> wrote:

Do we want that as the name of this new extension?

Personally, I think it's fine. We ought to discourage the idea that
this is just "explain, but better".

I agree that it's a tad cutesy, but the time to complain about this
name was > two months ago. I can't see renaming it post-beta2.

regards, tom lane

#5David G. Johnston
david.g.johnston@gmail.com
In reply to: Peter Geoghegan (#3)
Re: pg_overexplain extension name

On Mon, Jul 14, 2025 at 11:55 AM Peter Geoghegan <pg@bowt.ie> wrote:

On Mon, Jul 14, 2025 at 5:23 AM Bruce Momjian <bruce@momjian.us> wrote:

I was thinking about the name of our new PG 18 pg_overexplain extension.
"Over-explain" has a negative connotation, like how can over-explaining
something be useful?

Over-explaining something can be somewhat useful if the person doing
the explaining doesn't exactly know which parts are relevant ahead of
time. If that person tells you everything that they know, you have
some chance of figuring out which parts are truly relevant.

"Over-explain" does have a slightly negative connotation, but I don't
find that inappropriate.

Do we want that as the name of this new extension?

Personally, I think it's fine. We ought to discourage the idea that
this is just "explain, but better".

If this does invoke a bit of a shock response I too believe that to be a
benefit.

pg_allthethingyouwantedtoknowaboutyourquerybutwereafraidtoask would be my
backup option.

David J.