Re: md5 password valid and invalid after upgrading - Mailing list pgsql-bugs

From Tom Lane
Subject Re: md5 password valid and invalid after upgrading
Date
Msg-id 1105864.1695939247@sss.pgh.pa.us
Whole thread Raw
In response to md5 password valid and invalid after upgrading  (Kyle MacMillan <macattackftw@gmail.com>)
Responses Re: md5 password valid and invalid after upgrading
List pgsql-bugs
Kyle MacMillan <macattackftw@gmail.com> 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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Broken type checking for empty subqueries
Next
From: Kyle MacMillan
Date:
Subject: Re: md5 password valid and invalid after upgrading