Notable changes

• fixed NPE in PreparedStatement.executeBatch in case of empty batch (regression since 42.1.2) PR#867

Notable changes

• Better logic for returning keyword detection. Previously, pgjdbc could be defeated by column names that contain returning, so pgjdbc failed to "return generated keys" as it considered statement as already having returning keyword PR#824 201daf1d
• Replication API: fix issue #834 setting statusIntervalUpdate causes high CPU load PR#835 59236b74
• perf: use server-prepared statements for batch inserts when prepareThreshold>0. Note: this enables batch to use server-prepared from the first executeBatch() execution (previously it waited for prepareThreshold executeBatch() calls) abc3d9d7

Notable changes

• fix: infinite dates might be corrupted when transferred in binary for certain JREs. For instance, 5881610-07-11 instead of infinity.

Notable changes

• fix: data being truncated in setCharacterStream (the bug introduced in 42.0.0) PR#802
• fix: calculation of lastReceiveLSN for logical replication PR#801
• fix: make sure org.postgresql.Driver is loaded when accessing though DataSource interface #768
• feat: support fetching a REF_CURSOR using getObject PR#809
• note: there's no 42.1.0.jre6 due to infinity handling bug. Fixed in 42.1.1.jre6

Notable changes

• BUG: setCharacterStream truncates data. The bug is fixed in 42.1.0
• BUG: no suitable driver found for jdbc:postgresql when using a DataSource implementation. The bug is fixed in 42.1.0
• Support for PostgreSQL versions below 8.2 was dropped
• java.util.logging is now used for logging: logging documentation
• Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0 (see issue 742)
• Replication protocol API was added: replication API documentation, GitHub PR 550
• Version bumped to 42.0.0 to avoid version clash with PostgreSQL version
• Error position is displayed when SQL has unterminated literals, comments, etc (see issue 688)

You may have noticed the change in the versioning of the driver, you can read the FAQ for more information.