I did check that all tables are Innodb.
I was using the Navicat Server Monitor because I know that when I see the
monitor reporting a status of locked during an attempted query, that user
comes to a complete halt until the lock is cleared (usually by the bad query
finishing.)
I will check the isolation level but I believe it is whatever was set out of
the box (five years ago.)
Thanks,
Carl
----- Original Message -----
From: "Perrin Harkins" <per...@elem.com>
To: "Carl" <c...@etrak-plus.com>
Cc: <mysql@lists.mysql.com>
Sent: Wednesday, March 04, 2009 1:49 PM
Subject: Re: Select query locks tables in Innodb
2009/3/4 Carl <c...@etrak-plus.com>:
However, when I had all the pieces in the query
(copy attached), I could easily see it was locking tables using the
Server
Monitor in Navicat.
I don't know what that is, but I think you'd better look at something
closer to the bone, like SHOW INNODB STATUS.
Explain (copy as text and copy as Excel attached) seems to indicate that
it
is fairly good although the first step does get quite a few rows.
EXPLAIN isn't really relevant to table locking. InnoDB tables should
never let readers block writers for a simple SELECT.
Does anyone have any ideas?
Did you check that your tables are InnoDB? Are you running some kind
of crazy isolation level?
- Perrin
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
