Hello.
In my opinion, it is just for some statistics. The variable
locks_immediate (which corresponds to Table_locks_immediate) is
incremented very often in mysys/thr_lock.c in this way:
statistic_increment(locks_immediate,THR_LOCK_lock);
lee wrote:
Why would a simple select
, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
.
List: mysql
Subject:Re: Table_locks_immediate and Innodb Selects
From: Gleb Paharenko gleb.paharenko
Why would a simple select against an innodb db result in a bump of the
table_locks_immediate variable? I've been debugging a different problem and I
noticed this behavior. I don't believe it is a problem but can't explain the
behavor and it seems odd.
Regards,
Lee
mysql create table
