| Showing 1-30 of 37 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 1973 | 2003-11-27 9:16 | 2003-12-13 18:57 | MySQL Server: Optimizer | Won't fix (7884 days) | S3 | 4.0 | Any (all) | Any | TPC-C query does not uses indexes efficently |
| 5606 | 2004-09-16 10:19 | 2004-10-07 12:27 | MySQL Server: Optimizer | Won't fix (7585 days) | S3 | 4.0.21 | Any (any) | Any | Nonoptimal join type |
| 6072 | 2004-10-13 19:22 | 2004-11-23 16:42 | MySQL Server: Optimizer | Won't fix (7538 days) | S2 | 4.1.6 (bk) | Any (all) | Any | MySQL 4.1 performance regression while comparing text fields |
| 8686 | 2005-02-22 13:42 | 2005-03-12 15:38 | MySQL Server: Optimizer | Won't fix (7429 days) | S3 | 4.1.10 | Any (*) | Any | explain show incorrect info |
| 9000 | 2005-03-06 22:25 | 2005-03-09 1:12 | MySQL Server: Optimizer | Won't fix (7432 days) | S3 | 4.0, 4.1 | Any (Any) | Any | HAVING not filtering correctly when used with SUM |
| 13500 | 2005-09-26 20:33 | 2005-10-05 5:44 | MySQL Server: Optimizer | Won't fix (7222 days) | S2 | 4.1.14/BK source | Linux (RHEL 3.0/Linux) | Any | sum() function returns different result based on order |
| 19346 | 2006-04-25 17:41 | 2011-02-16 23:43 | MySQL Server: Optimizer | Won't fix (5695 days) | S3 | 4.1, 5.0, 5.0.89-bzr | Linux (Linux) | Any | Range optimizer decides to scan NULL key values for t.key IN (NULL, ...) |
| 20182 | 2006-06-01 0:00 | 2006-07-11 6:06 | MySQL Server: Optimizer | Won't fix (6943 days) | S5 | 4.1.19 | Linux (gentoo linux) | Any | LEFT JOIN optimizations |
| 22144 | 2006-09-09 5:07 | 2014-01-07 15:25 | MySQL Server: Optimizer | Won't fix (4206 days) | S3 | 5.2 | Any | Any | EXPLAIN returns wrong information |
| 24714 | 2006-11-30 7:30 | 2007-08-20 15:40 | MySQL Server: Optimizer | Won't fix (6538 days) | S1 | 4.1.22, 4.1 BK | Linux (Linux, FreeBSD) | Any | Mathematical SELECT queries no longer return consistent results |
| 28866 | 2007-06-04 7:29 | 2007-08-17 23:07 | MySQL Server: Optimizer | Won't fix (6541 days) | S5 | 4.1, 5.0, 5.1 | Any (Linux) | Any | Optimizer doesn't choose best plan for execution |
| 37328 | 2008-06-11 4:50 | 2014-08-12 2:08 | MySQL Server: Optimizer | Won't fix (4648 days) | S3 | 5.0.60, 5.0.64 | Any | Any | Optimizer prefers ref access on multiple-column index over simple range access |
| 42821 | 2009-02-13 9:41 | 2011-02-16 23:43 | MySQL Server: Optimizer | Won't fix (5641 days) | S1 | 6.0-falcon-team | Any | Any | Assertion failed: maxcount!=0, file filesort.cc, line 1227 after Falcon recovery |
| 43371 | 2009-03-04 14:09 | 2013-01-10 11:02 | MySQL Server: Optimizer | Won't fix (4568 days) | S1 | 5.0, 5.1.31, 5.1.33-bzr | Any | Any | wrong index is used (sometimes) in tables with multiple keys |
| 44604 | 2009-05-01 14:26 | 2011-02-16 23:43 | MySQL Server: Optimizer | Won't fix (5903 days) | S1 | 5.1.34, 5.0, 5.1 bzr, 5.4 | Linux (Cent OS v5) | Any | Wrong number of results returned when executing query |
| 49872 | 2009-12-22 10:44 | 2011-02-16 23:44 | MySQL Server: Optimizer | Won't fix (5668 days) | S3 | 5.0-bugteam | Any | Any | MySQL returns wrong user variable value after select |
| 50052 | 2010-01-04 14:27 | 2011-02-16 23:44 | MySQL Server: Optimizer | Won't fix (5613 days) | S3 | 6.0 | Linux | Any | --optimizer-search-depth=63 makes mysql server crash |
| 51930 | 2010-03-10 19:13 | 2015-05-07 5:08 | MySQL Server: Optimizer | Won't fix (3721 days) | S5 | 5.1.43, 5.1.44, 5.1.46-bzr | Linux (Ubuntu 8.04) | Any | MySQL not optimizing query on two part (char,int) index |
| 53224 | 2010-04-27 21:54 | 2011-02-16 23:44 | MySQL Server: Optimizer | Won't fix (5555 days) | S3 | 5.0 | Any | Any | Aggregate-only query has extra rows if ORDER BY contains additional column |
| 57599 | 2010-10-20 11:59 | 2011-02-16 23:44 | MySQL Server: Optimizer | Won't fix (5373 days) | S3 | 5.1, 5.5 | Any | Any | ORDER BY .. LIMIT stops using a key after removing partitioning on a table |
| 61395 | 2011-06-03 12:23 | 2011-06-15 23:01 | MySQL Server: Optimizer | Won't fix (5143 days) | S3 | 5.1.58 | Any | Any | Bogus result with SQL_BIG_RESULT and multiple GROUP BY |
| 65995 | 2012-07-24 10:49 | 2013-01-30 0:38 | MySQL Server: Optimizer | Won't fix (4548 days) | S3 | 5.5.20, 5.5.28 | Any | Any | MySQL 5.5.20 sql_select.cc has error |
| 71849 | 2014-02-26 21:41 | 2014-04-04 13:50 | MySQL Server: Optimizer | Won't fix (4119 days) | S3 | 5.5 | Any | Any | memory leak when subquery using order by(make_reverse) and best_key used |
| 72040 | 2014-03-14 21:28 | 2017-05-16 14:23 | MySQL Server: Optimizer | Won't fix (4080 days) | S1 | 5.5.35,5.5.36 | Any | Any | mysql only returning the first row |
| 72510 | 2014-05-02 2:15 | 2014-05-04 15:39 | MySQL Server: Optimizer | Won't fix (4089 days) | S2 | 5.5.37-0ubuntu0.12.04.1 | Linux (Ubuntu 12.04) | Any | SELECT leaks memory |
| 77398 | 2015-06-18 8:01 | 2024-01-25 10:44 | MySQL Server: Optimizer | Won't fix (592 days) | S1 | 5.7.7 | Any | Any | row size too large in mysql 5.7 query |
| 78417 | 2015-09-12 9:48 | 2015-09-14 11:44 | MySQL Server: Optimizer | Won't fix (3591 days) | S3 | 5.6.22 | Any | Any | Valid select with expression in group by under "only_full_group_by" fails |
| 78822 | 2015-10-13 17:15 | 2016-10-20 8:41 | MySQL Server: Optimizer | Won't fix (3189 days) | S3 | 5.6, 5.6.27 | Any | Any | Materialized table from semijoin may change join order and lead to bad plan |
| 87164 | 2017-07-21 16:28 | 2021-04-13 7:44 | MySQL Server: Optimizer | Won't fix (2643 days) | S3 | 5.7, 5.7.18, 5.7.19 | CentOS (6 & 7) | Any | Queries running much slower in version 5.7 versus 5.6 |
| 100536 | 2020-08-15 0:48 | 2023-07-06 15:50 | MySQL Server: Optimizer | Won't fix (1608 days) | S5 | 8.0.21, 8.0.23 | Any | Any | Regression on 8.0 when using DISTINCT and LEFT JOIN |
| Showing 1-30 of 37 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
