| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 11413 | 2005-06-17 11:48 | 2005-07-23 13:08 | MySQL Server: Optimizer | No Feedback (6842 days) | S3 | 4.1.10 | Linix | Any | Merge Tables, Analize Table and Optomizer |
| 15076 | 2005-11-20 1:39 | 2005-12-25 7:27 | MySQL Server: Optimizer | No Feedback (6687 days) | S3 | 5.0.15-GA | pc-solaris2.10 (i386) | Any | index handeled incorrectly if part of a composite index is used |
| 61983 | 2011-07-26 12:13 | 2011-09-28 23:00 | MySQL Server: Optimizer | No Feedback (4585 days) | S2 | 5.1.48 | Any | Any | strange explain plan results |
| 30180 | 2007-08-01 14:49 | 2007-09-01 23:29 | MySQL Server: Optimizer | No Feedback (6072 days) | S2 | 5.0.37-community | Any | Any | Getting broken tmp key file on complex query |
| 31678 | 2007-10-17 23:51 | 2018-02-11 20:45 | MySQL Server: Optimizer | No Feedback (5634 days) | S1 | 5.0.48 | Any | Any | optimizer makes wrong index choice |
| 36109 | 2008-04-16 5:12 | 2012-05-18 20:19 | MySQL Server: Optimizer | No Feedback (5394 days) | S3 | 5.0.44, 5.0.51, 5.0.66a, 5.1.26-rc | Any | Any | index on part of varchar field is not used when it could be |
| 36681 | 2008-05-13 8:11 | 2012-05-18 20:19 | MySQL Server: Optimizer | No Feedback (5309 days) | S3 | 5.0.54 | Any | Any | Insufficient plans for huge tables |
| 42282 | 2009-01-22 22:23 | 2011-02-16 23:43 | MySQL Server: Optimizer | No Feedback (5532 days) | S3 | 5.0.67 | Any | Any | Failure to use index for group-by |
| 45226 | 2009-05-31 22:42 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5288 days) | S3 | 5.4 | Any | Any | extra rows returned for queries using IN,GROUP BY and HAVING clauses |
| 45228 | 2009-05-31 22:56 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5288 days) | S3 | 5.4 | Any | Any | Queries with WHERE <col_1> AND <condition> GROUP BY <col_2> produce bad results |
| 45886 | 2009-07-01 18:38 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5312 days) | S3 | 5.0.45-log, 5.0.83 | Any | Any | Index |
| 47906 | 2009-10-08 4:56 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5273 days) | S1 | 5.0.85, 5.1.37, 5.1.39, 6.0.9 | Any | Any | Having an extra field in a table changes optimizer index choice for other column |
| 49360 | 2009-12-02 17:53 | 2013-02-03 19:22 | MySQL Server: Optimizer | No Feedback (4762 days) | S3 | 5.0.66 , 5.0.84 , 5.0.84 , 5.1.41, 5.1.43 | Any | Any | In some circumstances, GROUP BY WITH ROLLUP is faster then GROUP BY |
| 60874 | 2011-04-14 18:30 | 2011-05-14 23:00 | MySQL Server: Optimizer | No Feedback (4721 days) | S2 | mysql-cluster-gpl-noinstall-7.1.10-win32 | Any | Any | inner join bug |
| 60941 | 2011-04-21 7:56 | 2011-06-27 23:00 | MySQL Server: Optimizer | No Feedback (4678 days) | S2 | 5.1.52-log, 5.1.56 | Any (Debian 5.0.8, Windows XP) | Any | Invalid use of join conditions |
| 45095 | 2009-05-26 11:18 | 2012-05-18 20:19 | MySQL Server: Optimizer | No Feedback (5252 days) | S3 | 5.1.32, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | order by not using index |
| 72242 | 2014-04-04 18:34 | 2014-07-11 1:00 | MySQL Server: Optimizer | No Feedback (3568 days) | S5 | 5.6.16, 5.6.17 | Any (tested on linux) | Any | Bug query optimizer when multiple conditions are included in ON section |
| 72588 | 2014-05-09 3:41 | 2014-06-10 1:00 | MySQL Server: Optimizer | No Feedback (3599 days) | S3 | 5.5.37 | Any | Any | MySQL creates large temporary tables with UNION ALL and strings |
| 78611 | 2015-09-28 21:27 | 2015-11-03 1:00 | MySQL Server: Optimizer | No Feedback (3088 days) | S5 | Any | Any | timout query after 99,999 seconds | |
| 78997 | 2015-10-28 9:53 | 2015-12-06 1:00 | MySQL Server: Optimizer | No Feedback (3055 days) | S3 | 5.6.27, 5.7.9 | Any | Any | optimizer prefers using index `a` to ORDER instead of `b,a` to EQ and ORDER |
| 80677 | 2016-03-09 19:37 | 2018-03-24 1:00 | MySQL Server: Optimizer | No Feedback (2216 days) | S5 | 5.6.25, 5.7.18 | Any | Any | Optimizer chooses wrong index for LEFT JOIN ORDER BY query |
| 82133 | 2016-07-06 21:16 | 2016-08-19 1:00 | MySQL Server: Optimizer | No Feedback (2798 days) | S2 | 5.7.12 | Any | Any | The optimizer is incorrectly using join buffer (Block Nested Loop) |
| 100346 | 2020-07-28 6:10 | 2021-10-30 1:00 | MySQL Server: Optimizer | No Feedback (900 days) | S2 | 8.0.16-7 | Any | x86 | crash |
| 100764 | 2020-09-08 8:50 | 2020-10-16 1:00 | MySQL Server: Optimizer | No Feedback (1279 days) | S1 | 8.0 | Any | Any | Rename Table causes other SQL execution plans to change. |
| 101805 | 2020-11-30 16:16 | 2021-01-02 1:00 | MySQL Server: Optimizer | No Feedback (1201 days) | S2 | 5.7.32 | Any | Any | Using index for group-by doesn't work with InnoDB compressed table |
| 112354 | 2023-09-15 7:52 | 2023-10-20 1:00 | MySQL Server: Optimizer | No Feedback (180 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
| 27467 | 2007-03-27 10:37 | 2007-05-30 7:49 | MySQL Server: Optimizer | No Feedback (6166 days) | S3 | 5.1.16-beta-log | Any | Any | MAX don't optimized. |
| 25459 | 2007-01-08 2:39 | 2007-02-28 13:34 | MySQL Server: Optimizer | No Feedback (6257 days) | S3 | 5.0 | Any (any) | Any | InnoDB prefers table scan over using primary key |
| 26339 | 2007-02-13 19:45 | 2018-09-09 20:45 | MySQL Server: Optimizer | No Feedback (4077 days) | S2 | 5.0.26, 5.0.41 | Any (2.6.19.2-grsec Linux) | Any | Query hangs / State: statistics |
| 28612 | 2007-05-23 7:30 | 2007-06-24 13:27 | MySQL Server: Optimizer | No Feedback (6141 days) | S5 | 5.0.37 | Any | Any | Optimizer does not use index for BETWEEN in a JOIN condition |
| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
