FAQ for the PostgreSQL JDBC Driver Upgrade

Postgres

...

The same minor changes apply as for AlloyDB, regarding printed value types and typo fixes.

Adjustments to the third listed change in the doc (regarding the scenario of “

...

All scenarios affected by this change are going to have errors roughly in that format - Batch entry 0 <query> was aborted: ERROR: <scenario-specific message> Position: <number> Call getNextException to see other errors in the batch., <error code and SQL state info>, next exception: <same error description and position as before>

Scenarios that could see these kinds of error message changes include (but are not limited to):

...

When the input value provided for a column is invalid for the column type.

...

When performing a delete that references a non-existent column.

...

When using an operator that does not exist or does not match given argument types.

...

When the query references some relation (schema, table, etc.) that does not exist.

...

What is happening?

We plan to upgrade the JDBC driver for the PostgreSQL Snap Pack from v9.4.1207 to v42.7.2 (Java 8). This upgrade will be part of the GA release on August 14, 2024 (Stable release). As a part of this upgrade, the 42.7.2 JDBC driver is bundled with the PostgreSQL Snap Pack as the default JDBC driver.

...

Use the postgres 9.4.1207.jar from v9.4.1207 to maintain the same behavior as before the driver upgrade.

Behavior Changes

• Changes in the query in the error messages:

  • Some error messages will now include the data type for certain values, for example:

    • Old: "...where (badId = 1) was aborted:..."

    • New: "...where (badId = ('1'::numeric)) was aborted:..."

• Improvisations in error messages:

  • There are some minor wording changes to some error messages, for example:

    • Old: "Hint: No operator matches the given name and argument types."

    • New: "Hint: No operator matches the given name and argument type(s)."

...