| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: pg_overexplain extension name |
| Date: | 2025-07-14 14:34:40 |
| Message-ID: | CAJ7c6TP_Dvjm7YBUKv6vYs53Y4Poq_aBcrh1gp3EKr3xQAzfxw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2025-07-14 14:39:33 | Re: Changing shared_buffers without restart |
| Previous Message | Tom Lane | 2025-07-14 14:29:12 | Re: track needed attributes in plan nodes for executor use |