Would love to know how that managed to take 22 minutes to search 17k rows, call it a server hiccup or somebody else's query locking the DB?

---------- Forwarded message ---------- From: no-reply@toolserver.org Date: Sun, Sep 25, 2011 at 10:19 AM Subject: [TS] Killed SQL-Task 36551515 on db-server thyme To: overlordq@toolserver.org

Hello overlordq, a MySQL-query of yours was killed because you didn't mark it as SLOW_OK and it have run for 1328 seconds which was longer than allowed. You can find the query below. Please have also a look at [1] to find information how you can avoid killings of your queries. Maybe you can optimze the query too? The replication lag at kill-time was 204s.

Sincerly, Query-Killer. This eMail was sent automaticaly, please don't reply.

SELECT ns_id FROM toolserver.namespace WHERE ns_name = '' AND dbname = 'enwiki_p'

[1] https://wiki.toolserver.org/view/Database_access#Slow_queries_and_the_query_...