forked from zalando/spilo
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choose WAL-G backup by start time when cloning and deleting #1
Closed
simonklb
wants to merge
8
commits into
elastisys:ol/3.0-p1-extras
from
simonklb:simonklb/choose-backup-by-start-time
Closed
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
a4f11b0
Choose WAL-G backup by start time when cloning
simonklb 30b4d13
Use wal-g delete retain to clean up old backups
simonklb 8416ba1
tmpfix
simonklb 65a49d7
Revert "tmpfix"
simonklb c8fcca2
Bump wal-g v3.0.3
simonklb 899bc94
Conform with upstream changes
simonklb 272fbf1
Pick base backup based on finish_time instead of start_time
simonklb c788be7
Another upstream change required for WAL-G v3
simonklb File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Simon, should this be
finish_time
instead ofstart_time
of the backup to compare with therecovery_target_time
? Postgres requires that the recovery target "must be after the ending time of the base backup" (https://www.postgresql.org/docs/13/continuous-archiving.html).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for bringing this up!
The rational behind picking
start_time
overfinish_time
is that one backup might have been started first but finished second. I'm actually not sure how likely parallel backups are, if they are possible at all. Please let me know if you know more on this matter!Either way, after having read the documentation you linked to I think you are absolutely correct. It does not make sense to pick a base backup that has not yet finished before the "recovery target".
272fbf1