Bug #77318 | Selects waiting on MDL when altering partitioned table | ||
---|---|---|---|
Submitted: | 11 Jun 2015 14:40 | Modified: | 12 Jun 2015 7:29 |
Reporter: | Przemyslaw Malkowski | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.5.44, 5.5.45 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | mdl |
[11 Jun 2015 14:40]
Przemyslaw Malkowski
[12 Jun 2015 7:29]
MySQL Verification Team
Hello Przemyslaw, Thank you for the report and test case. Observed this with 5.5.45 builds. Thanks, Umesh
[12 Jun 2015 7:29]
MySQL Verification Team
test results
Attachment: 77318.txt (text/plain), 5.98 KiB.
[12 Jun 2015 12:42]
MySQL Verification Team
I just read https://dev.mysql.com/doc/refman/5.5/en/partitioning-limitations-locking.html It starts out sounds not-so-bad "This is not true for statements effecting partitioned tables using storage engines such as InnoDB, that employ row-level locking and do not actually perform (or need to perform) the locks prior to partition pruning." but when you actually read the DML descriptions, it says entire table gets locked for everything ;)