Take the 2-minute tour ×  I am Working around MySQL error
"Deadlock found when trying to get lock; try restarting
transaction".  I am going to have to update a program to allow
deadlocks. Is it possible that SELECT statement will produce
deadlock errors? I know that it is only a read lock so multiple
selects won't be a problem, but what if there is an
INSERT/UPDATE/DELETE statement (with subqueries possible with
joins) and a SELECT statement (possible with joins or
subqueries)? Is it possible that the error will be thrown on the
SELECT instead of the INSERT/UPDATE/DELETE  The story is here if
you are curious.  share|improve this question +1 for this is
good question because it brings to light an InnoDB quirk most
people are not aware of in conjunction with SELECTs against
InnoDB tables. –  RolandoMySQLDBA Aug 8 '11 at 21:00  1 Answer 1
up vote 2 down vote accepted  The direct answer to your
question's title is No.    Just to keep your question in
perspective, when you look over these answers (don't look too