WAL checkpoint mode: PASSIVE vs TRUNCATE on close
Cluster 80255. Data as of
Nothing open on GitHub. Fix merged in #84881 on 13 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #84881. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #84881. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members concern the use of TRUNCATE instead of PASSIVE checkpoint mode when closing or vacuuming a shared-DB WAL, including a reported recurrence on the shutdown path and corresponding fixes.
Open issues0
Open PRs0
Fixes on record
-
#84881 fix(state): PASSIVE not TRUNCATE for all shared-DB WAL checkpoints
files:
contributors/emails/[redacted:email],hermes_cli/kanban_db.py,hermes_state.py,hermes_state_search.py,tests/hermes_cli/test_kanban_db_repair.py,tests/test_hermes_state.py,tests/test_wal_checkpoint_strategy.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#80346 fix(session): use PASSIVE wal checkpoint on close and pre-VACUUM · superseded by another PR →
#84277,#80255
Closed issues · 1
- Closed#80255close() still uses TRUNCATE checkpoint — #45383 recurs on the shutdown path
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #84881
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 13 Aug 2026