Repository navigation
build(deps-dev): bump postgresql from 42.3.5 to 42.4.1 - #15
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [postgresql](https://github.com/pgjdbc/pgjdbc) from 42.3.5 to 42.4.1. - [Release notes](https://github.com/pgjdbc/pgjdbc/releases) - [Changelog](https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md) - [Commits](pgjdbc/pgjdbc@REL42.3.5...REL42.4.1) --- updated-dependencies: - dependency-name: org.postgresql:postgresql dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Author
|
Superseded by #16. |
dependabot
Bot
deleted the
dependabot/maven/org.postgresql-postgresql-42.4.1
branch
August 18, 2022 18:52
astubbs
added a commit
that referenced
this pull request
Aug 25, 2026
… wedged poller is fatal at a backstop The code review's two remaining P1s, both on the sync lane's liveness. The deadlock (review finding #3, found independently by two reviewers): the control thread waited for a commit response while holding the commitCommand monitor for the whole cycle, and the broker-poll thread's onPartitionsRevoked blocked acquiring that same monitor - so the only thread that can produce the response could never run. Pre-branch the waiter's local deadline broke the cycle fatally in ~10s; this branch had removed that deadline, leaving no exit at all. Two composed fixes: - The monitor becomes a ReentrantLock (commitCycleLock) guarding exactly what the monitor guarded - the cycle and the command flag together, so a commit command can still only be placed between attempts. The revocation path is the one caller that may only ever tryLock (#29's own rule): on contention it declines with a WARN and defers, offsets stay dirty and travel to the new assignee. - commitAndWait gains a last-resort backstop at 4x offsetCommitTimeout + 60s: a poll thread that is alive but has serviced nothing for that whole window is wedged outside the commit path, commit state is unverifiable, and that is fatal - explicitly NOT the seam's budget exhaustion, which produces typed responses. The affirmative wait remains primary; merely-slow pollers are still waited out. The escalation clock (finding #4): deferral streaks escalated to the handler once they outlived offsetCommitTimeout - default 10 SECONDS - so the DEFAULT shutDown() handler killed instances during ordinary slow-but-healthy rebalances that pre-seam survived on WARNs, and each shutdown seeded the next rebalance. This overrides the plan's settled offsetCommitTimeout quantum, recorded at the declaration: the escalation clock is now rebalance-scale (5 minutes, parity with Kafka's default max.poll.interval.ms, test seam per the longPollTimeout precedent). Deferrals still WARN every cycle, never count as success, and clear on a real commit or assignment change. Also resolves the SpotBugs EI_EXPOSE_REP2 thread on CommitResponse (finding #15) with a justification comment - the payload is effectively immutable and the type is a package-internal single-producer channel; no annotations dependency exists to suppress with. Three new regression tests pin the fixes (revocation-declines, wedged-poller backstop, streak-outliving-budget-but-not-bound never escalates), each written to fail with the fix reverted; the four existing escalation scenarios drive the new bound through its test seam. Full core unit suite 448/448, all gates green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016jCtV2yqQvxDR6cLML8J8a
This file contains hidden or 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
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.
Bumps postgresql from 42.3.5 to 42.4.1.
Release notes
Sourced from postgresql's releases.
Changelog
Sourced from postgresql's changelog.
... (truncated)
Commits
bd91c4cPrepare for release (#2580)739e599Merge pull request from GHSA-r38f-c4h4-hqq2736f959fix: replace syncronization in Connection.close with compareAndSet4673fd2feat: synchronize statement executions (e.g. avoid deadlock when Connection.i...fd31a06update the website content (#2578)a6044d0set a timeout to get the return from requesting SSL upgrade. (#2572)58d6fa0test: bump system-stubs-jupiter to 2.0.1 to support Java 16+b452d8ctest: avoid concurrent executions of tests that update environment and system...aa5758atest: update JUnit to 5.8.236cd24cfix: log connection URL when it can't be parsedDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)