-
Notifications
You must be signed in to change notification settings - Fork 987
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
go-mysqlbinlog: wrong positions for events and Gtid events get decoded as QueryEvent #944
Comments
Decoded events from
And from
|
The reason for MariaDB server to send different events is probably that go-mysqlbinlog didn't send It turns out that I didn't use What we could/should do is;
|
This also now has the corrects log positions |
Server: MariaDB 11.4.2
From
go-mysqlbinlog
:From the client:
Note this event:
Issues:
Log position: 500
: This is not the position of the event as that should be 458. It is the end position of the event.Gtid
event and not aQueryEvent
Query: # Dum
: I think this should have said "Dummy", but that got truncated. But this should probably have hadGTID 0-1-2
instead.Issues with other events:
4.
Gtid_list
is decoded asUserVarEvent
.5.
Binlog_checkpoint
is decoded asQueryEvent
The text was updated successfully, but these errors were encountered: