Bug #68752 | Long query in "statistics" phase cannot be killed, prevents db shutdown too | ||
---|---|---|---|
Submitted: | 22 Mar 2013 21:28 | Modified: | 21 Jul 2014 20:00 |
Reporter: | Franjo Markovic | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.6.10 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[22 Mar 2013 21:28]
Franjo Markovic
[1 Apr 2013 16:47]
MySQL Verification Team
The fact this query takes so long on 5.6.10 is due to: http://bugs.mysql.com/bug.php?id=68046 Tested 5.6.12: 189000 rows in set (1 min 6.78 sec) Query OK, 0 rows affected (1 min 50.34 sec) Tested 5.6.10: 189000 rows in set (13 min 28.79 sec) Query OK, 0 rows affected (14 min 6.58 sec)
[1 Apr 2013 16:50]
MySQL Verification Team
I should note that the 1 min+ is spent concatting the string, not for the actual query itself! So, I'm setting this as duplicate.
[3 Apr 2013 0:15]
Franjo Markovic
This is not about "in" behavior and optimization. There are other cases where "statistics" phase takes long in very complex queries. This bug is about non-responsiveness of "statistics" phase. Why should it not be stoppable?
[23 Apr 2013 20:41]
MySQL Verification Team
Please try 5.6.11. Thanks.
[2 May 2013 18:17]
Franjo Markovic
5.6.11 has fixed "in" behavior, making my test case not appropriate any more.
[21 Jul 2014 20:00]
Sveta Smirnova
Thank you for the feedback. Closed as "Can't repeat" since the issue is not repeatable anymore.