Showing 1-10 of 585 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
118625 | 2025-07-10 3:04 | 2025-07-10 8:26 | MySQL Server: DDL | Analyzing (5 days) | S3 | 9.3.0 | Any | Any | index makes query generate incorrect result |
118571 | 2025-07-02 7:27 | 2025-07-02 8:56 | MySQL Server: DML | Analyzing (13 days) | S3 | 8.0.41 | Any | Any | using index lookup, the query return a wrong result; |
45130 | 2009-05-27 13:03 | 2013-03-03 20:45 | MySQL Server: FULLTEXT search | In progress (5787 days) | S3 | 5.0 and later | Any | Any | Incorrect results with multiple MATCH() against a table with no fulltext indexes |
117165 | 2025-01-09 6:53 | 2025-07-14 7:53 | MySQL Server: DML | Need Feedback (1 day) | S5 | 8.0.36 | Any | Any | load data local infile replace have poor performance |
118549 | 2025-06-28 17:53 | 2025-06-30 12:42 | MySQL Workbench: Administration | Need Feedback (15 days) | S3 | Any | Any | index | |
52620 | 2010-04-06 15:06 | 2023-02-12 20:45 | MySQL Server: Replication | Patch queued (5257 days) | S3 | 5.0.84 | Any | Any | Crash can leave null characters in binary log index file |
76639 | 2015-04-09 10:49 | 2015-04-09 10:53 | MySQL Server: Logging | Verified | S3 | 5.6.20 | Any | Any | Index Merge (sort_union) plan gets picked up by log_queries_not_using_indexes=1 |
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 |
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) |
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 |
Showing 1-10 of 585 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |