Re: Custom oauth validator options
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro 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>
Date: 2026-01-28T16:23:39Z
Lists: pgsql-hackers
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/
Commits
-
oauth: Allow validators to register custom HBA options
- b977bd308a09 19 (unreleased) landed
-
Make LOAD of an already-loaded library into a no-op, instead of attempting
- 602a9ef5a7c6 9.0.0 cited