Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4IxU-00HSE7-JC for pgsql-general@arkaria.postgresql.org; Fri, 25 Oct 2024 11:58:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t4IxS-00GV4Y-US for pgsql-general@arkaria.postgresql.org; Fri, 25 Oct 2024 11:58:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4IxS-00GV4P-JS for pgsql-general@lists.postgresql.org; Fri, 25 Oct 2024 11:58:22 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4IxQ-002muy-D9 for pgsql-general@lists.postgresql.org; Fri, 25 Oct 2024 11:58:21 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id DA37E119BAF for ; Fri, 25 Oct 2024 13:58:18 +0200 (CEST) Received: from s980.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id C6A5711A013; Fri, 25 Oct 2024 13:58:18 +0200 (CEST) Received: from s474.loopia.se (unknown [172.22.191.6]) by s980.loopia.se (Postfix) with ESMTP id C52322201644; Fri, 25 Oct 2024 13:58:18 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s979.loopia.se ([172.22.191.6]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id cpb1KGW9VGgg; Fri, 25 Oct 2024 13:58:18 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s979.loopia.se (Postfix) with ESMTPSA id 5E41710BC33E; Fri, 25 Oct 2024 13:58:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1729857498; bh=lCXA2aFpecvv6NpfXyBJ6vn5XTVnlemgp4kYcGYpuPM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=gPLtJOeeyIpD38sdTyC0wJ7CgZ3i8TFJ3hb+Dh2pY0lLqVJQGA+QMBoj2hQ/gHJVU CVhdz+DOvJFpeLsKv7hyCFBO281u+B9BEvHhfslMSeSpFw/fd97QzKTw/2Z1S66kcz Q22PtL6f568NWSURBsh5vJ075HLyBuFDM/M4IZXZ2ut2Bqn2XVfaG07NE1KCYl3Y7k wSm0RpYYlvmwOfV9kF4f9/Upu7BCdjP0RjUzs7n/s/KIriW3+kfpmzfmcx8jnkspXN Ue9IyY/cKHQzX7fBzA7r/CATRpSVAkkrJnAea6fIKY8MIJbBICGWj7GHTf6uu5Oi99 eIdoRpxsRZdnQ== 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 In-Reply-To: Date: Fri, 25 Oct 2024 13:58:07 +0200 Cc: "pgsql-general@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: To: =?utf-8?B?6aas44CA6aiw6aOb?= X-Mailer: Apple Mail (2.3774.600.62) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 25 Oct 2024, at 05:45, =E9=A6=AC=E3=80=80=E9=A8=B0=E9=A3=9B = wrote: >=20 > Dear PostgreSQL Community, >=20 > After upgrading PostgreSQL to version 16.3, our server encountered the = error=20 > "Only AuthenticationClearTextPassword and AuthenticationMD5Password = supported for now. Received: 10" when connecting to the database. >=20 > We are currently using .NET Framework version 3.5. If we upgrade = Npgsql to version 8.0.5, will there be compatibility issues?=20 > If there are compatibility issues, could you tell me the minimum = version of Npgsql that we should use to upgrade PostgreSQL to 16.3 = without upgrading the .NET Framework? Try PostgreSQL 16.4 instead, there was a known regression for very old = Npgsql versions in 16.3. -- Daniel Gustafsson