Lately I saw many cases when users specified option
--base64-output=DECODE-ROWS
to print out a statement representation of row events in MySQL binary logs just to get nothing. Reason for this is obvious: option
--base64-output=DECODE-ROWS
does not convert row events into its string representation, this is job of option
--verbose
. But why users mix these two options so often? This blog post is result of my investigations.
There are already two great blog posts about printing row events on the Percona blog: “Debugging problems with row based replication” by Justin Swanhart and “ …
[Read more]