Re: Custom oauth validator options

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: Nikolay Shaplov <dhyan(at)nataraj(dot)su>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, VASUKI M <vasukianand0119(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, david(dot)g(dot)johnston(at)gmail(dot)com, Robert Haas <robertmhaas(at)gmail(dot)com>, myon(at)debian(dot)org
Subject: Re: Custom oauth validator options
Date: 2026-04-06 22:16:55
Message-ID: CAOYmi+=WsZ6rKe5vfa5mENzg-LkOjuepubcN-+e_bQgB8WDYEw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 6, 2026 at 3:09 PM Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
> > I believe this is now a complete patch
> > proposal; tear it apart. :D
>
> The patch looks good to me as is, I don't see any real issues with it,

Great! I am prepping for a commit Sometime Very Soon.

> maybe one cosmetic question in the test.
>
> + if (GetOAuthHBAOption(state, "log"))
> + elog(LOG, "%s", GetOAuthHBAOption(state, "log"));
> +
>
> If we treat the test code as an example for real implementations,

(It's not, though -- my test code is frequently abusive on purpose and
should not be used as best-practice. If we want compilable sample
code, that looks different from tests IMHO.)

> this
> and the other use could cache the option in a local variable instead
> of making duplicate calls, following the pattern of the documentation.

In this case, I want the test to pin the behavior that multiple calls
should work as you'd expect.

Thanks,
--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2026-04-06 22:22:32 Re: Adding REPACK [concurrently]
Previous Message Zsolt Parragi 2026-04-06 22:09:27 Re: Custom oauth validator options