| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improving GUC prefix ownership for extensions |
| Date: | 2026-02-11 16:44:23 |
| Message-ID: | CAKFQuwaQHV6fFWFcZB4u8jrXgwOzje+Qtdyroc-ZVO9byAM80w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday, February 11, 2026, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
wrote:
> > Do we really want the grief of making it mandatory?
>
> I didn't suggest making it mandatory - the current patch I attached is
> completely opt-in (default setting is exactly how it works currently,
> DBAs have to opt in by changing it).
>
> My reasoning for making the warning the default is to encourage
> extension developers to properly reserve GUC prefixes, without causing
> compatibility problems for users - but I'm not sure about that, that's
> why I submitted the patch with "off" default.
>
The fact users can set this to strict effectively makes variable
registration mandatory for extension authors, not merely “encouragement”,
IMO. That’s a decent step-up from “protect thyself” to “user-mandated”.
I’m just not seeing enough benefit here to provoke three-way discussions
between users, extension authors, and ourselves. Rather leave well-enough
alone given current information about the community’s experiences in this
realm.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-02-11 16:58:48 | Re: Improving GUC prefix ownership for extensions |
| Previous Message | Nathan Bossart | 2026-02-11 16:37:12 | Re: Pasword expiration warning |