Feedback-ID: ie3de48e3:Fastmail
Date: Wed, 28 Jan 2026 17:23:39 +0100
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>, 
	VASUKI M <vasukianand0119@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, 
	david.g.johnston@gmail.com, Robert Haas <robertmhaas@gmail.com>, myon@debian.org, 
	Nikolay Shaplov <dhyan@nataraj.su>
Subject: Re: Custom oauth validator options
Message-ID: <202601281620.m3hrqtih5b2w@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAN4CZFPmF9fGOcFubwOxqXymhVo_RvbUx3bLoYQcfk=f0mwECw@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202601281620.m3hrqtih5b2w%40alvherre.pgsql>
Precedence: bulk

On 2026-Jan-28, Zsolt Parragi wrote:

> 0001: defines a new guc, guc_prefix_enforcement that potentially
> changes the behavior of prefix reservation. It has a few modes, based
> on which missing prefix reservations or variables defined outside the
> reserved prefix result in warnings or errors during library load time.
> This is unrelated to pgc_hba, and applies to all custom variables.

I didn't actually read this patch, but I wonder if this is something we
should attempt in the context of the larger refactoring done by the
patch series here,
https://postgr.es/m/2438819.yKrmzQ4Hd0@thinkpad-pgpro
I'm afraid it's likely to be very outdated at the moment, I think it'll
need a difficult rebase, but I invite you to have a look at what it
offered when it was last posted, and see if it would help write what
you're trying to achieve here.

Thanks

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"I'm always right, but sometimes I'm more right than other times."
                                                  (Linus Torvalds)
https://lore.kernel.org/git/Pine.LNX.4.58.0504150753440.7211@ppc970.osdl.org/