MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Mikhail Entaltsev Date:July 24 2003 12:43pm
Subject:InnoDB locking: Different behavior on 3.23.55 and 4.0.13
View as plain text  
Hi

I have 2 MySQL  servers: 
Server1 is 3.23.55-max-log
Server2 is 4.0.13-standard-log

Let's assume that we have 2 connections (Conn1 and Conn2) and table test:
------------------------------------------------------------
CREATE TABLE `test` (
  `id` int(3) NOT NULL auto_increment,
  `name` char(10) default '',
  PRIMARY KEY  (`id`)
) TYPE=InnoDB;
------------------------------------------------------------
and put some data in it:
------------------------------------------------------------
insert into test (id, name) values (1, 'cat');
insert into test (id, name) values (2, 'dog');
insert into test (id, name) values (3, 'bird');

------------------------------------------------------------

I execute queries in the order:

Conn1: 
LOCK TABLES test WRITE;

then 

Conn2:
select * from test;

On the Server1 Conn2 is locked and it will be locked even more 
than innodb_lock_wait_timeout (that is not correct, right?).
But on the Server2 Conn2 returns results immediately.

I guess that Server2 is wrong. What do you think?

Thanks,
Mikhail.
Thread
InnoDB locking: Different behavior on 3.23.55 and 4.0.13Mikhail Entaltsev24 Jul
Re: InnoDB locking: Different behavior on 3.23.55 and 4.0.13Heikki Tuuri24 Jul
Re: InnoDB locking: Different behavior on 3.23.55 and 4.0.13Mikhail Entaltsev25 Jul
Re: InnoDB locking: Different behavior on 3.23.55 and 4.0.13Info26 Jul
Re: InnoDB locking: Different behavior on 3.23.55 and 4.0.13Info26 Jul