-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update dependency org.postgresql:postgresql to v42.7.4 #8
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/org.postgresql-postgresql-42.x
base: main
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
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
April 26, 2021 16:43
de7f63a
to
0305ed6
Compare
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.2.19
chore(deps): update dependency org.postgresql:postgresql to v42.2.20
Apr 26, 2021
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.2.20
chore(deps): update dependency org.postgresql:postgresql to v42.2.21
Jun 15, 2021
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
June 15, 2021 01:12
0305ed6
to
560c06c
Compare
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
October 18, 2021 22:00
560c06c
to
903c34d
Compare
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.2.21
chore(deps): update dependency org.postgresql:postgresql to v42.3.0
Oct 18, 2021
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
March 7, 2022 14:08
903c34d
to
ef80fe8
Compare
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.3.0
chore(deps): 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 20:11
ef80fe8
to
a5dc607
Compare
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.3.3
chore(deps): 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:58
a5dc607
to
d899955
Compare
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.3.4
chore(deps): update dependency org.postgresql:postgresql to v42.3.5
May 15, 2022
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
June 18, 2022 20:28
d899955
to
c93bcce
Compare
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.3.5
chore(deps): update dependency org.postgresql:postgresql to v42.4.0
Jun 18, 2022
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
September 25, 2022 15:02
c93bcce
to
4d2927f
Compare
renovate
bot
changed the title
chore(deps): update dependency org.postgresql:postgresql to v42.4.0
fix(deps): update dependency org.postgresql:postgresql to v42.5.0
Sep 25, 2022
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
March 16, 2023 10:00
4d2927f
to
5b1a806
Compare
renovate
bot
changed the title
fix(deps): update dependency org.postgresql:postgresql to v42.5.0
fix(deps): update dependency org.postgresql:postgresql to v42.5.4
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
March 24, 2023 22:12
5b1a806
to
fdd9f77
Compare
renovate
bot
changed the title
fix(deps): update dependency org.postgresql:postgresql to v42.5.4
fix(deps): update dependency org.postgresql:postgresql to v42.6.0
Mar 24, 2023
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
November 21, 2023 20:18
fdd9f77
to
137c639
Compare
renovate
bot
changed the title
fix(deps): update dependency org.postgresql:postgresql to v42.6.0
fix(deps): update dependency org.postgresql:postgresql to v42.7.0
Nov 21, 2023
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
December 7, 2023 05:52
137c639
to
f064346
Compare
renovate
bot
changed the title
fix(deps): update dependency org.postgresql:postgresql to v42.7.0
fix(deps): update dependency org.postgresql:postgresql to v42.7.1
Dec 7, 2023
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
February 21, 2024 05:37
f064346
to
719057f
Compare
renovate
bot
changed the title
fix(deps): update dependency org.postgresql:postgresql to v42.7.1
fix(deps): update dependency org.postgresql:postgresql to v42.7.2
Feb 21, 2024
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
March 15, 2024 02:37
719057f
to
d1d316a
Compare
renovate
bot
changed the title
fix(deps): update dependency org.postgresql:postgresql to v42.7.2
fix(deps): update dependency org.postgresql:postgresql to v42.7.3
Mar 15, 2024
renovate
bot
force-pushed
the
renovate/org.postgresql-postgresql-42.x
branch
from
August 23, 2024 02:50
d1d316a
to
d89fb49
Compare
renovate
bot
changed the title
fix(deps): update dependency org.postgresql:postgresql to v42.7.3
fix(deps): update dependency org.postgresql:postgresql to v42.7.4
Aug 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.18
->42.7.4
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
pgjdbc/pgjdbc (org.postgresql:postgresql)
v42.7.4
Added
Fixed
Deprecated
v42.7.3
Changed
Fixed
else if
toswitch
NoSuchMethodError on ByteBuffer#position
when running on Java 8v42.7.2
Security
SimpleQuery
mode to generate a line comment by having a placeholder for a numeric with a-
such as
-?
. There must be second placeholder for a string immediately after. Setting the parameter to a -ve value creates a line comment.This has been fixed in this version fixes CVE-2024-1597. Reported by Paul Gerste. See the security advisory for more details. This has been fixed in versions 42.7.2, 42.6.1 42.5.5, 42.4.4, 42.3.9, 42.2.28.jre7. See the security advisory for work arounds.
Changed
Added
v42.7.1
Changed
Fixed
Fixes Issue #3008
Fixes Issue #3007
,Issue #2850
Closes [Issue #1391(https://github.com/pgjdbc/pgjdbc/issues/1391)
v42.7.0
Changed
java.desktop
module. PR #2967Fixed
v42.6.0
Changed
fix: use PhantomReferences instead of
Obejct.finalize()
to track Connection leaks PR #2847The change replaces all uses of Object.finalize with PhantomReferences.
The leaked resources (Connections) are tracked in a helper thread that is active as long as
there are connections in use. By default, the thread keeps running for 30 seconds after all
the connections are released. The timeout is set with pgjdbc.config.cleanup.thread.ttl system property.
refactor:(loom) replace the usages of synchronized with ReentrantLock PR #2635
Fixes Issue #1951
v42.5.4
Fixed
v42.5.3
Fixed
v42.5.2
Changed
Added
Fixed
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
v42.3.6
Changed
Added
Fixed
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.
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
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.