Re: pg_upgrade: warn about roles with md5 passwords

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: pg_upgrade: warn about roles with md5 passwords
Date: 2025-06-04 20:55:47
Message-ID: E9CD7B61-DAD1-4ACF-BC32-D623082D1575@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 4 Jun 2025, at 22:15, Peter Eisentraut <peter(at)eisentraut(dot)org> 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.

Agreed, I was going to support this warning but this comment convinced me
otherwise. pg_upgrade is messy as it is without tasking it with more usecases.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-06-04 21:02:38 Re: PG 18 release notes draft committed
Previous Message Nathan Bossart 2025-06-04 20:55:34 Re: pg_upgrade: warn about roles with md5 passwords