MySQL Bugs: #56155: 'You cannot 'ALTER' a log table if logging is enabled' even if I log to files

Bug #56155	'You cannot 'ALTER' a log table if logging is enabled' even if I log to files
Submitted:	20 Aug 2010 19:15	Modified:	27 Sep 2012 8:30
Reporter:	Sveta Smirnova	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Logging	Severity:	S3 (Non-critical)
Version:	5.1, 5.6.99 bzr	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
If slave has logging turned on and logs to file and on master mysql_upgrade run without option to skip writing to binary log replication breaks.

This is not good, because logging goes not to tables, but to files and tables should not be used.

There are related Bug #43579 where --write-binlog and --skip-write-binlog options were introduced and Bug #39133 where user logs to table, but would be reasonable if replication is not affected if logging to file used.

How to repeat:
$cat rpl_issue50169.test 
--source include/master-slave.inc

--exec  $MYSQL_UPGRADE --force >/dev/null

sleep 1;
connection slave;
--vertical_results
show slave status;

$cat rpl_issue50169-slave.opt 
--log-output=FILE

Suggested fix:
Allow to modify log tables if mysqld logs to files.

Fixed in trunk, currently tagged 5.7.0.

Closed.

Bug#69953 was closed as a duplicate of this bug.