diff options
| author | unknown <sergefp@mysql.com> | 2005-10-25 00:27:15 +0400 |
|---|---|---|
| committer | unknown <sergefp@mysql.com> | 2005-10-25 00:27:15 +0400 |
| commit | b25ee828838ae6f88e4616f4c01b6c84aa7059b0 (patch) | |
| tree | f5f8a9f101f123acf5138f9d5209d555d0704fda /innobase | |
| parent | 5b4e13f9e006c924dbf7188d72396d9edf8488f8 (diff) | |
| download | mariadb-git-b25ee828838ae6f88e4616f4c01b6c84aa7059b0.tar.gz | |
BUG#11704: Make InnoDB not to convert TL_WRITE_ONLY locks to TL_WRITE_ALLOW_WRITE in
OPTIMIZE TABLE.
sql/ha_innodb.cc:
Fix for BUG#11704: "Found locks from different thread" warnings:
The source of warnings was this scenario in OPTIMIZE:
thr1: lock table with TL_WRITE_ONLY (InnoDB converts lock to TL_WRITE_ALLOW_WRITE)
thr2: (UPDATE command) obtains a TL_WRITE_ALLOW_WRITE lock
thr1: call mysql_lock_abort(). This function sets type of thr'1 lock to TL_WRITE_ONLY
thr2: try to release thr2's lock. See two locks: TL_WRITE_ONLY, TL_WRITE_ALLOW_WRITE
and produce a warning.
The fix: Make InnoDB not to convert TL_WRITE_ONLY locks to TL_WRITE_ALLOW_WRITE in
OPTIMIZE TABLE.
Diffstat (limited to 'innobase')
0 files changed, 0 insertions, 0 deletions