| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Michael Banck <mbanck(at)gmx(dot)net>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Time to drop RADIUS support? |
| Date: | 2026-01-23 16:30:07 |
| Message-ID: | 3112825.1769185807@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
> Would it work to add a WARNING (or something) to all back branches to
> ask users to write here, so that we can confirm in the next few months
> whether the protocol is completely unused or not? If we do find users,
> then we could try to think of workarounds[*], but otherwise we'd just
> remove it for pg19 (or pg20 at the latest) and not waste any more time
> on it.
I don't think that'd prove a lot. Affected users (if any) wouldn't
necessarily be quick to adopt the latest minor releases. They're
probably not even up-to-date on their RADIUS server, or they'd have
noticed it spewing complaints.
> 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-01-23 16:33:26 | Re: More speedups for tuple deformation |
| Previous Message | Srirama Kucherlapati | 2026-01-23 16:11:25 | RE: AIX support |