| Showing 1-30 of 749 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 86215 | 2017-05-08 13:35 | 2017-07-11 22:44 | MySQL Server: Optimizer | Analyzing (2480 days) | S5 | 8.0.1 | Any | Any | MySQL is much slower in 5.7 vs 5.6 |
| 24770 | 2006-12-02 0:37 | 2018-09-09 20:45 | MySQL Server: Optimizer | In progress (4784 days) | S5 | 5.1 | Any (all) | Any | update with subquery slow |
| 48703 | 2009-11-11 21:58 | 2022-09-04 20:45 | MySQL Server: Optimizer | In progress (5071 days) | S3 | 5.0+ | Any | Any | nontrivial ORDER/GROUP BY expressions: ambiguous statements not detected |
| 24251 | 2006-11-13 10:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | In progress (5267 days) | S5 | 5.0.30-BK, 5.1.12 | Linux (Linux, Win XP SP2) | Any | Non-optimal choice of indexes for queries |
| 44549 | 2009-04-29 17:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0.80, 5.1.34 | Any | Any | optimizer incorrectly chooses table scan and filesort over index |
| 45680 | 2009-06-23 14:15 | 2020-04-01 13:16 | MySQL Server: Optimizer | Verified | S3 | 5.0.54, 5.0.82, 5.1.35, 6.0.12 | Any | Any | wrong results when using index for lookup with implicitly casted values |
| 45880 | 2009-07-01 14:21 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1 | Any | Any | OUTER JOINed tables with no condition in WHERE must be at the end of explain |
| 46056 | 2009-07-08 20:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0,5.1,5.4 | Any | Any | Duplicate rows returned on MAX + ORDER BY |
| 46217 | 2009-07-16 11:16 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0,5.1,5.4 | Any | Any | Wrong result on aggregate + JOIN + ORDER BY + LIMIT |
| 46277 | 2009-07-17 21:33 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1, 5.4, 6.0 | Any | Any | differing results for equivalent queries using VAR_POP() & AVG() with DISTINCT |
| 46283 | 2009-07-18 15:22 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0, 5.1, 5.4, 6.0 | Any | Any | COUNT() returning bad values when LIMIT 1 clause added to query |
| 46517 | 2009-08-02 21:54 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.4,5.6.99 | Any | Any | Queries with constant / null only WHERE clause interpreted differently in azalea |
| 48049 | 2009-10-14 16:46 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1.37, 5.5.7 | Any | Any | SELECT MIN(1) reports differently for MERGE tables in 5.0 and 5.1 |
| 48103 | 2009-10-16 0:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1, 6.0 | Any | Any | Using STRAIGHT_JOIN with Innodb tables can produce duplicate results |
| 48190 | 2009-10-20 14:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1,6.0 | Any | Any | Error processing ALL subqueries on empty sets - different than JavaDB/Postgres |
| 49590 | 2009-12-10 16:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0+ | Any | Any | Server reporting different result sets for a query depending on use of indexes |
| 50388 | 2010-01-16 4:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S5 | 5.1.41,5.1.42, 5.1.43-bzr | Any | Any | partition pruning not working with some right joins |
| 54179 | 2010-06-02 11:37 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1.37 , 5.1.47 , 5.5.4 | Any | Any | Index is not used for range scan on SET field |
| 60023 | 2011-02-08 21:45 | 2014-05-22 12:13 | MySQL Server: Optimizer | Verified | S5 | 5.5.8 , 5.1.51 | Any | Any | No Loose Index Scan for GROUP BY / DISTINCT on InnoDB partitioned table |
| 69350 | 2013-05-30 5:44 | 2014-02-20 5:48 | MySQL Server: Optimizer | Verified | S5 | 5.6 | Any | Any | performance regression between 5.5 and 5.6 for simple statement in routine loop |
| 69891 | 2013-08-01 6:33 | 2014-09-18 21:25 | MySQL Server: Optimizer | Verified | S3 | 5.1.31 | Any | Any | since 5.1.31 REPLACE() function concats it's results under certain conditions |
| 72501 | 2014-05-01 17:31 | 2014-05-01 18:12 | MySQL Server: Optimizer | Verified | S3 | 5.6.17 | Any | Any | joining NULLs + different collation is not efficient |
| 80206 | 2016-01-30 6:13 | 2016-01-30 6:13 | MySQL Server: Optimizer | Verified | S3 | 5.7.10 | Any | Any | EQ_REF extension should be skipped for the last joined table |
| 95543 | 2019-05-27 12:37 | 2019-05-29 12:34 | MySQL Server: Optimizer | Verified | S2 | 5.7.26 | Any | Any | optimizer prefers index for order by rather than filtering - (70x slower) |
| 108863 | 2022-10-24 16:40 | 2024-03-15 8:49 | MySQL Server: Optimizer | Verified | S5 | 8.0.31 | Any | Any | different index picked when row is not found, marginally slower |
| 114751 | 2024-04-24 2:53 | 2024-04-24 7:24 | MySQL Server: Optimizer | Verified (1 day) | S1 | 8.0.36 | Any | Any | Incorrect query result |
| 114762 | 2024-04-24 10:05 | 2024-04-24 13:22 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0 | Any | Any | invalid result set with join lateral and group by on a generated field |
| 114741 | 2024-04-23 9:43 | 2024-04-23 13:36 | MySQL Server: Optimizer | Verified (2 days) | S3 | 8.0 | Any | Any | Inconsistent query results caused by different execution of subqueries |
| 114714 | 2024-04-20 3:54 | 2024-04-22 9:33 | MySQL Server: Optimizer | Verified (3 days) | S3 | 8.0.33 | Any | Any | Duplicate subquery explain plan output when explain format is tree |
| 114719 | 2024-04-21 14:31 | 2024-04-22 7:46 | MySQL Server: Optimizer | Verified (3 days) | S1 | 8.0.36 | Any | Any | Incorrect results caused by different access types for an index |
| Showing 1-30 of 749 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
