fix(postgresql): traverse PITR history-only archives - #3404
Draft
weicao wants to merge 2 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## easton/pg-pitr-restore-current-history #3404 +/- ##
======================================================================
Coverage 0.00% 0.00%
======================================================================
Files 195 195
Lines 28397 28405 +8
======================================================================
- Misses 28397 28405 +8 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
weicao
marked this pull request as draft
August 17, 2026 03:44
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.
What
Remove the directory-level latest-WAL shortcut and rely on sorted, exact per-object filtering during PITR archive traversal.
Why
A directory containing only required timeline-history metadata was skipped because the history basename sorted below the start WAL. Fetch returned success without downloading the metadata.
Tests
dc172e1a1: Bash 3.2 focused, 19 examples / 1 failure / 2 assertions