Looks like SLOW_OK mark is not recognized for INSERT queries. The query below is marked as SLOW_OK, but unlike to SELECT like queries, report shows just space doubled where the mark was set.
All tables in the query below are user tables, I cannot imaging which way such a query would cause any replag increase. mashiah On Sun, Nov 6, 2011 at 2:40 AM, <[email protected]> wrote: > Hello mashiah, > a MySQL-query of yours was killed because you didn't mark it as SLOW_OK and > it have run for 609 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 121s. > > Sincerly, > Query-Killer. > This eMail was sent automaticaly, please don't reply. > > INSERT INTO lwl (lwl_id) > SELECT l_from as lwl_id > FROM l > WHERE NOT EXISTS ( > SELECT a2cr_to, > a2cr_from > FROM a2cr > WHERE a2cr_to=l_to and > a2cr_from=l_from > ) > > > [1] > https://wiki.toolserver.org/view/Database_access#Slow_queries_and_the_query_killer > _______________________________________________ Toolserver-l mailing list ([email protected]) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
