Message-ID: <7d64a850d87a88a46e2e9104caebb4305af4c106.camel@cybertec.at>
Subject: Re: JDBC Compatibility Matrix for PostgreSQL 16
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Edwin UY <edwin.uy@gmail.com>, pgsql-admin@lists.postgresql.org
Date: Wed, 26 Feb 2025 05:00:50 +0100
In-Reply-To: 
 <CA+wokJ_dK1jSgQtNUha8PJRUoGt_1-QsMt+D3ZoQK8GZKiVHhQ@mail.gmail.com>
References: 
	<CA+wokJ_dK1jSgQtNUha8PJRUoGt_1-QsMt+D3ZoQK8GZKiVHhQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/7d64a850d87a88a46e2e9104caebb4305af4c106.camel%40cybertec.at>
Precedence: bulk

On Wed, 2025-02-26 at 10:18 +1300, Edwin UY wrote:
> Does anyone know a link where I can check JDBC compatibility for PostgreS=
QL. We are upgrading from V12 to V16.
> I tried https://jdbc.postgresql.org and there is no working link for 42.2=
.
> Currently, the application is using 42.2.22. We have upgraded the non-PRO=
D DB to V16 already
> and it appears to be working fine. Just want to make sure there is no got=
cha of any sort.=C2=A0=20
> pgAdmin has stopped working though and requires an upgrade.

You should turn to the pgsql-jdbc mailing list for authoritative answers.

I believe that you should *always* use the latest version of the driver for=
 your Java version.
See https://jdbc.postgresql.org/download/

Yours,
Laurenz Albe