Mike Wexler wrote:
It doesn't really answer your question, but have you tried "INSERT DELAYED" as a work around?
We've not had a lot of luck with this in the past, but it's worth a try.
Also the "updated" status is strange, because that generally indicates that its looking for the record to be updated, but since the record is new, there is no record to be updated. Could it be checking for duplicates? Not that it should be this slow, but you might try ALTER TABLE xxx DISABLE KEYS and see how that effect performance. At least it will tell you whether the problem is in updating the keys, or something else.
It's certainly checking for duplicates. There are 10034461 records in the link_area table at the moment, and 514408715 in trimble.old_crumb.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
