From: Tom Lane <tgl@sss.pgh.pa.us>
To: zz5s-akd@asahi-net.or.jp
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16672: Postgres user passwords are corrupted during migration
Date: Wed, 14 Oct 2020 20:09:48 -0400
Message-ID: <3640830.1602720588@sss.pgh.pa.us> (raw)
In-Reply-To: <16672-cdf02792fc851417@postgresql.org>
References: <16672-cdf02792fc851417@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> The postgres user password is corrupted when migrating from Postgresql 12.4
> to Postgresql 13.
I tried to verify that claim, without success: AFAICS, dump/reload will
correctly propagate the password to the new server, in either md5 or
SCRAM format.
You have not shown very much supporting detail, but I wonder whether
the password is hashed in md5 format and the v13 server's pg_hba.conf
is set to only allow SCRAM passwords. The report sent to the client
intentionally just says "password authentication failed", but you
could look in the postmaster log to see what it says about the failure.
Also, look in pg_authid (of either server), or in the dump file, to see
whether the rolpassword value starts with "md5" or "SCRAM-SHA-256".
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, zz5s-akd@asahi-net.or.jp, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16672: Postgres user passwords are corrupted during migration
In-Reply-To: <3640830.1602720588@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox