Comments on: Migrating MySQL MyISAM apps to the InnoDB storage engine http://openquery.com/blog/migrating-mysql-myisam-apps-to-the-innodb-storage-engine About MySQL, Drizzle, MariaDB and more! Thu, 02 Feb 2012 21:40:24 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: arjen http://openquery.com/blog/migrating-mysql-myisam-apps-to-the-innodb-storage-engine/comment-page-1#comment-922 arjen Thu, 12 Mar 2009 14:50:33 +0000 http://openquery.com/blogs/migrating-mysql-myisam-apps-to-the-innodb-storage-engine#comment-922 Hi Harry! Thanks for that clarification. Hi Harry!
Thanks for that clarification.

]]> By: harrison_fisk http://openquery.com/blog/migrating-mysql-myisam-apps-to-the-innodb-storage-engine/comment-page-1#comment-921 harrison_fisk Thu, 12 Mar 2009 14:03:43 +0000 http://openquery.com/blogs/migrating-mysql-myisam-apps-to-the-innodb-storage-engine#comment-921 You said: <blockquote>If you're not (yet) using InnoDB but just MyISAM, you're not in the clear though: regular lock timeouts can also occur with MyISAM, although problems are, in my experience, less common.</blockquote> Locks almost never timeout in MyISAM. They only can in 5.0 if you are using server-side cursors to the client (which almost no one does since they are pretty bad). It requires using the mysql_stmt_attr_set API with the prepared statement API, which will then cause table_lock_wait_timeout to take effect. Otherwise, in normal operations MyISAM locks will wait forever. You said:

If you’re not (yet) using InnoDB but just MyISAM, you’re not in the clear though: regular lock timeouts can also occur with MyISAM, although problems are, in my experience, less common.

Locks almost never timeout in MyISAM. They only can in 5.0 if you are using server-side cursors to the client (which almost no one does since they are pretty bad). It requires using the mysql_stmt_attr_set API with the prepared statement API, which will then cause table_lock_wait_timeout to take effect.

Otherwise, in normal operations MyISAM locks will wait forever.

]]>