From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
cc: Andreas Karlsson <andreas@proxel.se>, pgsql-hackers@postgresql.org
Subject: Re: add warning upon successful md5 password auth
In-reply-to: <aY9ewvQr4PBCVe0e@nathan>
References: <aYzeAYEbodkkg5e-@nathan>
 <0731e3d8-3d13-4539-addc-a2c13a8b1b14@proxel.se> <aY9ewvQr4PBCVe0e@nathan>
Comments: In-reply-to Nathan Bossart <nathandbossart@gmail.com>
	message dated "Fri, 13 Feb 2026 11:26:26 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <543883.1771004590.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 Feb 2026 12:43:10 -0500
Message-ID: <543884.1771004590@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/543884.1771004590%40sss.pgh.pa.us>
Precedence: bulk

Nathan Bossart <nathandbossart@gmail.com> writes:
> On Fri, Feb 13, 2026 at 06:04:14AM +0100, Andreas Karlsson wrote:
>> The patch looks good and I think it would make sense to merge it in 19,=
 why
>> wait for 20? But the main question I see is if this is too noisy or not=
.
>> Some applications connected to PostgreSQL quite a lot and I am sure we =
would
>> make some users unhappy so I am not fully on board with this patch. But=
 on
>> the other hand we have way too many people who still use md5 and we rea=
lly
>> should push them towards using scram.

> FWIW if users are really annoyed with these warnings, they can disable t=
hem
> by setting md5_password_warnings to off.  But I think we really ought to=
 do
> something like $subject before we completely remove MD5 password support=
.

+1.  We need something like this to be there for at least a year or
two before we can consider removing MD5 passwords entirely.  As long
as the warnings can be turned off, I think it's all right and indeed
necessary to have them on-by-default.

			regards, tom lane

PS: I've not read the patch, so this isn't an endorsement of details.