This was "fixed" for upstream in frames of https://bugs.mysql.com/bug.php?id=43579 by adding --[skip]-write-binlog option. There is this closed feature request also, http://bugs.mysql.com/bug.php?id=56155, that covers current case and it's implemented in 5.7.x.
It seems we have to "backport" fix from MySQL 5.7 to PS 5.5 (and 5.6, for the case when upgrade writes to the binary log, but logging on slave). ** Bug watch added: MySQL Bug System #43579 http://bugs.mysql.com/bug.php?id=43579 ** Bug watch added: MySQL Bug System #56155 http://bugs.mysql.com/bug.php?id=56155 ** Changed in: percona-server/5.5 Status: New => Confirmed ** Changed in: percona-server/5.6 Status: New => Confirmed ** Also affects: mysql-server via http://bugs.mysql.com/bug.php?id=56155 Importance: Unknown Status: Unknown ** Tags added: upstream -- You received this bug notification because you are a member of Ubuntu Server/Client Support Team, which is subscribed to MySQL. Matching subscriptions: Ubuntu Server/Client Support Team https://bugs.launchpad.net/bugs/1441362 Title: mysql_upgrade binlogs queries that fail on master To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1441362/+subscriptions -- Mailing list: https://launchpad.net/~enterprise-support Post to : [email protected] Unsubscribe : https://launchpad.net/~enterprise-support More help : https://help.launchpad.net/ListHelp
