-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency org.postgresql:postgresql to v42.3.5 #336
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/org.postgresql-postgresql-42.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.2.20
Update dependency org.postgresql:postgresql to v42.2.20 - autoclosed
May 7, 2021
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.2.20 - autoclosed
Update dependency org.postgresql:postgresql to v42.2.20
May 7, 2021
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
May 7, 2021 15:31
8a53fe5
to
746cf3e
Compare
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.2.20
Update dependency org.postgresql:postgresql to v42.2.20 - autoclosed
Jun 1, 2021
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.2.20 - autoclosed
Update dependency org.postgresql:postgresql to v42.2.20
Jun 4, 2021
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
2 times, most recently
from
June 10, 2021 19:40
cddd539
to
e0bdba5
Compare
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.2.20
Update dependency org.postgresql:postgresql to v42.2.21
Jun 10, 2021
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
June 16, 2021 16:14
e0bdba5
to
919a70c
Compare
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.2.21
Update dependency org.postgresql:postgresql to v42.2.22
Jun 16, 2021
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
October 19, 2021 02:50
919a70c
to
474d362
Compare
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.2.22
Update dependency org.postgresql:postgresql to v42.3.0
Oct 19, 2021
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
March 7, 2022 08:14
474d362
to
62c1f22
Compare
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.3.0
Update dependency org.postgresql:postgresql to v42.3.3
Mar 7, 2022
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
April 24, 2022 21:49
62c1f22
to
b42f987
Compare
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.3.3
Update dependency org.postgresql:postgresql to v42.3.4
Apr 24, 2022
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
May 15, 2022 23:39
b42f987
to
21b7053
Compare
renovate
bot
changed the title
Update dependency org.postgresql:postgresql to v42.3.4
Update dependency org.postgresql:postgresql to v42.3.5
May 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.19
->42.3.5
Release Notes
pgjdbc/pgjdbc
v42.3.5
Changed
Added
Fixed
This is a regression from 42.2.x versions where tcpNoDelay defaulted to true
v42.3.4
Changed
and default timezones PR 2464 fixes Issue #2221
Added
Fixed
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.
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.