Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after
 Upgrading to PostgreSQL 16.3
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <BJSPR01MB04989313C380D79F1A0EE0A5E24B2@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>
Date: Tue, 29 Oct 2024 12:01:26 +0100
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBE429A3-B64F-43AB-AA25-FC2A0CFE47F3@yesql.se>
References: <BJSPR01MB04989313C380D79F1A0EE0A5E24B2@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>
To: =?utf-8?B?6aas44CA6aiw6aOb?= <ma-tengfei@nec.cn>
Archived-At: <https://www.postgresql.org/message-id/DBE429A3-B64F-43AB-AA25-FC2A0CFE47F3%40yesql.se>
Precedence: bulk

> On 29 Oct 2024, at 04:25, =E9=A6=AC=E3=80=80=E9=A8=B0=E9=A3=9B =
<ma-tengfei@nec.cn> wrote:
>=20
> Thank you very much for your reply.=20
> However, after installing PostgreSQL 16.4, our server still encounters =
the following error when connecting to the database, just like with =
version 16.3:
> =E2=80=9COnly AuthenticationClearTextPassword and =
AuthenticationMD5Password supported for now. Received: 10=E2=80=9D.
> 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