test(e2e): add point-in-time recovery (PITR) e2e test with backup plugin#33
Merged
Merged
Conversation
Signed-off-by: ermakov-oleg <ermakovolegs@gmail.com>
Author
|
Hey @Agalin! Friendly ping on the PR when you get a chance. Thanks! 🙏 |
Collaborator
|
Sorry for the delay, we've been really busy this week. Will check it during the weekend. |
Agalin
approved these changes
Oct 12, 2025
Agalin
left a comment
Agalin
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for adding a test for that! I'm also positively surprised it actually works as expected with current implementation, feared it would continue to the last WAL. 🙂
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 end-to-end test for point-in-time recovery (PITR) functionality with the pgBackRest backup plugin.
This test verifies that the plugin can correctly restore PostgreSQL clusters to a specific timestamp, ensuring data consistency and proper WAL replay.