…5.5.20. With this release we make clustering very easy and affordable for everyone. You can convert your existing MySQL replication… not block operations against table This is an General…replication overhead Percona Server 5.5.15 + Galera 21.1-beta2 State of the art: Galera – synchronous replication…
Post: How FLUSH TABLES WITH READ LOCK works with Innodb Tables
March 23, 2012 By 20 Comments
…look at what the problem is. As of MySQL 5.5 FLUSH TABLES WITH READ LOCK does not work as optimally … | localhost | NULL | Query | 681 | Waiting for table flush | flush tables with read lock | 0 | 0 | 1 | | 10291 | root | localhost | dumptest | Query…the slave can be done by simply pausing replication…
Post: InnoDB's gap locks
March 27, 2012 By 15 Comments
…, regardless other session modifications on that table. This makes reads consistent and therefore makes the replication between servers consistent. If you execute… source of information: http://dev.mysql.com/doc/refman/5.1/en/innodb-locks-set.html. Conclusion MySQL uses REPEATABLE READ as the default…
Post: Percona Server 5.1.60-13.1
December 16, 2011 By Leave a Comment
…MySQL 5.1.60, including all the bug fixes in it, Percona Server 5.1.60-13.1 is now the current stable release in the 5.1…5.1.60-13.1 milestone at Launchpad. Bug Fixes SHOW SLAVE STATUS could give incorrect output with master-master replication…CREATE INDEX and ALTER TABLE performance. Bug Fixed: #…
Post: Percona Server 5.1.58-12.9
August 17, 2011 By 2 Comments
… Percona Software Repositories). Based on MySQL 5.1.58, including all the bug fixes in it, Percona Server 5.1.58-12.9 is now… from MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL bug (#27877) introduced an incompatible change in collations in MySQL 5.1… close another if the table cache is full. If the closed table was on the FEDERATED engine and a replication environment, its client…
Post: Percona Server 5.1.59-13.0
October 16, 2011 By Leave a Comment
… Based on MySQL 5.1.59, including all the bug fixes in it, Percona Server 5.1.59-13…5.1.59-13.0 milestone at Launchpad. New Features InnoDB Fake Changes When restarting a slave server in a replication…(Alexey Kopytov). Bugs Fixed InnoDB requires a full table rebuild for foreign key changes. This …
Post: Can MySQL temporary tables be made safe for statement-based replication?
May 26, 2008 By 8 Comments
… tables. Thus, I claimed, there’s no alternative but to eliminate temporary tables. This problem may not exist for row-based replication in MySQL 5.1… of are using statement-based replication, even on MySQL 5.1 This is a contentious topic. People love their temporary tables and will ask hopefully…
Post: Upgrading MySQL
January 5, 2010 By 23 Comments
…. MySQL always was very good maintaining on disk binary compatibility between version and so you can run MySQL 5.0 database with MySQL 5.1 with no problems in most cases. When storage type changes, such as DECIMAL field got whole another meaning in MySQL 5.0 MySQL… MySQL Replication for upgrade. Once you have setup slave with new version and made it to caught up you can use mk-table…
Post: Percona Server 5.5.14-20.5
August 17, 2011 By 4 Comments
… MySQL 5.5.14, including all the bug fixes in it, Percona Server 5.5.14-20.5 is now the current stable release in the 5.5… from MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL bug (#27877) introduced an incompatible change in collations in MySQL 5.1… close another if the table cache is full. If the closed table was on the FEDERATED engine and a replication environment, its client…
Post: Getting History of Table Sizes in MySQL
December 8, 2010 By 13 Comments
… INFORMATION_SCHEMA.TABLES” Though if you’re looking to keep it completely inside MySQL you can create appropriate event in MySQL 5.1+ Unless you’re having millions of tables this is something you… Master only. If you use statement based replication it will automatically pick up sizes and even different tables on master and slave.
