Showing 1-30 of 735 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
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 |
114510 | 2024-03-29 6:42 | 2024-03-29 7:29 | MySQL Server: Optimizer | Verified | S2 | 8.0.36 | Linux | x86 | Inconsistent results after dropping index on join column |
114301 | 2024-03-11 16:40 | 2024-03-12 16:23 | MySQL Server: Optimizer | Verified (17 days) | S3 | 8.0 | Any | Any | Incorrect result with IS NULL predicate in join condition |
114237 | 2024-03-06 6:57 | 2024-03-06 8:30 | MySQL Server: Optimizer | Verified (23 days) | S5 | 8.2.0, 8.3.0 | Any | Any | Unexpected Cardinality by Index |
112902 | 2023-10-31 14:39 | 2024-02-26 11:07 | MySQL Server: Optimizer | Verified (32 days) | S5 | 8.0.31, 8.0.35 | Linux (n.a.) | x86 (x86_64) | Optimizer in MySQL 8 is significantly slower on dependent subqueries than 5.7 |
114092 | 2024-02-22 23:40 | 2024-02-26 14:58 | MySQL Server: Optimizer | Verified (34 days) | S5 | Ver 8.0.36-0 | Ubuntu (ubuntu 22.04.1) | x86 (Linux on x86_64 ((Ubuntu))) | WHERE statement on an indexed decimal column hangs |
114027 | 2024-02-17 19:34 | 2024-02-19 6:29 | MySQL Server: Optimizer | Verified (39 days) | S3 | 8.0.36 & 8.3.0 | Windows (10 & 11) | ARM (x64) | Plans for inner hash join show that wrong table is hashed |
113892 | 2024-02-05 10:39 | 2024-02-05 14:13 | MySQL Server: Optimizer | Verified (53 days) | S3 | 8.0 | Any | Any | FORCE INDEX reports wrong number of rows |
110656 | 2023-04-11 16:02 | 2024-01-26 9:27 | MySQL Server: Optimizer | Verified (63 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | Join query with wrong result |
113736 | 2024-01-24 9:44 | 2024-01-24 14:03 | MySQL Server: Optimizer | Verified (65 days) | S3 | 8.3 | MacOS (14.3) | ARM | Test main.qualify_hypergraph failing with a result difference |
Showing 1-30 of 735 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |