On Thu, Oct 14, 2010 at 3:28 AM, Johan De Meersman wrote:
> That depends on the type of lock. If no lock type is specified, InnDB will
> prefer row locks, while MyISAM will do table locks.
>
> That may help, unless all your queries are trying to access the same rows
> anyway :-)
Even that can wor
On Thu, Oct 14, 2010 at 9:19 AM, monloi perez wrote:
> Does this happen if your table is InnoDB?
>
That depends on the type of lock. If no lock type is specified, InnDB will
prefer row locks, while MyISAM will do table locks.
That may help, unless all your queries are trying to access the same
Does this happen if your table is InnoDB?
Thanks all,
Mon
From: Claudio Nanni
To: monloi perez
Cc: mysql mailing list
Sent: Thu, October 14, 2010 3:16:38 PM
Subject: Re: How to kill locked queries
Hi Mon,
Killing locked queries is not the first step in
Hi Mon,
Killing locked queries is not the first step in database tuning.
Queries locked for a long time usually depend on slow updates that lock
other updates or selects,
this happen on MyISAM (or table level locking engines).
If you are really sure you want and can without problems kill the queri
The root cause is another query that has tables locked that your "locked"
queries want. Behind that may be, for example, an inefficient but
often-executed query, high I/O concurrency that has a cumulative slowing
effect, or maybe simply a long-running update that might be better scheduled
during th
