We have no impact for that product (bpm engine), so i hope they use just basic stuff and everything will work fine. (seem so so far).
BR,
bkalas
On Thu, May 6, 2021 at 12:53 PM Jorge Solórzano <jorsol@gmail.com> wrote:
In general, the protocol of Postgres doesn't change, so the driver "might" work with newer versions of Postgres, the trouble comes if there are catalog changes and you query the metadata information or some parts that might require special handling.
The jdbc driver even test on CI the master branch of postgres, so it "should" work with the latest unreleased PostgreSQL 14 version, but please note that even if it should work, that doesn't mean that it implements new functionally from that version (this as always from the latest version of the driver).
Generally speaking, you should always try to use the latest version of the jdbc driver and don't be stuck with a specific version, you will get small improvements and bug fixes, but as usual, always make your own tests to make sure everything works correctly, in your case, as is a third party product, you might need to verify the compatibility with the vendor.
Regards,
On Thu, May 6, 2021 at 10:27 AM Branislav Kalas <bkalas@gmail.com> wrote:
Hi guys,
we are using third party product with bundled jdbc driver in version 42.2.3
Now postgres is going to be upgraded from 9.5 to 12.5
So far local tests are working also with 42.2.3 driver.
What is confusing me i went through changelogs of drivers and in 42.2.6 i saw this message
Added
CI tests with Java 11, and Java EA
Support temporary replication slots in ReplicationCreateSlotBuilder PR 1306
Support PostgreSQL 11, 12
Does that mean that 42.2.6 is first version supporting pg 12, or 42.2.3 should work with pg12 as well?
