feat(pitr): add command to fetch recovery window of a database - #1249
Merged
matthieu526-scalingo merged 2 commits intoAug 13, 2026
Merged
Conversation
matthieu526-scalingo
marked this pull request as ready for review
August 13, 2026 08:40
matthieu526-scalingo
requested review from
SCedricThomas and
curzolapierre
and removed request for
a team
August 13, 2026 08:40
SCedricThomas
requested changes
Aug 13, 2026
Contributor
There was a problem hiding this comment.
We will need a proper release before merging my bad
Contributor
Author
There was a problem hiding this comment.
I know, this is still tracked in the description 😄
matthieu526-scalingo
deleted the
feat/STORY-4094/add-recovery-window-command
branch
August 13, 2026 09:25
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
2 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.
Add a new command to get the recovery window for a given DB.
Basic QA on staging done on the 13/08.
I am curious about why the recovery window is not now, maybe there was no new data at all in the DB.