Leo,
Leo Huang wrote:
Heikki,
Thanks for you help!
I also read the comment in file of innodbase/lock/lock0lock.c in which
you said Different transaction can have conflicting locks set on the
gap at the same time.. I think that the innodb gap lock's behavior
just like an IX lock's behavior.
backup tool for InnoDB which also backs up
MyISAM tables
http://www.innodb.com/order.php
.
From: leo huang Date: December 12 2006 7:46am
Subject: Why innodb can give the same X gap lock to two transactions?
Get Plain Text
Hi, all,
We have an innodb table named test. It has some rows
, 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
.
From: leo huang Date: December 12 2006 7:46am
Subject: Why innodb can give the same X gap lock to two transactions?
Get Plain Text
Hi, all
Which version of mysql is this?
In 5.1.12 when I run your test the section transaction blocks waiting
for the lock (as it should). My show innodb status output is:
TRANSACTIONS
Trx id counter 0 1300
Purge done for trx's n:o 0 1288 undo n:o 0 0
History list length 1
Hi, all,
We have an innodb table named test. It has some rows as follow:
mysql show create table test;
+---+-+
| Table | Create Table
