Bug #83619 PITR instructions using binary mode would not work if binary log contains '\0'
Submitted: 31 Oct 2016 9:20 Modified: 7 Nov 2016 14:16
Reporter: Sveta Smirnova (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.5, 5.6, 5.7, 8.0 OS:Any
Assigned to: CPU Architecture:Any

[31 Oct 2016 9:20] Sveta Smirnova
Description:
If mysqlbinlog parses binary log containing '\0' resulting SQL cannot be read by mysql command line client unless option --binary-mode specified. However PITR instructions do not cover this case: https://dev.mysql.com/doc/refman/5.6/en/point-in-time-recovery.html

How to repeat:
See https://bugs.launchpad.net/percona-server/+bug/1610144

Suggested fix:
Add option --binary-mode for examples with mysql command line client or, at least, mention this option in "Warning" box.
[31 Oct 2016 13:13] Chiranjeevi Battula
Hello Sveta,

Thank you for the bug report.

Thanks,
Chiranjeevi.
[7 Nov 2016 14:16] Paul DuBois
Posted by developer:
 
Added note to point out when --binary-mode is needed.