mysql_upgrade should default to --skip-write-binlog | Replication breaks with "You cannot 'ALTER' a log table if logging is enabled" on upgrade, even when logging to files
Bug #1065841 reported by
Marcus Bointon
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
High
|
Unassigned | |||
5.5 |
Fix Released
|
High
|
Laurynas Biveinis | |||
5.6 |
Fix Released
|
High
|
Unassigned | |||
5.7 |
Fix Released
|
High
|
Unassigned |
Bug Description
I get this error every time I upgrade MySQL on my servers.
This error is described in various MySQL bug reports dating back several years, for example http://
I generally work around it by telling slaves to skip that query and carry on, but it does mean that upgrades break replication.
To be clear, I am not logging to tables and never have!
tags: | added: upstream |
summary: |
- Replication breaks with "You cannot 'ALTER' a log table if logging is - enabled" on upgrade, even when logging to files + mysql_upgrade should default to --skip-write-binlog | Replication breaks + with "You cannot 'ALTER' a log table if logging is enabled" on upgrade, + even when logging to files |
To post a comment you must log in.
Hm, and of course on the upgrade to 5.5.27-29, it didn't happen after all...
I guess you can close this one now!