Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0.20
-
Component/s: Replication
-
Labels:
Description
The mysqlbinlog utility currently shipped with MariaDB has several issues, such as:
- The following bug is not fixed: mysqlbinlog -v does not properly decode DECIMAL values in an RBR log (https://bugs.mysql.com/bug.php?id=65812)
- New features such as --raw and --follow haven't been ported
MariaDB users can't always use the Oracle MySQL binary as a workaround, as it doesn't support MariaDB GTIDs.
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
MDEV-8713 Add continuous binary log backup to mysqlbinlog
-
- Open
-
- links to
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Sorry, for some reason I didn't name this option correctly. There are two options which allow to read from remote servers: read-from-remote-master and read-from-remote-server.
The option which allows to tail the log is stop-never
https://mariadb.atlassian.net/browse/MDEV-4989 is also a must-have. Suggest to upgrade priority to Major.
Maybe it should be split into two issues, the bug to be fixed in 10.0 and the features to be added in 10.1 or 10.2 – I'll leave it to Kristian to decide.
It happened on its own, Chris Calender filed a feature request for binlog options, so lets track it there, and this issue will remain a bug report for the upstream bug. The bug was fixed in 5.6.16.
Oleksandr Byelkin, can you backport the upstream bugfix, please?
Guillaume Lefranc, what is the --follow option? I would expect it's something similar to tail -f, but can't find it in the MySQL manual.