[MDEV-7894] ALTER TABLE ... IMPORT/DISCARD TABLESPACE under LOCK TABLES doesn't acquire X metadata lock Created: 2015-04-01  Updated: 2015-05-13  Resolved: 2015-05-13

Status: Closed
Project: MariaDB Server
Component/s: Locking
Affects Version/s: 10.0.17, 10.1.3
Fix Version/s: 10.1.5

Type: Bug Priority: Major
Reporter: Sergey Vojtovich Assignee: Sergei Golubchik
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-7660 MySQL WL#6671 "Improve scalability by... Closed

 Description   

This problem was fixed along with MySQL WL#6671 "Improve scalability by not using thr_lock.c locks for InnoDB tables".

Due to coding mistake thr_lock.c lock was necessary to isolate ALTER TABLE
IMPORT/DISCARD TABLESPACE under LOCK TABLES from concurrent I_S queries/
open HANDLERs.

Change ALTER TABLE IMPORT/DISCARD TABLESPACE code to acquire X
lock on table being imported/discarded even under lock tables.

 Comments   
Comment by Sergey Vojtovich [ 2015-04-01 ]

Sergei, please review fix for this bug.

Comment by Sergei Golubchik [ 2015-05-13 ]

This task is not relevant anymore since we don't plan to apply MySQL WL#6671 "Improve scalability by not using thr_lock.c locks for InnoDB tables".

The aim is to fix it in InnoDB instead of fixing it in MDL.

Generated at Thu Feb 08 07:23:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.