Public bug reported:
when locking a table with:
LOCK TABLE <table> WRITE;
the session does not obtain an exclusive lock. A second session can still read
from the table which is locked, but cannot write or update.
A test using another MySQL server (version 5.1.50) showed the correct
behaviour: an exclusive lock was obtained with "LOCK TABLE <table> WRITE;" an
other session were not able to read the locked table.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mysql-server-5.1 5.1.41-3ubuntu12.10
ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13
Uname: Linux 2.6.32-29-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Mar 16 08:45:53 2011
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
Logs.var.log.daemon.log:
Logs.var.log.kern.log:
MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
[mysqld_safe]
syslog
MySQLVarLibDirListing: False
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: mysql-dfsg-5.1
** Affects: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lucid
--
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
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
