On Wed, Jun 04, 2025 at 04:46:52PM -0400, Bruce Momjian wrote:
> On Wed, Jun 4, 2025 at 10:15:49PM +0200, Peter Eisentraut wrote:
>> I tend think pg_upgrade should stick to checking things that are necessary
>> for the upgrade to succeed. It shouldn't start being an interactive portal
>> to the release notes for aspects that are merely recommendations. I'm not
>> necessarily against having such a facility somewhere. But not everyone uses
>> pg_upgrade, and not every user of pg_upgrade reads all the messages.
>
> Yes, combine that with the fact that most people don't see pg_upgrade
> output, and the case is even less positive.
Okay, I'm getting the feeling that we should leave things as-is for v18 and
revisit 0002 (warning every time someone logs in with an MD5 password) down
the road. When we do remove MD5 password support, pg_upgrade will need
this check, but that's probably a few releases away still.
--
nathan
