public inbox for [email protected]  

help / color / mirror / Atom feed

From: Daniel Gustafsson <[email protected]>
To: 馬　騰飛 <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3
Date: Tue, 29 Oct 2024 12:01:26 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <BJSPR01MB04989313C380D79F1A0EE0A5E24B2@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>
References: <BJSPR01MB04989313C380D79F1A0EE0A5E24B2@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>

> On 29 Oct 2024, at 04:25, 馬　騰飛 <[email protected]> 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

view thread (2+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox