MySQL Truncate slow performance problems
I was having problems with a MySQL TRUNCATE taking a long time on a very large table (with foreign keys). I had thought that TRUNCATE ran more quickly than DELETE but, according to the MySQL manual, that isn't the case with InnoDB tables. In this case there is no difference between TRUNCATE and DELETE and it's recommended to drop the table and then re-create it. That sounds like a very high risk operation to me, but given that the TRUNCATE statement is taking an hour and a half to run then it looks like I've got some code to write. TRUNCATE in the MySQL documentation
Comments:
My solution to this can be found here.