-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix re-sync from bad position #414
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
Conversation
…from more_patch to master * commit '508a49d838caa77b4144249ae3cee11c6d06ac7b': Fix crash
Thanks @ianzapolsky CI failed. |
if err != nil { | ||
return errors.Trace(err) | ||
if b.currGset == nil { | ||
gset, err := ParseGTIDSet(MySQLFlavor, u.String()) |
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.
here b.currGset
is a single gtid, not a full gtid set, right?
} | ||
case *XIDEvent: | ||
b.prevGset = b.currGset.Clone() |
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.
as ditto comment, b.currGset
would miss some gtids
event.GSet = b.getGtidSet() | ||
case *QueryEvent: | ||
b.prevGset = b.currGset.Clone() |
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.
b.currGset
may be nil, is it better to add a function like getGitdSet
ping @ianzapolsky , thanks for your pr, please fix CI |
BTW, please also fix the issue does this still have a problem with the
Originally posted by @amyangfei in #416 |
…ed transaction from the beginning this is another stab at issues go-mysql-org#414 and go-mysql-org#416
thanks @ianzapolsky I will close this PR. |
…pted transaction (go-mysql-org#420) * on reconnect in the middle of transaction make sure to read interrupted transaction from the beginning this is another stab at issues go-mysql-org#414 and go-mysql-org#416
This pull request fixes an issue where siddontang skips a transaction when re-connecting to the database after its connection is severed.