[MDEV-4029] SELECT on information_schema using a subquery locks up the information_schema table due to incorrect mutexes handling Created: 2013-01-14 Updated: 2013-01-21 Resolved: 2013-01-21 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.1, 5.5.28a, 5.3.11, 5.2.13, 5.1.66 |
| Fix Version/s: | 10.0.1, 5.5.29, 5.1.67, 5.2.14, 5.3.12 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Jean Weisbuch | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | upstream | ||
| Environment: |
Debian 6.0.6 amd64 on both machines : one running 5.5.28a-MariaDB-a1~squeeze-l and one running MySQL 5.1.66-0+squeeze1-log |
||
| Attachments: |
|
| Description |
|
Doing a SELECT query involving a subquery on information_schema will lock the query and the whole information_schema (even if the query is done by an unpriviledged user). All queries done afterwise on the information_schema (including the use of SHOW STATUS and SHOW VARIABLES) wont end and cannot be killed (Status: Killed and State: executing) until the mysqld process is stopped and the mysqld wont shutdown gracefully (a kill -9 must be done in order to stop it). Here is an example of these problematic queries :
==================== The query boils down to
and one can add additional conditions of one's choice or extend it to make more realistic. Reproducible on all current trees, MariaDB 5.1-10.0 and MySQL 5.1-5.6.
|
| Comments |
| Comment by Elena Stepanova [ 2013-01-14 ] |
|
I think even though it's an upstream bug, it's worth fixing in the upcoming 5.5.29 release (next releases of 5.1+ might already pick up the upstream fix, but 5.5.29 won't). |
| Comment by Jean Weisbuch [ 2013-01-14 ] |
|
Seems related to http://bugs.mysql.com/bug.php?id=58738 |
| Comment by Sergei Golubchik [ 2013-01-14 ] |
|
fixed in 5.7.0 |
| Comment by Elena Stepanova [ 2013-01-14 ] |
|
I find it weird that it was only fixed in 5.7.0, doesn't seem to be usual approach to such bugs. Maybe it's because the bug was marked as debug-only, although in fact it affects release builds also, as Jean described. |
| Comment by Patryk Pomykalski [ 2013-01-16 ] |
|
trying to fix it |