From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | 馬 騰飛 <ma-tengfei(at)nec(dot)cn> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3 |
Date: | 2024-10-29 11:01:26 |
Message-ID: | DBE429A3-B64F-43AB-AA25-FC2A0CFE47F3@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 29 Oct 2024, at 04:25, 馬 騰飛 <ma-tengfei(at)nec(dot)cn> wrote:
>
> Thank you very much for your reply.
> However, after installing PostgreSQL 16.4, our server still encounters the following error when connecting to the database, just like with version 16.3:
> “Only AuthenticationClearTextPassword and AuthenticationMD5Password supported for now. Received: 10”.
> Could you please advise how to resolve this error? Should we also update Npgsql? If Npgsql needs to be updated, to which version should we update it?
I don't know the first thing about Npgsql so I can't offer any advice, but it
sounds like the problems is that the server wants to use SCRAM passwords and
your version of npgsql only support cleartext and md5. Changing the METHOD in
pg_hba.conf to md5 could fix the immediate problem perhaps but upgrading to a
version that support SCRAM seems the most appropriate (especially since md5
passwords are likely going away soon).
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-10-29 16:06:12 | Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3 |
Previous Message | David Rowley | 2024-10-29 10:42:24 | Re: Max size per relation for partitioned tables |