public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jacob Champion <[email protected]>
To: Tom Lane <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: Michael Banck <[email protected]>
Cc: Thomas Munro <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Time to drop RADIUS support?
Date: Fri, 23 Jan 2026 09:50:40 -0800
Message-ID: <CAOYmi+kwVHbra-80wSC7Rh9OGttdd8QFV+VcBtSNkEkux6XkyQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[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

view thread (3+ messages)  latest in thread

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: <CAOYmi+kwVHbra-80wSC7Rh9OGttdd8QFV+VcBtSNkEkux6XkyQ@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