Horton
Menu

Re: Time to drop RADIUS support?

Jacob Champion <jacob.champion@enterprisedb.com>

View thread
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Álvaro Herrera <alvherre@kurilemu.de>, Michael Banck <mbanck@gmx.net>, Thomas Munro <thomas.munro@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-01-23T17:50:40Z
Lists: pgsql-hackers 
On Fri, Jan 23, 2026 at 8:30 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > I don't think removing it entirely from all back branches is a good
> > idea, without first making sure that there are no users.
>
> Agreed, we can't pull it from the back branches.  But I'm in favor of
> pulling it from HEAD if we document how to use PAM-based RADIUS
> instead.  I agree with Thomas' argument that the cost-benefit ratio
> of fixing our implementation would be poor.

+1.

I still think a WARNING in the back branches would be a kindness, to
let people know that they need to move.

--Jacob

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove RADIUS support.