…. MySQL also has broken group commit (which we have partial fix for) meaning concurrent transaction commits will need to be serialized. Second, MySQL… async nature of MySQL replication is a showstopper) and it also solves the other big pain of semi-online MySQL/OS upgrades and Schema…
Post: MySQL 4 to MySQL 5 Upgrade performance regressions
…performance regression cases when upgrading from MySQL 4.0 and 4.1 to MySQL 5.0. By…MySQL 5.0 broken group commit bug. First I should note I am extremely unhappy how MySQL handled this problem. While working for MySQL…you loose point in time recovery and replication. Use innodb_flush_log_at_trx_commit…
Post: Percona Server 5.1.58-12.9
…upgrading from MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL… upgrade, and unique constrains may get broken after upgrade due to possible duplicates. This problem is avoided when upgrading… was on the FEDERATED engine and a replication environment, its client connection to the remote …
Post: Percona Server 5.5.14-20.5
…upgrading from MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL… upgrade, and unique constrains may get broken after upgrade due to possible duplicates. This problem is avoided when upgrading… was on the FEDERATED engine and a replication environment, its client connection to the remote …
Post: MySQL Master-Master replication manager released
…MySQL Master-Master replication (often in active-passive mode) is popular pattern used by many companies using MySQL… also implemented so restoring broken replication safe way becomes very easy…replication inconsistencies. This is very handy if you want to restart one of servers in clusters to upgrade…
Post: Using MMM to ALTER huge tables
…one of our MySQL support customers as they were upgrading their application and mysql schema. We deployed and used MySQL Master-Master replication manager (MMM…that when replication db2 => db1 is broken, db1 will be available as “writer” and roles stay consistent. 2. on db1: stop replication mysql> …
Post: Percona Server 5.1.52-12.3
… was enabled before” was sometimes reported after upgrading from MySQL 5.0. (Yasufumi Kinoyasu) Bug #643463 – …. (Oleg Tsarev) Bug #673562 – Debug build was broken due a to failing compile-time assertion…=innodb on a slave for row-based replication was not working correctly. (Oleg Tsarev) Bug #676147 …
Comment: Debugging problems with row based replication
…is MySQL and Drizzle. MySQL has a lot of weight with bad choices over many years which can’t be easily broken …they relay on any side effects. They just upgrade Master and Slave to MySQL 5.1 and just expect things work …lot more serious issue than improving things (which row level replication does)
Comment: When should you store serialized objects in the database?
…I’m a little worried that with ‘Broken Window Theory’ that prototype never gets…- thanks for your comments
Josh Berkus cited upgrades as one of the main reasons… my tools I’m used to (mysql cli, etc). I then have to… you for the two additional examples. Replication and messaging systems are both …

