Horton

Re: Custom oauth validator options

Zsolt Parragi <zsolt.parragi@percona.com>

View thread View on postgr.es
From: Zsolt Parragi <zsolt.parragi@percona.com>
To: Nikolay Shaplov <dhyan@nataraj.su>
Cc: Álvaro Herrera <alvherre@kurilemu.de>, 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
Date: 2026-01-29T13:00:57Z
Lists: pgsql-hackers 
> This patch suggests context independent API for managing extension
> defined sets of options. It is used for
> relation options and similar options, but cat be also used for any
> options sets, may be with small modifications.
>
> GUC options are almost same options as relation options. That is why, I
> guess, Alvaro suggested you to look at this patch.

Yes, but wouldn't that still require a generic refactoring of GUCs?
I'm not saying that would be a bad thing, but that's a big task in
itself.

But if I think about it in the general context of this thread (adding
extension options to pg_hba, ignoring the part that I tried to
implement it with GUCs in the current patch), that can be related.

Thanks for the clarification, I'll look into it in more detail.

Commits

  1. oauth: Allow validators to register custom HBA options

  2. Make LOAD of an already-loaded library into a no-op, instead of attempting