Re: INSERT-only table gets locked randomly (MySQL 5.0)

[Ingo Strüwing]

Hi,

what do you mean when you write "...a php cron job reads data from this table..." and "There are no SELECT..."? How do you read from the table without using select?

The "update" state is set by the INSERT statement after it opened and locked the table. After this it starts a loop over all insert values and writes them into the table. After the loop follow some cleanup operations including commit (which should be irrelevant for MyISAM tables) and binary log handling (but you don't use replication, right?). So I have no idea where the thread is waiting.

BTW, is that state coupled with major CPU time consumption?

It would be great if you could attach a debugger to the running server and look at the stack traces for all the threads to see where that insert waits. Or you kill the server with SIGSEGV and to the same analyze on the core file. This might give some insight, but I can't guarantee anything. :)

Regards

Ingo Strüwing, Senior Software Developer - Storage Engines
MySQL AB, www.mysql.com