From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Cc: | pgsql(at)j-davis(dot)com |
Subject: | Re: pg_upgrade: warn about roles with md5 passwords |
Date: | 2025-06-04 20:15:49 |
Message-ID: | 30ab355f-7ea1-4d4b-9c08-4ddf74877841@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 02.06.25 17:32, Nathan Bossart wrote:
> Since MD5 passwords are slated to be marked as deprecated in v18, I figured
> it might be a good idea to add a check for roles with MD5 passwords to
> pg_upgrade. I'm tempted to suggest that we apply this to v18, but I'm
> content to leave it for v19 if nobody feels too strongly about it.
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2025-06-04 20:20:17 | Re: Enhance pg_createsubscriber to create required standby. |
Previous Message | Andres Freund | 2025-06-04 20:02:32 | Re: Non-reproducible AIO failure |