Draft
Conversation
boddumanohar
force-pushed
the
pitr-restore
branch
3 times, most recently
from
fe8dc85 to
8306b74
Compare
boddumanohar
force-pushed
the
pitr-restore
branch
from
8306b74 to
6f8b13c
Compare
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
1 participant
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.
The behaviour of postgres init is going to be different with PITR. So extracted it into separated script and update the logic.
postgres init
When
WALPVCfolder is available(meaning PITR) is enabled, we explicitly intialise WAL (--waldir=$PGWAL) in that volume.