However it does not include an explanation of what 'updating reference tables' means, which is especially unfortunate as I have a long running query in that state that is negatively impacting the performance of my server. The overall query was very slow so I began breaking it down into smaller pieces (1. SHOW PROCESSLIST Syntax) lists many of the different processlist State values with an explanation of each. SQL update statement takes around 7 seconds and I'm wondering how to improve its performance. Since the query is spending most of its time 'updating'.

Search through local Iranian Chat Room Find events, attractions, activities and things to do in the Ottawa Region. Raising Sim Dating Sim - Spirited Heart Deluxe When it comes to, shall we say, progressive couples, no one tops the open-minded pairings found in dating sims. is a fascinating dating sim game brand, attracting a great number of players all over the world.

SHOW PROFILE FOR QUERY 3; --------------------------- ----------- | Status | Duration | --------------------------- ----------- | starting | 0.000075 | | checking permissions | 0.000013 | | checking permissions | 0.000012 | | Opening tables | 0.000073 | | checking permissions | 0.000011 | | checking permissions | 0.000013 | | System lock | 0.000023 | | init | 0.000021 | | updating main table | 0.000014 | | optimizing | 0.000020 | | statistics | 0.000117 | | preparing | 0.000028 | | executing | 0.000011 | | Sending data | 31.940094 | I have a few other UPDATE queries with similar symptoms.

Customer ID 1 Using where id select_type table type possible_keys key key_len ref rows Extra 1 SIMPLE D index PRIMARY Diff Time 9 NULL 4044212 Using index 1 SIMPLE V ref Order ID_Customer ID, Customer ID_Order ID Order ID_Customer ID 9 D.

UPDATE match Session Members msm JOIN match Sessions ms ON msm.match No = ms.match No AND ms.

) But if its spending time locating the rows to update, I thought that an index might help.