Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSqqH-0006nF-6Y for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Oct 2020 00:10:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kSqqF-0006Q8-OQ for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Oct 2020 00:09:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSqqF-0006Q1-I8 for pgsql-bugs@lists.postgresql.org; Thu, 15 Oct 2020 00:09:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSqq9-0002vb-AI for pgsql-bugs@lists.postgresql.org; Thu, 15 Oct 2020 00:09:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09F09mCT3640831; Wed, 14 Oct 2020 20:09:48 -0400 From: Tom Lane To: zz5s-akd@asahi-net.or.jp cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16672: Postgres user passwords are corrupted during migration In-reply-to: <16672-cdf02792fc851417@postgresql.org> References: <16672-cdf02792fc851417@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 14 Oct 2020 23:05:47 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3640829.1602720588.1@sss.pgh.pa.us> Date: Wed, 14 Oct 2020 20:09:48 -0400 Message-ID: <3640830.1602720588@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form 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