Re: pg_overexplain extension name - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: pg_overexplain extension name
Date
Msg-id CAKFQuwYcGavTN1h6SWObW3y-J9d2HViAvDkEVSQO+EtBrbNDCA@mail.gmail.com
Whole thread Raw
In response to Re: pg_overexplain extension name  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
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.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_overexplain extension name
Next
From: Nathan Bossart
Date:
Subject: small fix for pg_overexplain docs