MIME-Version: 1.0
References: 
 <CAN4CZFPmF9fGOcFubwOxqXymhVo_RvbUx3bLoYQcfk=f0mwECw@mail.gmail.com>
 <202601281620.m3hrqtih5b2w@alvherre.pgsql>
 <CAN4CZFPUfTj-BF-m5=F7_MnY_T3+Qh-DuG7N7ojdbJDkT8JHeA@mail.gmail.com>
 <fd412b8e-fab5-43fe-b18d-3e035e4998a7@nataraj.su>
 <CAN4CZFMCh3vOWGPbU5pTB-bwnoAtgFuDJmGGv7z7xeez+WJiag@mail.gmail.com>
 <CAN4CZFMGwGdMnxP07Rk2qrC9eGQt31Lrerrnk66vQuzRhDEwiw@mail.gmail.com>
 <CAOYmi+nTXGcroZD_Mnkc8LYWYFbfDYNR4ML_yQ5sF9+DY2amcg@mail.gmail.com>
 <CAN4CZFMxQzFD0ZJS7pX5Ajdei7TmpROEZKG5vxmfmhCQEQX3fA@mail.gmail.com>
 <CAOYmi+mUdsTODm0F8PWBQYcCQPBKvHUAieXgoP1pWXtEA2N9Aw@mail.gmail.com>
 <CAN4CZFOdfRKjmpsDHWG_3Qgtmkcd41GFBH1uenC9-5yUj=hBzA@mail.gmail.com>
In-Reply-To: 
 <CAN4CZFOdfRKjmpsDHWG_3Qgtmkcd41GFBH1uenC9-5yUj=hBzA@mail.gmail.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
Date: Mon, 30 Mar 2026 16:54:18 -0700
Message-ID: 
 <CAOYmi+nUCSoMuQBm+2z_-98mMB6F5SDABA2X8CMoo==5O4v13A@mail.gmail.com>
Subject: Re: Custom oauth validator options
To: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: Nikolay Shaplov <dhyan@nataraj.su>,
 =?UTF-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>,
	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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAOYmi%2BnUCSoMuQBm%2B2z_-98mMB6F5SDABA2X8CMoo%3D%3D5O4v13A%40mail.gmail.com>
Precedence: bulk

On Mon, Mar 30, 2026 at 2:46=E2=80=AFPM Zsolt Parragi <zsolt.parragi@percon=
a.com> wrote:
> That won't be the most user friendly option, but it is still
> definitely better than not having the ability to configure this.

Sounds good. Barring other objections, then, I'll plan to move forward
with this approach for PG19.

Thanks!
--Jacob