Re: pg_overexplain extension name

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_overexplain extension name
Date: 2025-07-14 19:00:21
Message-ID: CAKFQuwYcGavTN1h6SWObW3y-J9d2HViAvDkEVSQO+EtBrbNDCA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 14, 2025 at 11:55 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:

> On Mon, Jul 14, 2025 at 5:23 AM Bruce Momjian <bruce(at)momjian(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-07-14 19:10:32 small fix for pg_overexplain docs
Previous Message Tom Lane 2025-07-14 19:00:04 Re: pg_overexplain extension name