| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kyle MacMillan <macattackftw(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: md5 password valid and invalid after upgrading |
| Date: | 2023-09-28 22:14:07 |
| Message-ID: | 1105864.1695939247@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kyle MacMillan <macattackftw(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyle MacMillan | 2023-09-28 23:32:49 | Re: md5 password valid and invalid after upgrading |
| Previous Message | Tom Lane | 2023-09-28 21:53:41 | Re: Broken type checking for empty subqueries |