Upgrade PostgreSQL JDBC 42.3.6 -> 42.6.0 - autoclosed #264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
42.3.6
->42.6.0
42.3.6
->42.6.0
Release Notes
pgjdbc/pgjdbc (PostgreSQL JDBC)
v42.6.0
Changed
fix: use PhantomReferences instead of
Obejct.finalize()
to track Connection leaks PR #2847refactor:(loom) replace the usages of synchronized with ReentrantLock PR #2635
Fixes Issue #1951
v42.5.4
Fixed
fix: fix testGetSQLTypeQueryCache by searching for xid type. We used to search for box type but it is now cached. xid is not cached, this nuance is required for the test.
fix OidValueCorrectnessTest BOX_ARRAY OID, by adding BOX_ARRAY to the oidTypeName map [PR #2810](https://github.com/pgjdbc/pgjdbc/pull/28100).
fixes Issue #2804.
fix: Make sure that github CI runs tests on all(https://togithub.com/pgjdbc/pgjdbc/pull/2809)dbc/pgjdbc/pull/2809\)).
v42.5.3
Fixed
fix: Add box to TypeInfoCache, fixes Issue #2746 PR #2747
fix: regression in PgResultSet LONG_MIN copy and paste error fixes Issue #2748 PR#2749
v42.5.2
Changed
regression: This release has 2 known regressions which make it unusable see the notes above. We advise people to use 42.5.3 instead.
docs: specify that timeouts are in seconds and there is a maximum. Housekeeping on some tests fixes #Issue 2671 PR #2686
docs: clarify binaryTransfer and add it to README PR# 2698
docs: Document the need to encode reserved characters in the connection URL PR #2700
feat: Define binary transfer for custom types dynamically/automatically fixes Issue #2554 PR #2556
Added
fix: added gssResponseTimeout as part of PR #2687 to make sure we don't wait forever on a GSS RESPONSE
Fixed
fix: Ensure case of XML tags in Maven snippet is correct PR #2682
fix: Make sure socket is closed if an exception is thrown in createSocket fixes Issue #2684 PR #2685
fix: Apply patch from Issue #2683 to fix hanging ssl connections PR #2687
fix - binary conversion of (very) long numeric values (longer than 4 * 2^15 digits) PR #2697 fixes Issue #2695
minor: enhance readability connection of startup params PR #2705
v42.5.1
Security
This has been fixed in this version fixes CVE-2022-41946 see the security advisory for more details. Reported by Jonathan Leitschuh This has been fixed in versions 42.5.1, 42.4.3 42.3.8, 42.2.27.jre7. Note there is no fix for 42.2.26.jre6. See the security advisory for work arounds.
Fixed
v42.5.0
Changed
float now aliases to float8 PR #2598 fixes Issue #2597
v42.4.2
Changed
Added
Fixed
v42.4.1
Security
SQL. This allowed a malicious table with column names that include statement terminator to be parsed and
executed as multiple separate commands.
Changed
Added
v42.4.0
Changed
startup parameters in a transaction (default=false like 42.2.x) fixes Issue #2425
pgbouncer cannot deal with transactions in statement pooling mode PR #2425
Fixed
PR #2525, Issue #1311
Regression since 42.2.13. PR #2531, issue #2527