Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
22413 | 2006-09-16 13:59 | 2006-11-27 18:19 | MySQL Server | Closed (6332 days) | S1 | 5.0.24a,5.0BK,5.1BK | Any | EXPLAIN SELECT FROM view with ORDER BY yield server crash | |
22930 | 2006-10-03 12:41 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (6274 days) | S3 | 5.1-bk | Any | Wrong EXPLAIN output for query with subquery | |
68299 | 2013-02-07 5:40 | 2013-05-30 2:07 | MySQL Server: Optimizer | Closed (3956 days) | S3 | 5.6 | Any | Any | unexcepted "Using where" in "explain update/delete" |
111564 | 2023-06-26 12:33 | 2023-08-10 12:21 | MySQL Server: Optimizer | Closed (232 days) | S3 | 8.0 | Any | Any | Contribution by Tencent: explain format=tree lost the subquery in the hash join |
71980 | 2014-03-08 19:44 | 2014-05-14 1:34 | MySQL Workbench: SQL Editor | Closed (3607 days) | S3 | 6.1.2.11661 | Any | Any | canvas too small for visual explain in export |
71973 | 2014-03-07 13:28 | 2014-05-14 23:41 | MySQL Workbench: SQL Editor | Closed (3607 days) | S3 | 6.1.2.11661 | Any | Any | Visual explain fails on large explain plan |
72265 | 2014-04-07 16:59 | 2014-04-08 4:56 | MySQL Enterprise Monitor: Agent | Verified (3643 days) | S3 | 3.0.8 | Any | Any | MEM tries to explain INSERT/UPDATE/DELETE type statements on a read-only slave |
73305 | 2014-07-17 7:27 | 2017-05-15 12:39 | MySQL Server: Documentation | Closed (2510 days) | S2 | 5.6, 5.7 | Any | Any | Manual does not explain all cases when SHOW VIEW privilege is needed |
73306 | 2014-07-17 7:35 | 2017-05-15 12:37 | MySQL Server: Documentation | Closed (2510 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Manual does not explain what privileges are needed for EXPLAIN explainable_stmt |
68871 | 2013-04-05 7:32 | 2014-08-27 4:36 | MySQL Server: Optimizer | Can't repeat (3502 days) | S3 | 5.1.58, 5.5.30, 5.6.10 | Any | Any | EXPLAIN does not show real plan used for query with HAVING |
72031 | 2014-03-13 8:22 | 2014-03-13 11:14 | MySQL Server: Optimizer | Verified (3669 days) | S3 | 5.6.16 | Any | Any | Strange explain behaviour |
71981 | 2014-03-08 20:24 | 2014-03-13 11:15 | MySQL Server: DML | Verified (3669 days) | S3 | 5.6.16 | Any | Any | Strange result on explain |
78213 | 2015-08-25 20:03 | 2015-10-23 12:55 | MySQL Server: Optimizer | Closed (3096 days) | S2 | 5.6, 5.6.26, 5.5.46, 5.1.77 | Any (Mac OS X 10.9 and CentOS 6) | Any | Spatial index causes incorrect cardinality for all non-primary indexes |
79717 | 2015-12-21 2:47 | 2016-02-26 0:13 | MySQL Server: Documentation | Closed (2954 days) | S3 | 5.7 | Any | Any | Document Bug about "EXPLAIN Output Format" |
69795 | 2013-07-19 17:54 | 2016-06-16 20:32 | MySQL Server: Optimizer | Verified (2843 days) | S3 | 5.6.12 | Any | Any | EXPLAIN FORMAT=JSON doesn't show Using filesort for UNIONs |
83062 | 2016-09-20 13:18 | 2018-04-24 20:15 | MySQL Server: Optimizer | Verified (2746 days) | S3 | 5.6.32, 5.7.14, 5.6.33, 5.7.15 | Any | Any | it's no longer possible to determine used key parts by looking at key_length |
72030 | 2014-03-13 7:45 | 2016-11-05 9:43 | MySQL Enterprise Monitor: Server | Not a Bug (2701 days) | S3 | 3.0.7 | Any | Any | Exceptions on SQL Explain |
83398 | 2016-10-16 11:09 | 2017-02-17 18:00 | MySQL Server: Documentation | Closed (2597 days) | S3 | 5.7.15 | Any | Any | Slow and unexpected explain output on FTS |
86574 | 2017-06-03 16:16 | 2017-06-03 19:36 | MySQL Server: Optimizer | Verified (2491 days) | S3 | 5.6 | Any | Any | Confusing EXPLAIN output for INSERT Queries |
78412 | 2015-09-11 16:17 | 2017-01-13 9:03 | MySQL Server: Documentation | Closed (3031 days) | S2 | 5.6.24 | Any | Any | UPDATE with subquery is NOT optimized the same way as equivalent SELECT |
99707 | 2020-05-27 12:33 | 2020-06-01 12:29 | MySQL Server: Documentation | Closed (1397 days) | S3 | 8.0.20, 5.7.30 | Any | Any | EXPLAIN requires more than SELECT |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (406 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
111580 | 2023-06-27 11:01 | 2023-06-28 13:40 | MySQL Server: Security: Privileges | Not a Bug (275 days) | S3 | 8.0, 8.0.31 | Any | Any | view CREATE with SQL SECURITY DEFINER can SELECT but cannot EXPLAIN |
35355 | 2008-03-17 23:14 | 2012-10-16 4:40 | MySQL Server: DML | Closed (4182 days) | S2 | 5.0 | Any | Any | Support explain for update and delete statements |
47106 | 2009-09-03 16:44 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5215 days) | S3 | 5.1, 5.4/6.0 | Any | Any | Crash / segfault on adding EXPLAIN to a non-crashing query |
28728 | 2007-05-28 17:07 | 2007-06-10 18:27 | MySQL Server: Optimizer | Closed (6137 days) | S1 | 5.0.42, 5.0.44, 5.1.20 | Any | Any | server crash with EXPLAIN EXTENDED .. and subqueries |
29443 | 2007-06-29 13:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4915 days) | S3 | 5.1.19 | Any | Any | cost calculations are off |
50168 | 2010-01-08 2:16 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5189 days) | S3 | 5.0,5.1 | Any | Any | The value of 'rows' in EXPLAIN output is not accurate for LIMIT |
50394 | 2010-01-17 4:55 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4876 days) | S2 | 5.1.41, 5.1, 5.5.99 bzr | Any | Any | Regression in EXPLAIN with index scan, LIMIT, GROUP BY and ORDER BY computed col |
51524 | 2010-02-25 18:38 | 2011-02-16 23:44 | MySQL Server: Optimizer | Duplicate (5145 days) | S1 | 5.1.44,5.5.99-m3 | Any | Any | valgrind errors with explain, join, unionless merge table |
Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |