[Bug 735950] Re: LOCK TABLE <table> WRITE; does not obtain an exclusive table lock

[James Page]

Confirmed using the following procedure (on a fresh Lucid 10.04.2 +
mysql-server-5.1 install).

Session 1:

CREATE DATABASE test;
USE test;
CREATE TABLE example (
  id INT,
  data VARCHAR(100)
);
INSERT INTO example VALUES (1,'test-1');
INSERT INTO example VALUES (2,'test-2');
INSERT INTO example VALUES (3,'test-3');

LOCK TABLE example WRITE;

Session 2 (already created - really important - see below):

SELECT * FROM example;

Should return all three rows (which is not correct - see
http://dev.mysql.com/doc/refman/5.1/en/lock-tables.html)

However I did notice that if I created the second session after the
first session had acquired the lock on the table, I got the right
behaviour - i.e. the SELECT blocked until the lock was released in the
first session.

INSERTS seem to be OK - i.e. I was unable to insert to the table when
the lock was acquired in the first session.

** Changed in: mysql-dfsg-5.1 (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
https://bugs.launchpad.net/bugs/735950

Title:
  LOCK TABLE <table> WRITE; does not obtain an exclusive table lock