|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Denis Jedig (dj
syneticon.net)
Date: Thu May 09 2013 - 17:39:12 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 09.05.2013 22:58, schrieb Robinson, Eric:
> Q: What conditions could cause single query to lock up a database for a while for all users
From
<http://docs.oracle.com/cd/E17952_01/refman-5.5-en/table-locking.html>
:
A SELECT statement that takes a long time to run prevents other
sessions from updating the table in the meantime, making the
other sessions appear slow or unresponsive. While a session is
waiting to get exclusive access to the table for updates, other
sessions that issue SELECT statements will queue up behind it,
reducing concurrency even for read-only sessions.
You might try using low_priority_updates to mitigate this.
Regards,
--
Denis Jedig
syneticon networks gmbh
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]