public inbox for [email protected]help / color / mirror / Atom feed
Re: Time to drop RADIUS support? 3+ messages / 3 participants [nested] [flat]
* Re: Time to drop RADIUS support? @ 2026-01-23 16:30 Tom Lane <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Tom Lane @ 2026-01-23 16:30 UTC (permalink / raw) To: Álvaro Herrera <[email protected]>; +Cc: Michael Banck <[email protected]>; Thomas Munro <[email protected]>; PostgreSQL Hackers <[email protected]> =?utf-8?Q?=C3=81lvaro?= Herrera <[email protected]> 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Time to drop RADIUS support? @ 2026-01-23 17:50 Jacob Champion <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Jacob Champion @ 2026-01-23 17:50 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Álvaro Herrera <[email protected]>; Michael Banck <[email protected]>; Thomas Munro <[email protected]>; PostgreSQL Hackers <[email protected]> On Fri, Jan 23, 2026 at 8:30 AM Tom Lane <[email protected]> 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Time to drop RADIUS support? @ 2026-01-24 23:14 Thomas Munro <[email protected]> parent: Jacob Champion <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Thomas Munro @ 2026-01-24 23:14 UTC (permalink / raw) To: Jacob Champion <[email protected]>; +Cc: Tom Lane <[email protected]>; Álvaro Herrera <[email protected]>; Michael Banck <[email protected]>; PostgreSQL Hackers <[email protected]> On Sat, Jan 24, 2026 at 6:50 AM Jacob Champion <[email protected]> wrote: > On Fri, Jan 23, 2026 at 8:30 AM Tom Lane <[email protected]> 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. Great, it sounds like we have a plan. I think the wiki might be a good place for that documentation. The details are likely to change, and I wouldn't want to have to maintain that information in-tree, so I created some PAM how-to documentation at https://wiki.postgresql.org/wiki/RADIUS after testing on Debian and FreeBSD. We could point to that from the 19 release notes and in the deprecation notice added to the documentation for 14-18, calling it "community-maintained guidance on migration to supported configurations". Do we need to keep any trace of this in the 19 docs, and if so, where? A new tombstone section? ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2026-01-24 23:14 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-01-23 16:30 Re: Time to drop RADIUS support? Tom Lane <[email protected]> 2026-01-23 17:50 ` Jacob Champion <[email protected]> 2026-01-24 23:14 ` Thomas Munro <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox