Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlzH2-0059Ob-Bh for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Sep 2023 22:14:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qlzGz-00Gu0o-DE for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Sep 2023 22:14:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlzGz-00Gu0b-3l for pgsql-bugs@lists.postgresql.org; Thu, 28 Sep 2023 22:14:17 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlzGr-008APl-PM for pgsql-bugs@lists.postgresql.org; Thu, 28 Sep 2023 22:14:16 +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 38SME7Zb1105865; Thu, 28 Sep 2023 18:14:07 -0400 From: Tom Lane To: Kyle MacMillan cc: Laurenz Albe , pgsql-bugs@lists.postgresql.org Subject: Re: md5 password valid and invalid after upgrading In-reply-to: References: <01fbb3d2f280a7691ae6e563870c00d19fadb02e.camel@cybertec.at> <698775.1695853502@sss.pgh.pa.us> Comments: In-reply-to Kyle MacMillan message dated "Thu, 28 Sep 2023 17:49:39 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1105863.1695939247.1@sss.pgh.pa.us> Date: Thu, 28 Sep 2023 18:14:07 -0400 Message-ID: <1105864.1695939247@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Kyle MacMillan writes: > The server was AWS's "serverless" Aurora service, I'm not sure where logs > for that would be found. I did not see any error logs generated. > I found a solution, but I still think the docs do not illustrate the > regression, at the very least. To resolve this issue I had to paste my > existing password into the master password of the server. I was able to > connect to the database after that "change". That sounds like something you should discuss with AWS support. Postgres per se doesn't even have a concept of a "master password". I suspect you unwedged something in AWS's secret sauce, which would not be a matter for community Postgres to document. regards, tom lane