Re: Improving GUC prefix ownership for extensions - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Improving GUC prefix ownership for extensions
Date
Msg-id CAKFQuwaQHV6fFWFcZB4u8jrXgwOzje+Qtdyroc-ZVO9byAM80w@mail.gmail.com
Whole thread
In response to Re: Improving GUC prefix ownership for extensions  (Zsolt Parragi <zsolt.parragi@percona.com>)
List pgsql-hackers
On Wednesday, February 11, 2026, Zsolt Parragi <zsolt.parragi@percona.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.

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Pasword expiration warning
Next
From: Tom Lane
Date:
Subject: Re: Improving GUC prefix ownership for extensions