Bug #47543 add option --skip-write-binlog for mysql_upgrade to pass on to mysqlcheck
Submitted: 23 Sep 2009 9:19 Modified: 22 Oct 2009 6:43
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S4 (Feature request)
Version:5.1, 5.4 OS:Any
Assigned to: CPU Architecture:Any

[23 Sep 2009 9:19] Shane Bester 
Description:
this is a feature request to enable mysql_upgrade to take an option --skip-write-binlog and run then mysqlcheck with that option.

the reason is tables are repaired, we don't want these to be replicated to slaves.

How to repeat:
.
[23 Sep 2009 9:25] Valeriy Kravchuk 
Thank you for the feature request.
[23 Sep 2009 11:23] Simon Mudd 
The real point for this request is that in a replicated environment it's possible that the master and slaves are running a different version of the server. Often the slaves are updated first and the master at the end so it will never be obvious whether or not the operations intended on the master should be replicated to the slave.

Perhaps the default behaviour should be to ensure that the commands are NOT replicated and if they are needed an explicit option to replicate them should be added. It seems safer that way as also changes are made to the system (mysql database tables) and these changes may too cause unintended behaviour on a slave.

Also please ensure that any change and the reason for it are clearly documented and also that msyql_upgrade is very clear about what it is doing.
[22 Oct 2009 6:43] MySQL Verification Team 
turns out this was a duplicate of bug #43579