Comment: Pitfalls of converting to InnoDB
… basic problem I’ve found. I’m using PHP 5.1.6, MySQL 5.0.24a default installs from Ubuntu 6.10, so… time-out with a “1205 – Lock wait timeout exceeded; try restarting transaction“. The 1205 error...
View ArticlePost: Test Drive of Solid
…waiting… In 30 sec Session1: ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction…waiting… Session2: mysql> update test2 set names=’mysql2′ where id=1; ERROR 1213 (40001):...
View ArticleComment: InnoDB's gap locks
… tried it with PS 5.5 and default (REPEATABLE READ) isolation mode and the insert is failing mysql> START TRANSACTION; Query OK, 0 rows affected (0.00 sec) mysql> INSERT INTO t VALUES(26); ERROR...
View ArticleIntroducing backup locks in Percona Server
TL;DR version: The backup locks feature introduced in Percona Server 5.6.16-64.0 is a lightweight alternative to FLUSH TABLES WITH READ LOCK and can be used to take both physical and logical backups...
View ArticleTest Drive of Solid
Not so long ago Solid released solidDB for MySQL Beta 3 so I decided now is time to take a bit closer look on new transactional engine for MySQL. While my far goal is the performance and scalability...
View ArticleClik here to view.
InnoDB’s gap locks
One of the most important features of InnoDB is the row level locking. This feature provides better concurrency under heavy write load but needs additional precautions to avoid phantom reads and to get...
View ArticleIntroducing backup locks in Percona Server
TL;DR version: The backup locks feature introduced in Percona Server 5.6.16-64.0 is a lightweight alternative to FLUSH TABLES WITH READ LOCK and can be used to take both physical and logical backups...
View ArticleTest Drive of Solid
Not so long ago Solid released solidDB for MySQL Beta 3 so I decided now is time to take a bit closer look on new transactional engine for MySQL. While my far goal is the performance and scalability...
View ArticleClik here to view.
InnoDB’s gap locks
One of the most important features of InnoDB is the row level locking. This feature provides better concurrency under heavy write load but needs additional precautions to avoid phantom reads and to get...
View ArticleInteractive Debugging of Transaction Conflicts with TokuDB
I am developing a concurrent application that uses TokuDB to store its database. Sometimes, one of my SQL statements returns with a ‘lock wait timeout exceeded’ error. How do I identify the cause of...
View ArticleIntroducing backup locks in Percona Server
TL;DR version: The backup locks feature introduced in Percona Server 5.6.16-64.0 is a lightweight alternative to FLUSH TABLES WITH READ LOCK and can be used to take both physical and logical backups...
View Article
