Bug #17521 | alter database cores slave | ||
---|---|---|---|
Submitted: | 17 Feb 2006 9:55 | Modified: | 27 Feb 2006 20:48 |
Reporter: | Tomas Ulin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
Version: | 5.1.7 bk src | OS: | |
Assigned to: | Elliot Murphy | CPU Architecture: | Any |
[17 Feb 2006 9:55]
Tomas Ulin
[17 Feb 2006 9:58]
Tomas Ulin
looked at master though seems to be a missing use <database>; in the binlog show binlog events; | master-bin.000001 | 102 | Query | 1 | 198 | alter database collate latin1_bin |
[23 Feb 2006 21:16]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/3086
[24 Feb 2006 4:20]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/3095
[24 Feb 2006 4:35]
Elliot Murphy
Reviewed by mats and lars. Problem was that slave was not using the default database name in the replication filtering rules when receiving an ALTER DATABASE command which did not specify a database. Now correctly uses the default db when db is not specified. Fix has been pushed into the 5.1.7 release clone.
[27 Feb 2006 20:48]
Mike Hillyer
Documented in 5.1.7 changelog: <listitem> <para> An <literal>ALTER DATABASE</literal> statement on a replication master crashed the slaves. (Bug #17521) </para> </listitem>