Add multi-protocol support for rolling upgrades for v5.0.x -> v6.0.0 #276
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.
This change implements protocol version negotiation to enable rolling upgrades from Spock v5.0.0 through v6.0.0 without breaking replication.
Protocol 4 (v5.0.0-5.0.4): remote_insert_lsn at end of COMMIT only
Protocol 5 (v6.0.0+): remote_insert_lsn at beginning of all messages
(v5.0.5+): Same as v6.0.0, once backported.
Key changes: