Re: md5 password valid and invalid after upgrading

Поиск
Список
Период
Сортировка
От Kyle MacMillan
Тема Re: md5 password valid and invalid after upgrading
Дата
Msg-id CACW=iPtLgDLcLDkTxCfwmkFcMQF4OVn05kGZKJeR55QrOfmc_A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: md5 password valid and invalid after upgrading  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Hi Tom,

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".

No configuration changes, just re-inputting my existing password into the server, then I was able to remotely connect with psql 14.

Kyle

On Wed, Sep 27, 2023 at 6:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Kyle MacMillan <macattackftw@gmail.com> writes:
> Here's the connection method:
> psql -h <url> -d <database>

> I'm then prompted for a password and enter the password.

> And the error:
> psql: error: connection to server at <redacted> failed: fe_sendauth: error
> sending password authentication

What appears in the server's log when you do this?

                        regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Broken type checking for empty subqueries
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Broken type checking for empty subqueries