Update dependency org.postgresql:postgresql to v42.3.3 #26
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.2.5
->42.3.3
By merging this PR, the issue #2 will be automatically resolved and closed:
Release Notes
pgjdbc/pgjdbc (org.postgresql:postgresql)
v42.3.3
Changed
They can no longer be used to configure the driver logging. Instead use java.util.logging
configuration mechanisms such as
logging.properties
.Added
Fixed
v42.3.2
Security
sslhostnameverifier, socketFactory, sslfactory, sslpasswordcallback connection properties.
However, the driver did not verify if the class implements the expected interface before instantiating the class. This
would allow a malicious class to be instantiated that could execute arbitrary code from the JVM. Fixed in commit
Changed
is prefer or require PR #2396 remove the need to have a ticket in the cache before asking the server if gss encryptions are supported
or JDBC 4.2.
CallableStatement#getBoolean(int) on BIT(>1).
Changes internal constructors for PgConnection and related classes to only accept the connection properties object and
remove the user and password arguments. Any locations that required those fields can retrieve them from the properties map.
Added
Adds authenticationPluginClassName connection property that allows end users to specify a class
that will provide the connection passwords at runtime. Users implementing that interface must
ensure that each invocation of the method provides a new char[] array as the contents
will be filled with zeroes by the driver after use.Call sites within the driver have been updated to use the char[] directly wherever possible.
This includes direct usage in the GSS authentication code paths that internally were already converting the String password into a char[] for internal usage.
This allows configuring a connection with a password that must be generated on the fly or periodically changes. PR #2369 original issue Issue #2102
Fixed
fixes Issue #921 synchronize modification of shared calendar
resultSet.getTimestamp() only ms precision is retained, the microsecond fractional digits are lost." This change will retain the microsecond
precision when .getTimestamp() is called on TIME(6). PR #2181 Closes Issue #1537
Add to TestUtil and also to DatabaseMetaData setup and teardown fixes Issue #2060
OutOfMemoryException
=>OutOfMemoryError
safety TimestampUtil is not thread safe. It raises exceptions when multiple threads use ResultSets of one connection. PR #2291
fixes Issue #921
If PgStatement and PgResultSet use their own TimestampUtil no synchronize is needed.
v42.3.1
Changed
multi-dimensional array the one exception is byte[], which is not supported.
improve the parsing of bytea hex encoded string by making a lookup table for each of the valid ascii code points to the 4 bit numeric value
Added
Fixed
binary numeric values which represented integers multiples of 10,000 from 10,000-9,990,000 were not decoded correctly
Greagorian
toGregorian
.v42.3.0
Changed
Added
Resource can be provided using 1) property "-Dorg.postgresql.pgservicefile=file1" 2) environment variable PGSERVICEFILE=file2 3) default location "$HOME/.pg_service.conf" 4) environment variable PGSYSCONFDIR=dir1 looks for file "dir1/pg_service.conf".
Fixed
Add a property
QUOTE_RETURNING_IDENTIFIERS
which determines if we put double quotesaround identifiers that are provided in the returning array.
v42.2.24
Fixed
Avoid leaking server error details through BatchUpdateException when logServerErrorDetail PR #2254
QueryExecutorImpl.receiveFastpathResult did not properly handle ParameterStatus messages.
This in turn caused failures for some LargeObjectManager operations. Closes Issue #2237
Fixed by adding the missing code path, based on the existing handling in processResults. PR #2253
It is possible to break method PgDatabaseMetaData.getIndexInfo() by adding certain custom operators. This PR fixes it.
use older syntax for COMMENT ON FUNCTION with explicit no-arg parameter parentheses as it is required on server versions before v10.
Handle cleanup of connection creation in StatementTest, handle cleanup of privileged connection in DatabaseMetaDataTest
fixes issues introduced in PR #2199 closes Issue #2196
v42.2.23
Changed
Fixed
This does not have the issue of name shadowing / qual-names, and has the added benefit of fixing #1948.
v42.2.22
Fixed
due to the blocking nature of the driver and issues with seeing if there is a byte available on a blocking stream when it is encrypted
this introduces unacceptable delays in returning from peek(). At this time there is no simple solution to this.
v42.2.21
Changed
Fixed
fixes Issue 2173
v42.2.20
Fixed
The usage of
setQueryTimeout();
with the same value as thesetNetworkTimeout();
is blocking the current transaction timeout.The timeouts are blocking each other with this approach.
v42.2.19
Notable Changes
Changed
There is a small behaviour change here as a result. If closeOnCompletion is called on an existing statement and the statement
is executed a second time it will fail.
Added
Fixed
v42.2.18
Fixed
fixed in #1920
v42.2.17
Changed
Added
Fixed
v42.2.16
Known issues
Fixed
Since 42.2.0 single dimensional arrays were stored 0 based. They are now sent 1 based which is the SQL standard, and the default
for Postgres when sent as strings such as '{1,2,3}'. Fixes issue 1860 in PR 1863.
v42.2.15
Known issues
Changed
postgresql-$version-jdbc-src.tar.gz
, and add top-level archive folder ba017507are possible. Now the driver will attempt to connect to the server with a GSSAPI encrypted connection. If that fails then
attempt an SSL connection, finally falling back to a plain text connection. All of this is controlled using both the gssEncMode
and sslMode parameters which, in concert with pg_hba.conf, determine if a particular mode is allowed and or required. PR 1821 ad921b9e
Added
Fixed
v42.2.14
Changed
v42.2.13
Notable Changes
Reported by David Dworken, this is an XXE and more information can be found here.
Sehrope Sarkuni reworked the XML parsing to provide a solution in commit 14b62aca4.
Changed
Added
Fixed
procedures fixed in PR 1774
v42.2.12
Notable changes
We have released 42.2.12 to correct regressions in this version: Specifically
We recommend that version 42.2.11 not be used.
Changed
This change introduced a breaking change which will be moved to 42.3.0
v42.2.11
Notable changes
As mentioned above this version is broken and should not be used.
Changed
DatabaseMetaData#getProcedures
returns only procedures (not functions) for PostgreSQL 11+ PR 1723commit
orxa.prepare
command PR 1729Added
raiseExceptionOnSilentRollback
connection option to configure if silent rollback should raise an exception PR 1729ByteStreamWriter
in CopyManager PR 1702Fixed
.
as decimal separator in PGInterval PR 1705Changed
Added
docker
folder)v42.2.10
Changed
Added
Fixed
v42.2.9
Changed
Added
Fixed
v42.2.8
Changed
Added
Fixed
v42.2.7
Changed
Added
Fixed
v42.2.6
Known issues
Changed
Added
to allow a consistent snapshot in some uses cases. PR 1335
Fixed