public inbox for [email protected]  

help / color / mirror / Atom feed

From: Thomas Munro <[email protected]>
To: Jacob Champion <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: Michael Banck <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Time to drop RADIUS support?
Date: Sun, 25 Jan 2026 12:14:19 +1300
Message-ID: <CA+hUKGKXHBCptORqu2jZf5o0Gw45Q7YMW9wKmrXYDm35uQStoA@mail.gmail.com> (raw)
In-Reply-To: <CAOYmi+kwVHbra-80wSC7Rh9OGttdd8QFV+VcBtSNkEkux6XkyQ@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CAOYmi+kwVHbra-80wSC7Rh9OGttdd8QFV+VcBtSNkEkux6XkyQ@mail.gmail.com>

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?

view thread (3+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Time to drop RADIUS support?
  In-Reply-To: <CA+hUKGKXHBCptORqu2jZf5o0Gw45Q7YMW9wKmrXYDm35uQStoA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox