June 18, 2013

Post: Filtered MySQL Replication

… big fan of filtered or partial MySQL Replication (as of version MySQL 5.0) – there is enough gotchas with replication itself and getting things right with… traditional pre MySQL 5.0 way to break such replication is also using multi-table update or delete statements, if you happen to replicate one table… Filtered Replication can work pretty well for you. P.S It is in my todo to see how well MySQL 5.1 row based replication

Post: Announcing Percona Server for MySQL version 5.5.29-30.0

MySQL version 5.5.29-30.0 on February 26th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5statement containing BLOB values for a compressed table. This regression was introduced in Percona Server 5.5… in the replicate-ignore-table. Bug fixed…

Post: InnoDB's gap locks

… phantom reads and to get a consistent Statement based replication. To accomplish that, row level locking databases… OK, 1 row affected (0.00 sec) After running the delete statement on the first session,…: http://dev.mysql.com/doc/refman/5.1/en/innodb-locks-set.html. Conclusion MySQL uses REPEATABLE…

Post: Top 5 Wishes for MySQL

MySQL Cluster would ever be that thing as it provides too strong guarantees. It is same as with MySQL ReplicationStatements is only fixed in MySQL 5MySQL I have created more than hundred of such little projects suggested by MySQL customers and myself based on long MySQL

Post: High-Performance Click Analysis with MySQL

… too, assuming you use statement-based replication. You can save that work by either using MySQL 5.1′s row-based replication, or in MySQL 5.0 and earlier, doing… master with LOAD DATA INFILE, which kind of emulates row-based replication in a way. When you’re updating big aggregate tables…

Post: READ-COMMITED vs REPETABLE-READ in tpcc-like load

… row level having small dataset. I used as usually tpcc-mysql benchmark with 16 and 32 (for 10w) concurrent users. Also…-COMMITED does not support STATEMENT based replication in 5.1), and everything was run under XtraDB-9 ( based on InnoDB-plugin 1.0.6) So there…), that is less-tested READ-COMMITED does not work with statement-based replication in 5.1 with READ-COMMITED you may have more DEADLOCKS

Post: Fighting MySQL Replication Lag

… batch in multiple row insert statement or Fetching data you’re … will perform full table scan in MySQL 5.0 (even if there are no spam… allows it. In MySQL 5.1 with row level replication you will not … hardware purchases or development efforts based on assumption MySQL replication can’t possibly keep…

Post: Percona Server 5.1.52-12.3

… enabled before” was sometimes reported after upgrading from MySQL 5.0. (Yasufumi Kinoyasu) Bug #643463 – Shutting down XtraDB could …based replication was not working correctly. (Oleg Tsarev) Bug #676147 – The development environment test of option log_slow_slave_statements for row-based replication

Post: MySQL Crash Recovery

…. This will sometimes break replication but if you’re …MySQL 5.0 XA is taking care of this synchronization. .frm Corruption – Few people know MySQLstatements. There is a chance of failing for example during CREATE statementbasing my failure handling scenarios. Cold Start – If you restart MySQL

Post: Getting History of Table Sizes in MySQL

… space used on partition is not very helpful. Now as MySQL 5.0+ has information schema collecting and keeping this data is very… among shards etc. In replicated environment you should put this cron on Master only. If you use statement based replication it will automatically pick…