Bug #73625 | Strange error message for incompatible gtid options for mysqlbinlog | ||
---|---|---|---|
Submitted: | 18 Aug 2014 14:54 | Modified: | 28 Aug 2014 11:25 |
Reporter: | Sven Sandberg | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[18 Aug 2014 14:54]
Sven Sandberg
[28 Aug 2014 11:25]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. Documented fix in the MySQL 5.7.5 changelog as follows: Misleading or confusing error messages have been revised, which were produced in the following 2 cases when using mysqlbinlog with the --raw option: When this option was used together with --include-gtids. When this option was used together with --exclude-gtids and --read-from-remote-master=BINLOG-DUMP-NON-GTIDS. Closed. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html