Showing 1-30 of 908 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
72294 | 2014-04-09 17:28 | 2014-04-10 6:24 | MySQL Server: Optimizer | Verified (4113 days) | S3 | 5.5-debug, 5.6-debug | Any | Any | Assertion `0' fails on killing INSERT .. SELECT into a FEDERATED table |
114581 | 2024-04-08 11:24 | 2024-04-08 12:37 | MySQL Server: Optimizer | Verified (462 days) | S2 | 8.0.36 | Any | Any | Constant-Folding optimization negative constant truncate gives wrong operator |
116724 | 2024-11-20 7:44 | 2024-11-20 8:49 | MySQL Server: Optimizer | Verified (236 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with CASE statements |
116725 | 2024-11-20 7:44 | 2024-11-20 8:54 | MySQL Server: Optimizer | Verified (236 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with CASE statements. |
116722 | 2024-11-20 7:11 | 2024-11-20 7:37 | MySQL Server: Optimizer | Verified (236 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the COALESCE function. |
77340 | 2015-06-12 22:34 | 2015-12-18 10:58 | MySQL Server: Optimizer | Verified (3496 days) | S3 | 5.6.25, 5.7.7 | Any | Any | Optimizer chooses wrong index for LEFT JOIN query |
78612 | 2015-09-28 22:46 | 2022-11-12 22:13 | MySQL Server: Optimizer | Verified (3575 days) | S3 | 5.5.45, 5.6.26, 5.7.8,5.5.47, 5.6.28,5.7.10 | Any | Any | Optimizer chooses wrong index for ORDER BY |
117809 | 2025-03-27 13:06 | 2025-03-27 20:10 | MySQL Server: Optimizer | Verified (109 days) | S5 | Any | Any | Statistics update failed. | |
116034 | 2024-09-08 16:54 | 2024-09-09 7:05 | MySQL Server: Optimizer | Verified (308 days) | S3 | 8.4.2, 8.0.39, 9.0.1 | Any | Any | Unexpected behavior when subquery returns an empty set |
93606 | 2018-12-14 7:53 | 2021-11-23 15:30 | MySQL Server: Optimizer | Verified (2377 days) | S2 | 5.6.40,5.7.24 | CentOS (6.9) | x86 | when use Connector/J preparestatement mysql returns the wrong result |
53793 | 2010-05-19 9:52 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5535 days) | S3 | 6.0-codebase-bugfixing | Any | Any | "early NULL filtering" not done for outer join converted to inner join |
58928 | 2010-12-14 20:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5326 days) | S3 | 5.1-bugteam | Any | Any | "not exists" optimization not applied if relevant table is not single inner one |
45776 | 2009-06-26 7:17 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5862 days) | S5 | mysql-5.1.35 | Linux | Any | "OR" condition on SPATIAL index not optimized |
80802 | 2016-03-21 9:22 | 2016-03-21 10:56 | MySQL Server: Optimizer | Verified (3402 days) | S3 | 5..1/5.5/5.6/57 | Any | Any | "ORDER BY expression" does not allow alias to aggregate |
76501 | 2015-03-27 6:50 | 2015-03-27 15:11 | MySQL Server: Optimizer | Verified (3762 days) | S3 | 5.6.22 | Any | Any | "select + distinct + group by " works incorrectly |
94224 | 2019-02-06 16:45 | 2019-11-17 10:39 | MySQL Server: Optimizer | Verified (2349 days) | S3 | 5.6, 5.6.43 | Any (any) | Any (any) | [5.6] Optimizer reconsiders index based on index definition order, not value |
66849 | 2012-09-17 18:49 | 2013-06-10 19:50 | MySQL Server: Optimizer | Verified (4417 days) | S1 | 5.5.16, 5.1.70, 5.5.32, 5.6.12 | Linux | Any | [REGRESSION] this query hangs the server (100% CPU for several minutes) |
109363 | 2022-12-13 13:08 | 2022-12-16 14:50 | MySQL Server: Optimizer | Verified (941 days) | S3 | 8.0.4, 8.0.31 | Any | Any | 0 changed to -0 caused by DISTINCT and UNION ALL |
108946 | 2022-11-01 3:35 | 2022-12-13 4:12 | MySQL Server: Optimizer | Verified (944 days) | S3 | 8.0.30 | Any | Any | 0 changed to 0.0 caused by DISTINCT and UNION ALL |
66825 | 2012-09-14 22:38 | 2012-09-15 18:02 | MySQL Server: Optimizer | Verified (4685 days) | S3 | 5.5.27 | Any | Any | 5.5 ignores an index if BINARY is used |
118020 | 2025-04-20 23:23 | 2025-05-19 14:51 | MySQL Server: Optimizer | Verified (56 days) | S1 | 9.2.0, 9.3.0 | Any (22.04) | Any | A critical logic bug and performance bug |
58924 | 2010-12-14 18:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5325 days) | S3 | 5.1.44, 5.0, 5.1, 5.6.1 | Linux | Any | a LIMIT after a UNION doesn't propogate to all queries |
68044 | 2013-01-06 22:02 | 2013-01-07 1:30 | MySQL Server: Optimizer | Verified (4571 days) | S3 | 5.5.30 | Any | Any | A minor bug in check_simple_equality() |
118548 | 2025-06-28 7:56 | 2025-06-30 6:45 | MySQL Server: Optimizer | Verified (14 days) | S3 | 9.2.0, 9.3.0 | Linux | x86 | A potential bugs in Mysql Server |
118544 | 2025-06-27 14:18 | 2025-06-30 6:43 | MySQL Server: Optimizer | Verified (14 days) | S3 | 9.2.0 , 9.3.0 | Linux | Any | A potential join operator bug |
118018 | 2025-04-20 13:49 | 2025-05-19 14:53 | MySQL Server: Optimizer | Verified (56 days) | S1 | 9.2.0, 9.3.0 | Ubuntu (22.04) | Any | A query expose a logic bug and performance bug |
72646 | 2014-05-14 9:40 | 2014-05-14 12:17 | MySQL Server: Optimizer | Verified (4079 days) | S3 | 5.5 5.6, 5.6.19 | Any | Any | A strange result from explain query |
118017 | 2025-04-20 10:59 | 2025-05-19 14:53 | MySQL Server: Optimizer | Verified (56 days) | S5 | 9.2.0, 9.3.0 | Ubuntu (22.04) | Any | A very serious performance bug |
95776 | 2019-06-13 2:34 | 2019-06-13 5:38 | MySQL Server: Optimizer | Verified (2223 days) | S3 | 5.7.15-log MySQL Community Server (GPL), 5.6.44, 5.7.26, 8.0.16 | CentOS | Any | About FUNCTION STDDEV_SAMP:Data only in different order |
104978 | 2021-09-17 19:57 | 2021-09-20 9:02 | MySQL Server: Optimizer | Verified (1393 days) | S5 | 8.0.26, 5.7.35 | Windows | Any | Adding Join Index forces query optimizer to use inefficient execution plan |
Showing 1-30 of 908 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |