Pg10 xlog to wal #73
Open
Pg10 xlog to wal #73
Conversation
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
Contributor
Author
|
HI, Is there any chance of you merging this in? I have some other postgres 10 compatibility changes that I want to make and it would be nice to get this closed out first. All the best |
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.
Hi,
I have added the code to allow the wal replay to be paused and restarted on postgres version 10 and up.
This problem was caused by the renaming of the pg_xlog_replay_pause(), pg_xlog_replay_resume() and pg_is_xlog_replay_paused() functions to pg_wal_replay_pause(), pg_wal_replay_resume() and pg_is_wal_replay_paused().