| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 112354 | 2023-09-15 7:52 | 2023-10-20 1:00 | MySQL Server: Optimizer | No Feedback (189 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
| 100346 | 2020-07-28 6:10 | 2021-10-30 1:00 | MySQL Server: Optimizer | No Feedback (909 days) | S2 | 8.0.16-7 | Any | x86 | crash |
| 103852 | 2021-05-29 20:02 | 2021-07-01 1:00 | MySQL Server: Optimizer | No Feedback (1030 days) | S2 | 8.0.17 | Other (official Docker image) | x86 | intermediate ROLLUP gives incorrect result |
| 101805 | 2020-11-30 16:16 | 2021-01-02 1:00 | MySQL Server: Optimizer | No Feedback (1210 days) | S2 | 5.7.32 | Any | Any | Using index for group-by doesn't work with InnoDB compressed table |
| 100764 | 2020-09-08 8:50 | 2020-10-16 1:00 | MySQL Server: Optimizer | No Feedback (1288 days) | S1 | 8.0 | Any | Any | Rename Table causes other SQL execution plans to change. |
| 96591 | 2019-08-20 11:45 | 2019-09-21 1:00 | MySQL Server: Optimizer | No Feedback (1679 days) | S1 | 5.7.24 | CentOS (5.7) | x86 | The select query return not all matching rows from single table select |
| 79547 | 2015-12-07 13:59 | 2019-06-03 1:00 | MySQL Server: Optimizer | No Feedback (1789 days) | S3 | 5.6 | Debian | Any | bad performance query on mysql 5.6 |
| 92724 | 2018-10-09 21:33 | 2018-11-12 13:21 | MySQL Server: Optimizer | No Feedback (1993 days) | S3 | 5.7.21, 5.7.23 | CentOS | Any | Optimizer is using wrong index that isn't in possible index list |
| 69390 | 2013-06-03 18:27 | 2018-04-24 1:00 | MySQL Server: Optimizer | No Feedback (2194 days) | S2 | 5.6.11 | Linux (Oracle Linux 6.4) | Any | Query is more than 2 orders of magnitude slower on MySQL 5.6.11 |
| 80677 | 2016-03-09 19:37 | 2018-03-24 1:00 | MySQL Server: Optimizer | No Feedback (2225 days) | S5 | 5.6.25, 5.7.18 | Any | Any | Optimizer chooses wrong index for LEFT JOIN ORDER BY query |
| 86205 | 2017-05-06 23:13 | 2017-06-10 1:00 | MySQL Server: Optimizer | No Feedback (2512 days) | S3 | 5.6/5.7 | Windows | Any | optimizer index using select where column in select |
| 85703 | 2017-03-30 8:03 | 2017-05-01 1:00 | MySQL Server: Optimizer | No Feedback (2552 days) | S2 | 5.6.34 | Red Hat | Any | mrr_cost_based = off Complex query return empty |
| 83152 | 2016-09-26 15:03 | 2016-10-28 1:00 | MySQL Server: Optimizer | No Feedback (2737 days) | S3 | 5.7.14 | Red Hat (CentOS 7) | Any | Badly optimized query with VIEWs (regression) |
| 82133 | 2016-07-06 21:16 | 2016-08-19 1:00 | MySQL Server: Optimizer | No Feedback (2807 days) | S2 | 5.7.12 | Any | Any | The optimizer is incorrectly using join buffer (Block Nested Loop) |
| 81914 | 2016-06-17 22:42 | 2016-08-19 1:00 | MySQL Server: Optimizer | No Feedback (2807 days) | S2 | 5.7.12 | CentOS | Any | The optimizer is choosing the wrong index |
| 81812 | 2016-06-11 14:40 | 2016-07-15 1:00 | MySQL Server: Optimizer | No Feedback (2842 days) | S1 | 5.6 | Ubuntu | Any | Query Planner chooses wrong index for ORDER BY LIMIT 1 and limit 2 and more |
| 80789 | 2016-03-18 10:22 | 2019-06-06 21:10 | MySQL Server: Optimizer | No Feedback (2913 days) | S1 | 5.6.27-29, 5.7.11 | CentOS (x86_64) | Any | "Select" query gives empty result depending on index or spacing in query |
| 80127 | 2016-01-23 11:24 | 2016-02-25 1:00 | MySQL Server: Optimizer | No Feedback (2983 days) | S2 | 5.7.10-log | Windows | Any | Linq with order by specific field and take or first fails |
| 78997 | 2015-10-28 9:53 | 2015-12-06 1:00 | MySQL Server: Optimizer | No Feedback (3064 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 |
| 78611 | 2015-09-28 21:27 | 2015-11-03 1:00 | MySQL Server: Optimizer | No Feedback (3097 days) | S5 | Any | Any | timout query after 99,999 seconds | |
| 77424 | 2015-06-22 6:39 | 2015-12-24 8:38 | MySQL Server: Optimizer | No Feedback (3177 days) | S2 | 5.5.43, 5.6.25 | Debian (Wheezy) | Any | Poor choices by query planner on innodb table vs myisam |
| 75818 | 2015-02-07 15:11 | 2015-03-11 1:00 | MySQL Server: Optimizer | No Feedback (3334 days) | S5 | 5.6.17, 5.6.20 | Linux (CentOS 5.7) | Any | can't utilize more keyparts |
| 74200 | 2014-10-03 2:07 | 2015-03-12 15:59 | MySQL Server: Optimizer | No Feedback (3394 days) | S2 | 5.6 | MacOS | Any | Optimizer randomly transforms some LEFT JOINs into INNER JOINs |
| 72242 | 2014-04-04 18:34 | 2014-07-11 1:00 | MySQL Server: Optimizer | No Feedback (3577 days) | S5 | 5.6.16, 5.6.17 | Any (tested on linux) | Any | Bug query optimizer when multiple conditions are included in ON section |
| 72834 | 2014-06-02 14:10 | 2014-07-04 1:00 | MySQL Server: Optimizer | No Feedback (3584 days) | S2 | 5.6.12 | Windows (Microsoft build 9200, 64-bit) | Any | Cannot query for a date column using time specification with unique index |
| 72588 | 2014-05-09 3:41 | 2014-06-10 1:00 | MySQL Server: Optimizer | No Feedback (3608 days) | S3 | 5.5.37 | Any | Any | MySQL creates large temporary tables with UNION ALL and strings |
| 70012 | 2013-08-13 11:12 | 2014-01-10 1:00 | MySQL Server: Optimizer | No Feedback (3759 days) | S2 | 5.6.12 | Solaris (SunOS db-stage02.fmk.netic.dk 5.10 Generic_147441-27 i86pc i386 i86pc) | Any | Different Optimizer (slower) for Query in 5.6 compared to 5.1 |
| 70086 | 2013-08-19 16:06 | 2013-11-03 1:00 | MySQL Server: Optimizer | No Feedback (3827 days) | S2 | 5.6.13-log | Linux (2.6.16.33-xenU x86_64) | Any | Degraded performance for index_merge updates |
| 26339 | 2007-02-13 19:45 | 2018-09-09 20:45 | MySQL Server: Optimizer | No Feedback (4086 days) | S2 | 5.0.26, 5.0.41 | Any (2.6.19.2-grsec Linux) | Any | Query hangs / State: statistics |
| 59950 | 2011-02-04 16:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | No Feedback (4401 days) | S5 | 5.5.8 | Linux (centos 5.5 64bit) | Any | Identical query taking longer on 5.5.8 compared to 5.1 |
| Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
