Re: Custom oauth validator options - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Custom oauth validator options
Date
Msg-id CAOYmi+krPZDC8K+9z64M2EY9fELTKzLbqw8fD_wK=87YV+TBgw@mail.gmail.com
Whole thread Raw
In response to Re: Custom oauth validator options  (Zsolt Parragi <zsolt.parragi@percona.com>)
Responses Re: Custom oauth validator options
List pgsql-hackers
On Thu, Dec 18, 2025 at 1:08 AM Zsolt Parragi <zsolt.parragi@percona.com> wrote:
>
> It however requires shared_preload_libraries (that is common
> for all options), maybe oauth_validator_libraries could imply that?

Haven't looked at the patch yet, but I think most people probably want
to use session_preload_libraries, not shared_preload_libraries, so
that a security update to their validator doesn't require a restart of
the cluster.

If a particular validator implementation requires shared preload, so
be it; but I don't think we want to force it. Might be more reason to
look into the GUC system?

--Jacob



pgsql-hackers by date:

Previous
From: Oleg Tkachenko
Date:
Subject: Re: [BUG] [PATCH] pg_basebackup produces wrong incremental files after relation truncation in segmented tables
Next
From: Jacob Champion
Date:
Subject: Re: Make PGOAUTHCAFILE in libpq-oauth work out of debug mode