Re: Custom oauth validator options

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, 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, Nikolay Shaplov <dhyan(at)nataraj(dot)su>
Subject: Re: Custom oauth validator options
Date: 2026-01-28 19:21:13
Message-ID: CAN4CZFPUfTj-BF-m5=F7_MnY_T3+Qh-DuG7N7ojdbJDkT8JHeA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> but I wonder if this is something we
> should attempt in the context of the larger refactoring done by the
> patch series here,

That patch series is interesting but it is about SQL (table, index,
operator) options, while this is about guc variable validation and
extension. These seem unrelated to me.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-01-28 19:25:34 Re: Pasword expiration warning
Previous Message Steve Chavez 2026-01-28 19:19:31 Re: Add SECURITY_INVOKER_VIEWS option to CREATE DATABASE