June 19, 2013

Post: Test Drive of Solid

to tell what is really happening. Test 3: Phantom rows: Table before test: select * from test2; +—-+——–+ | id | names | +—-+——–+ | 1 | Mysql | | 2 | Solid | | 3 | MyISAMLOCK IN SHARE MODE) as only actual row versions can be locked. With Innodb we would get “SolidDB2″ as result. mysql

Post: Choosing innodb_buffer_pool_size

to bypass cache for your Innodb tables but there are other things you need OS cache for – MyISAM tables (mysqlto play with. Finally you can try locking MySQL in memory by using –memlock – just be careful as in

Post: Performance impact of complex queries

how it is happening and how to prevent it. Cache Wiping This is first reason for this toMySQL Itself employs various strategies to attempt totables on the slave and when move them to the master using mysqldump, or even careful file transfer if you’re using MyISAM tables

Comment: Pitfalls of converting to InnoDB

MyISAM you were not getting any because it did not support transactions and used only table level locks which had to…because of how data is accessed. If you want to avoid …No there is no option on MySQL level to solve this problem because only application knows what to do in the case of deadlock. In