Support multiple GTIDs in MariaDB GTIDSets#4360
Merged
sougou merged 2 commits intovitessio:masterfrom Nov 15, 2018
Merged
Conversation
b13bc5e to
601da18
Compare
Signed-off-by: Michael Hebelka <michael.hebelka@sharpspring.com>
601da18 to
820e1c1
Compare
Signed-off-by: Michael Hebelka <michael.hebelka@sharpspring.com>
cfee051 to
99199c2
Compare
sougou
approved these changes
Nov 15, 2018
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
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 current GTIDSet implementation for MariaDB doesn't properly support MariaDB GTIDs - a
gtid_slave_posof, for example,1-1-141129273,2-2-3551534,3-3-805048is not supported. This consequently breaks (at the very least) the replication reporter.