public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Á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 11:30:07 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[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

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]
  Subject: Re: Time to drop RADIUS support?
  In-Reply-To: <[email protected]>

* 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