| Showing all 241 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 116418 | 2024-10-19 13:14 | 2024-10-20 14:35 | MySQL Server: InnoDB storage engine | Closed (330 days) | S2 | Any | Any | innodb_cached_indexes no longer shows cached_indexes but page reads | |
| 118022 | 2025-04-21 4:12 | 2025-04-28 12:23 | MySQL Server: DML | Not a Bug (139 days) | S2 | Any | Any | between date and str_TO_DATE in select where returns incorrect result | |
| 118260 | 2025-05-23 16:25 | 2025-06-26 1:00 | MySQL Server: Compiling | No Feedback (81 days) | S1 | Other (OpenSUSE) | x86 | ld can't find stdc++ | |
| 118269 | 2025-05-26 9:41 | 2025-05-26 12:29 | MySQL Server: Optimizer | Closed (111 days) | S2 | Any | Any | The result of anti disk hash join is wrong | |
| 117702 | 2025-03-14 8:48 | 2025-03-14 10:29 | MySQL Server: Optimizer | Verified (184 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Query Results When Using DISTINCT and Logical AND in Subquery |
| 117847 | 2025-04-02 6:29 | 2025-04-02 7:47 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | NULLIF Filtering Fails in WHERE Clause |
| 117855 | 2025-04-02 7:37 | 2025-04-02 8:15 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0 , 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | QUOTE Function Incorrectly Handles NULL Values |
| 117703 | 2025-03-14 9:00 | 2025-03-14 10:39 | MySQL Server: Optimizer | Verified (184 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Query Results When Using REPEAT (Branch Structure) in Subquery |
| 117704 | 2025-03-14 9:24 | 2025-03-14 10:49 | MySQL Server: Optimizer | Verified (184 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | WHERE Clause Fails to Filter NULL Values in Condition (col1 = col2) |
| 117848 | 2025-04-02 6:37 | 2025-04-02 9:50 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | INTERVAL Function Incorrectly Filters Results in WHERE Clause |
| 117849 | 2025-04-02 6:52 | 2025-04-02 9:48 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Query Results When Using Nested String Operation Functions with Conditional Expressions as Inner Parameters |
| 117851 | 2025-04-02 7:05 | 2025-04-02 9:45 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Behavior of EXISTS Condition with OR in SQL Query |
| 117852 | 2025-04-02 7:14 | 2025-04-08 15:00 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Handling of NULL Values with FIELD Function in SQL Query |
| 117853 | 2025-04-02 7:23 | 2025-04-02 9:27 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Result When Using LEFT OUTER JOIN with Subquery |
| 117854 | 2025-04-02 7:31 | 2025-04-02 8:35 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | Incorrect Filtering Behavior of MAKE_SET Function |
| 117856 | 2025-04-02 7:42 | 2025-04-02 8:01 | MySQL Server: Optimizer | Verified (165 days) | S2 | 9.1.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu (20.04) | Any | REPEAT Function Causes Row Loss in WHERE Clause |
| 118916 | 2025-08-31 18:26 | 2025-09-05 8:21 | MySQL Server: Optimizer | Duplicate (9 days) | S2 | 9.4.0 | Any | Any | Incorrect result set when querying view with LEFT JOIN, COALESCE and EXISTS subquery |
| 118918 | 2025-09-01 7:30 | 2025-09-04 11:47 | MySQL Server: Optimizer | Verified (11 days) | S2 | 9.4.0 | Any | Any | Inconsistent NULL handling in CTE LEFT JOIN results |
| 118937 | 2025-09-04 4:36 | 2025-09-10 0:43 | MySQL Server: Optimizer | Verified (5 days) | S2 | 9.4.0 | Any | Any | LEFT JOIN with constant functions returns incorrect results when condition is ON FALSE |
| 117714 | 2025-03-14 15:36 | 2025-03-21 1:11 | MySQL Server: Optimizer | Verified (180 days) | S2 | 5.7.42 | Any | Any | Incorrect row filtering when using CAST(... AS DATE) adding an AND condition. |
| 118669 | 2025-07-16 5:22 | 2025-07-16 6:46 | MySQL Server: Optimizer | Verified (60 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Issue in applying limit on aggregated data |
| 118912 | 2025-08-28 16:24 | 2025-09-04 11:48 | MySQL Server: Optimizer | Verified (13 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Mismatch in Column values with SUM of IFNULL vs IFNULL of SUM |
| 117619 | 2025-03-05 0:14 | 2025-03-05 5:53 | MySQL Server: Optimizer | Verified (193 days) | S2 | 8.*, 8.0.41, 8.0.44 | Any | Any | MySQL indexes in MyISAM tables not behave as expected. |
| 116142 | 2024-09-18 11:34 | 2025-01-21 11:13 | MySQL Server: InnoDB storage engine | Verified (360 days) | S2 | 8.0 | Any | Any | Add another uk to a field that already has a uk results in a duplicate key error |
| 116398 | 2024-10-17 14:34 | 2024-10-25 9:40 | MySQL Server: Optimizer | Verified (324 days) | S2 | 8.0 | Any | Any | Incorrect result with LEFT JOIN and small join_buffer_size |
| 117135 | 2025-01-08 11:54 | 2025-01-10 12:04 | MySQL Server: DDL | Verified (247 days) | S2 | 8.0 | Any | Any | When executing online ddl rebuilt table, concurrent delete operations may cause row_log memory to be read out of bounds. |
| 117241 | 2025-01-20 7:42 | 2025-02-08 6:21 | MySQL Server: DDL | Not a Bug (218 days) | S2 | 8.0 | Any | Any | Adding an auto-increment primary key to an InnoDB table may lead to data inconsistency. |
| 117281 | 2025-01-23 10:27 | 2025-01-23 17:01 | MySQL Server: Compiling | Verified (234 days) | S2 | 8.0 | Any | Any | sql/table_cache.cc init does not cleanup on failure |
| 117436 | 2025-02-11 7:22 | 2025-04-29 10:27 | MySQL Server: InnoDB storage engine | Verified (151 days) | S2 | 8.0 | Any | Any | PCursor::move_to_next_block may skip records incorrectly |
| 118046 | 2025-04-23 21:21 | 2025-05-22 10:34 | MySQL Server: Stored Routines | Verified (115 days) | S2 | 8.0 | Any | Any | KILL (QUERY) should check thread ownership against the security context that initiated the current operation |
| 118367 | 2025-06-05 9:18 | 2025-06-06 10:06 | MySQL Server: Data Dictionary | Verified (100 days) | S1 | 8.0 | Any | Any | The server may fail to start again if it exits abnormally during the upgrade |
| 118705 | 2025-07-23 8:06 | 2025-08-13 11:06 | MySQL Server: InnoDB storage engine | Verified (51 days) | S2 | 8.0 | Any | Any | when call que_eval_sql, may crash. |
| 117036 | 2024-12-23 7:28 | 2024-12-31 5:43 | MySQL Server: GIS | Verified (265 days) | S2 | 8.0, 8.0.40 | Any | Any | Spatial Index causes CHECK TABLE to fail |
| 116741 | 2024-11-21 6:58 | 2024-11-22 1:05 | MySQL Server: Optimizer | Verified (296 days) | S2 | 8.0, 8.0.40, 8.4.3 | Any | Any | Innodb tmp table causes incorrect query results |
| 117242 | 2025-01-20 9:13 | 2025-01-20 9:50 | MySQL Server: Optimizer | Verified (237 days) | S2 | 8.0, 8.0.40, 8.4.3 | Ubuntu | x86 | DISTINCT does not fetch all distinct rows when used with GROUP BY |
| 117395 | 2025-02-06 1:56 | 2025-03-03 14:02 | MySQL Server: FULLTEXT search | Verified (195 days) | S1 | 8.0, 8.0.41 | Any | Any | FTS checks table with FK constraints without acquiring MDL |
| 117386 | 2025-02-05 10:13 | 2025-02-05 13:51 | MySQL Server: Optimizer | Verified (221 days) | S2 | 8.0, 8.0.41, 8.4.4 | Ubuntu | x86 | Ambiguous functional index not based on any column under-fetches rows |
| 117549 | 2025-02-24 2:24 | 2025-02-24 4:52 | MySQL Server: Optimizer | Verified (202 days) | S1 | 8.0, 8.0.41, 8.4.4 | Any | Any | Wrong result when use "in (select * from (set operation) d)" |
| 117439 | 2025-02-11 14:27 | 2025-02-20 13:12 | MySQL Server: Optimizer | Verified (214 days) | S2 | 8.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu | x86 | Suspicious behaviour around creation of multi-column indexes |
| 117653 | 2025-03-10 3:22 | 2025-03-10 5:36 | MySQL Server: Optimizer | Verified (188 days) | S2 | 8.0, 8.0.41, 8.4.4, 9.2.0 | Ubuntu | x86 | Invisible index affects output of query result |
| 118682 | 2025-07-18 3:52 | 2025-07-24 6:33 | MySQL Server: Options | Verified (52 days) | S2 | 8.0, 8.0.42 | Any | Any | connection_memory_limit and global_connection_memory_limit don't work |
| 118476 | 2025-06-18 8:45 | 2025-07-02 14:47 | MySQL Server: DDL | Verified (88 days) | S2 | 8.0, 8.4 | Red Hat | x86 | Unable to create partition with name '1e3fRQM2GhI' |
| 116319 | 2024-10-09 6:50 | 2024-10-10 3:58 | MySQL Server: InnoDB storage engine | Verified (340 days) | S2 | 8.0, 8.4, 8.0.39 | Any | Any | When locks exhaust the BP, an incorret assert about semi_consistent causes crash |
| 118322 | 2025-06-01 4:47 | 2025-07-20 1:00 | MySQL Server: Replication | No Feedback (57 days) | S2 | 8.0.20 | Any | x86 | Result of `show master status` is not correct !!! |
| 117732 | 2025-03-18 2:27 | 2025-03-18 6:19 | MySQL Server: Storage Engines | Can't repeat (180 days) | S2 | 8.0.22 | Any | Any | Server crashed when parallel read is enabled for select count query |
| 118186 | 2025-05-13 15:34 | 2025-05-19 11:51 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (118 days) | S2 | 8.0.22 | Linux | Any | With row‑based replication (binlog_format = ROW), the function generates duplicate sequence values; in mixed mode (binlo |
| 116673 | 2024-11-15 3:37 | 2024-11-15 19:35 | MySQL Server: Group Replication | Can't repeat (303 days) | S1 | 8.0.25 | Any | Any | gtid exists，but data and binlog lost |
| 117086 | 2024-12-31 9:52 | 2025-01-02 1:51 | MySQL Server: Replication | Can't repeat (255 days) | S1 | 8.0.25 | Any | Any | replace into can cause 1062 error |
| 117423 | 2025-02-10 10:20 | 2025-02-12 8:49 | MySQL Server: Pluggable Authentication | Verified (215 days) | S2 | 8.0.28, 8.0.41 | Any | Any | RETAIN PASSWORD not working with Non Built-in authentication plugins |
| 116815 | 2024-11-28 3:51 | 2025-07-08 5:00 | MySQL Server: InnoDB storage engine | Not a Bug (68 days) | S2 | 8.0.30 | Any | Any | INSERT locks primary key supremum after secondary index duplicate key collision |
| 118805 | 2025-08-09 12:04 | 2025-08-19 8:34 | MySQL Server: Pluggable Authentication | Verified (26 days) | S2 | 8.0.30, 8.0.43, 8.4.6 | Windows (11 Pro) | x86 (64 bit) | mysqld fails to start |
| 117777 | 2025-03-24 9:15 | 2025-03-26 5:03 | MySQL Server: InnoDB storage engine | Can't repeat (172 days) | S1 | 8.0.31 | Any | Any | mysql crash Assertion failure: rec.cc:384 |
| 116277 | 2024-10-01 14:57 | 2024-10-01 20:52 | MySQL Server: Data Types | Duplicate (348 days) | S2 | 8.0.32 | Any | Any | Insert rounds datetime/timestamp fractions instead of truncating |
| 117187 | 2025-01-13 7:33 | 2025-02-13 19:37 | MySQL Server: Charsets | Not a Bug (244 days) | S2 | 8.0.32, 8.0.39, 8.0.40, 8.4.3 | Any | Any | Cannot convert string '\xA0' from binary to utf8mb4 |
| 117783 | 2025-03-25 8:45 | 2025-03-26 8:20 | MySQL Server: Optimizer | Verified (172 days) | S2 | 8.0.32, 8.0.41 | Any | Any | optimizer selects the wrong index due to the "low_limit" mechanism |
| 117917 | 2025-04-08 16:01 | 2025-05-10 1:00 | MySQL Server: InnoDB storage engine | No Feedback (128 days) | S1 | 8.0.32、5.7.44 | Linux | x86 | InnoDB: Failing assertion: lock->lock_word == X_LOCK_DECR |
| 117646 | 2025-03-09 9:18 | 2025-04-12 1:00 | MySQL Server: InnoDB storage engine | No Feedback (156 days) | S2 | 8.0.34 | Any | Any | InnoDB Purge Process Inefficiency on Idle Serve |
| 117337 | 2025-01-30 12:09 | 2025-02-03 11:47 | MySQL Server: Storage Engines | Verified (226 days) | S2 | 8.0.34-26, 8.0.41 | Any | Any | Transaction Commit Allowed on Blackhole Table After read_only=1 is Enabled |
| 117419 | 2025-02-10 4:45 | 2025-02-10 7:08 | MySQL Server: Stored Routines | Verified (216 days) | S2 | 8.0.34, 8.0.41, 8.4.4, 9.2.0 | Any | Any | BEFORE INSERT trigger causes all columns in DEFAULT value expression to be NULL |
| 117598 | 2025-02-28 3:28 | 2025-04-01 5:09 | MySQL Server: Optimizer | Verified (198 days) | S2 | 8.0.35, 8.0.41, 8.4.4 | Any | Any | Wrong sort order for queries with ORDER BY DESC when using range comparison with LIMIT |
| 117424 | 2025-02-10 11:06 | 2025-06-11 12:16 | MySQL Server: Group Replication | Duplicate (95 days) | S2 | 8.0.35,8.4.2,8.0.40 | Red Hat (8) | x86 | InnoDB Cluster with group_replication_paxos_single_leader=ON unable to process write traffic |
| 116245 | 2024-09-26 15:23 | 2024-11-01 1:00 | MySQL Server: Group Replication | No Feedback (319 days) | S2 | 8.0.36 | Red Hat ( 4.18.0-553.8.1.el8_10.x86_64) | x86 | innodb cluster / GR error after import w/ has_generated_invisible_primary_key=0 |
| 118043 | 2025-04-23 16:32 | 2025-06-11 12:17 | MySQL Server: Group Replication | Duplicate (95 days) | S2 | 8.0.36 | CentOS | x86 | mgr single leader mode tps slow down and 0 in the end when network is unstable |
| 116584 | 2024-11-07 11:58 | 2024-11-10 6:46 | MySQL Server: Charsets | Verified (311 days) | S2 | 8.0.36, 8.0.40 | Any (Redhat 7.4) | Any (Intel) | Query produces different resultset with force index |
| 116762 | 2024-11-24 9:01 | 2024-12-03 22:44 | MySQL Server: Optimizer | Closed (285 days) | S2 | 8.0.36, 8.0.40, 8.4.3 | Any (Redhat 7.4) | Any (Intel) | Optimizer gives 'Impossible where' without considering field collation |
| 116688 | 2024-11-18 3:23 | 2024-11-18 6:46 | MySQL Server: JSON | Verified (300 days) | S2 | 8.0.36, 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Behavior in `CASE` Statement with JSON Null Values |
| 118710 | 2025-07-23 12:08 | 2025-07-23 12:42 | MySQL Server: Optimizer | Verified (53 days) | S1 | 8.0.36, 8.0.42, 8.0.43, 8.4.6 | Windows | Any | Optimizer incorrectly simplifies negative float/decimal comparison in JOIN condition, leading to wrong results |
| 116576 | 2024-11-07 7:58 | 2024-12-29 1:00 | MySQL Server: Replication | No Feedback (260 days) | S1 | 8.0.37 | CentOS | Any | InnoDB Deadlock and Assertion Failure Leading to MySQL Crash |
| 116863 | 2024-12-04 6:47 | 2024-12-04 7:03 | MySQL Server: DML | Verified (284 days) | S2 | 8.0.37, 8.0.40, 8.4.3, 9.1.0 | Linux | Any | Queries data of the time type, the returned result is incorrect |
| 118101 | 2025-05-01 23:58 | 2025-05-13 15:59 | MySQL Server: Data Dictionary | Verified (124 days) | S2 | 8.0.37, 8.0.41, 8.0.42 | Linux | Any | In-Place upgrade fails with out of memory when instance has large number of routines |
| 117674 | 2025-03-12 6:20 | 2025-03-17 9:46 | MySQL Server: JSON | Verified (181 days) | S2 | 8.0.37, 8.0.41, 8.4.4 | Any | Any | JSON value is not recognized by Mysql inside Stored Routines |
| 118411 | 2025-06-10 15:52 | 2025-07-21 11:44 | MySQL Server: InnoDB storage engine | Verified (55 days) | S2 | 8.0.37, 8.0.42 | CentOS | x86 | Performance degradation in write workload after rebuilding table with row_format=compressed |
| 116964 | 2024-12-13 8:06 | 2024-12-13 9:31 | MySQL Server: Optimizer | Verified (275 days) | S2 | 8.0.38, 8.0.40 | Linux | Any | Result mismatch caused by derived condition push down. |
| 116312 | 2024-10-07 16:51 | 2024-11-02 20:46 | MySQL Server: Replication | Can't repeat (316 days) | S1 | 8.0.39 | Red Hat (Almalinux 8) | x86 | 8.0 replica cannot establish TLS connection with 5.7 replication source |
| 116334 | 2024-10-10 16:10 | 2024-11-22 13:33 | MySQL Server: Optimizer | Closed (312 days) | S2 | 8.0.39 | Any | Any | Incorrect result with LEFT JOIN and small join_buffer_size |
| 118010 | 2025-04-18 9:46 | 2025-04-24 0:27 | MySQL Server: Options | Verified (144 days) | S2 | 8.0.39 | FreeBSD (13.3/14.1) | Any | "Could not increase number of max_open_files to more than 32768" |
| 118510 | 2025-06-23 20:09 | 2025-07-01 12:50 | MySQL Server: FULLTEXT search | Verified (75 days) | S2 | 8.0.39 | Any | Any | InnoDB Match Against does not work properly with utf8mb4_0900_as_ci |
| 116323 | 2024-10-09 13:32 | 2024-11-30 16:06 | MySQL Server: Connection Handling | Verified (288 days) | S2 | 8.0.39, 8.0.40 | Any | Any | Waiting for MDL lock during COM_CHANGE_USER may cause connection leaks |
| 117105 | 2025-01-04 10:02 | 2025-01-06 9:43 | MySQL Server: Optimizer | Verified (253 days) | S2 | 8.0.39, 8.0.40 | Any | Any | Dependent subqueries incorrect results |
| 116619 | 2024-11-11 20:52 | 2025-05-26 21:23 | MySQL Server: Logging | Verified (111 days) | S2 | 8.0.39, 8.0.40, 8.4.3, 9.1.0 | Any | Any | Startup without Signs of Progress with Many Tables (1M+). |
| 116407 | 2024-10-18 10:18 | 2024-10-18 10:53 | MySQL Server: DDL | Verified (331 days) | S2 | 8.0.39, 8.0.40, 9.1.0 | Any | Any | Database Drop Failure Due to Residual .cfp File from Importing Encrypted Tables |
| 116502 | 2024-10-30 4:31 | 2025-01-20 6:58 | MySQL Server: InnoDB storage engine | Verified (318 days) | S2 | 8.0.40 | Any | Any | Duplicate Detection Flaw for NULL Values in UK During DDL Rollback Operations |
| 116532 | 2024-11-03 3:07 | 2024-11-28 14:36 | MySQL Server: Group Replication | Verified (290 days) | S1 | 8.0.40 | Ubuntu (24.04) | x86 (x86-64) | Group Replication cluster deployed across a regional GCP regularly got stuck |
| 116793 | 2024-11-27 3:51 | 2024-11-27 7:14 | MySQL Server: InnoDB storage engine | Verified (291 days) | S2 | 8.0.40 | Any | Any | AHI crash : ut_a(old_index != nullptr) |
| 117042 | 2024-12-25 6:56 | 2024-12-30 13:43 | MySQL Server: GIS | Verified (258 days) | S2 | 8.0.40 | Windows | Any | ST_Within gives unexpected result with Linestring and Polygon in WGS84. |
| 117046 | 2024-12-25 12:44 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (258 days) | S2 | 8.0.40 | Any | Any | Negative buffer of a polygon gives an result that not small enough. |
| 117047 | 2024-12-26 8:27 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (258 days) | S1 | 8.0.40 | Any | Any | ST_Touches always return null with Point and GeometryCollection with Points |
| 117048 | 2024-12-26 9:06 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (258 days) | S2 | 8.0.40 | Any | Any | ST_Buffer gives unexpected reuslt using end_flat strategy with closed Linestring |
| 117063 | 2024-12-28 13:40 | 2024-12-30 13:44 | MySQL Server: GIS | Verified (258 days) | S1 | 8.0.40 | Any | Any | Spatial index causes the disjoint predicate gives wrong result with WHERE,INNER JOIN and CROSS JOIN, |
| 117076 | 2024-12-30 13:38 | 2024-12-30 13:49 | MySQL Server: GIS | Verified (258 days) | S2 | 8.0.40 | Any | Any | ST_Intersection returns a non-empty result for two geometries that are disjoint. |
| 117099 | 2025-01-02 18:20 | 2025-01-08 15:18 | MySQL Server: InnoDB storage engine | Verified (249 days) | S2 | 8.0.40 | Any | Any | Variable innodb_ddl_buffer_size does not limit memory usage in the first phase of an ALTER TABLE |
| 117134 | 2025-01-08 10:25 | 2025-01-08 10:47 | MySQL Server: GIS | Verified (249 days) | S1 | 8.0.40 | Any | Any | ST_Buffer gives unexpected result with LinearRing |
| 117275 | 2025-01-23 7:14 | 2025-01-23 8:39 | MySQL Server: Optimizer | Closed (234 days) | S2 | 8.0.40 | Any | Any | when index_merge is on, the result is incorrect |
| 118074 | 2025-04-28 17:23 | 2025-06-08 1:00 | MySQL Server: InnoDB storage engine | No Feedback (99 days) | S1 | 8.0.40 | Any | x86 | Frequent MySQL Failovers After Upgrade to 8.0.40 |
| 118700 | 2025-07-22 12:55 | 2025-08-25 1:00 | MySQL Server: Replication | No Feedback (21 days) | S2 | 8.0.40 | Any | Any | Due to the master enabling the NO_BACKSLASH_ESCAPES sql_mode, an error occurs during replay on the slave. |
| 118798 | 2025-08-07 9:22 | 2025-08-08 7:36 | MySQL Server: Replication | Verified (37 days) | S1 | 8.0.40 | Ubuntu | Any | Replication Break in 8.0.40 salve when from 8.0.33 Master |
| 117612 | 2025-03-03 22:42 | 2025-03-04 11:05 | MySQL Server: DML | Not a Bug (194 days) | S2 | 8.0.40, 8.0.41, 8.4.4 | Any | Any | EVAL in UPDATE statement changes row value before statement is fully parsed |
| 117186 | 2025-01-13 3:01 | 2025-01-15 6:36 | MySQL Server: DML | Verified (244 days) | S2 | 8.0.40, 8.4.3 | Any | Any | result is incorrect |
| 116564 | 2024-11-06 1:51 | 2024-11-06 12:57 | MySQL Server: Replication | Verified (312 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Replication breaks with partial_revokes when GRANT after DROP current USER. |
| 116778 | 2024-11-26 4:28 | 2024-11-26 7:03 | MySQL Server: InnoDB storage engine | Verified (292 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | mysql crash when optimize table and update |
| 117231 | 2025-01-17 20:50 | 2025-01-27 6:57 | MySQL Server: InnoDB storage engine | Verified (230 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Wrong SDI after upgrade from 8.0.23 because Bug#98501 (Exchanging partition does not update SDI). |
| 117237 | 2025-01-19 4:13 | 2025-01-21 11:41 | MySQL Server: InnoDB storage engine | Verified (236 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Duplicate Error in DDL Row Log Apply |
| 118536 | 2025-06-26 17:55 | 2025-06-27 7:24 | MySQL Server: Optimizer | Analyzing (79 days) | S2 | 8.0.40, 9.3.0 | Linux (RDS, Docker) | Any (Tested on x86_64 and aarch64) | Concurrent CTE queries cause erroneous missing temporary table errors |
| 116760 | 2024-11-23 13:44 | 2025-07-28 5:11 | MySQL Server: InnoDB storage engine | Verified (293 days) | S2 | 8.0.40,8.4.3,9.1.0 | Any | Any | Page deadlock occured when searching BTREE after nullable cols dropped by INSTAN |
| 117259 | 2025-01-22 7:17 | 2025-01-30 1:03 | MySQL Server: InnoDB storage engine | Closed (227 days) | S2 | 8.0.41 | Any | Any | Bugfix of Bug#37318367 in 8.0.41 contains an obvious logical issue |
| 117572 | 2025-02-26 2:37 | 2025-02-26 6:36 | MySQL Server: Optimizer | Verified (200 days) | S2 | 8.0.41 | Ubuntu (22.04) | x86 | The same query yields different results across different versions |
| 117666 | 2025-03-11 10:59 | 2025-03-25 22:54 | MySQL Server: Optimizer | Closed (173 days) | S2 | 8.0.41 | Any | Any | EXPLAIN FORMAT=TREE does not say the index is covering, unlike plain EXPLAIN |
| 117719 | 2025-03-17 2:13 | 2025-03-27 20:10 | MySQL Server: Stored Routines | Verified (172 days) | S2 | 8.0.41 | Any | Any | The event scheduler is not working. |
| 117983 | 2025-04-15 5:58 | 2025-04-15 10:02 | MySQL Server: Data Dictionary | Verified (152 days) | S2 | 8.0.41 | Any | Any | Huge memory usage while upragding data dictionary with many views |
| 118116 | 2025-05-05 17:41 | 2025-06-20 1:00 | MySQL Server: Replication | No Feedback (87 days) | S1 | 8.0.41 | Any | Any | HA_ERR_CORRUPT_EVENT on replication from datetime -> datetime(6) |
| 118168 | 2025-05-12 12:27 | 2025-09-02 7:14 | MySQL Server: Replication | Verified (124 days) | S1 | 8.0.41 | Any | Any | MySQL data dictionary fails to upgrade at startup with lock timeout on ALTER TABLE |
| 118422 | 2025-06-12 2:54 | 2025-06-12 23:46 | MySQL Server: InnoDB storage engine | Can't repeat (94 days) | S2 | 8.0.41 | Any | Any | Assertion failure happens in page_is_comp(get_block->frame) == page_is_comp(page) |
| 118820 | 2025-08-13 7:39 | 2025-08-20 6:01 | MySQL Server: InnoDB storage engine | Verified (26 days) | S2 | 8.0.41 | Any | Any | AHI results the mysqld hung and assertion failure: btr0sea.cc:295:sleep_counter < 60000 |
| 117964 | 2025-04-14 6:21 | 2025-04-16 12:02 | MySQL Server: DDL | Verified (151 days) | S2 | 8.0.41, 8.0.42 | Any | Any | Inconsistent Query Results Between Primary Key and Secondary Index After Online DDL Execution |
| 118071 | 2025-04-28 13:09 | 2025-04-28 14:07 | MySQL Server: Optimizer | Verified (139 days) | S2 | 8.0.41, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Indexed table fails WHERE filtering with different charset value |
| 118092 | 2025-04-30 3:31 | 2025-08-06 12:51 | MySQL Server: DML | Verified (137 days) | S2 | 8.0.41, 8.0.42, 8.4.5, 9.3.0 | Linux | Any | The query result using index is different with not used index |
| 118818 | 2025-08-13 3:44 | 2025-08-18 12:16 | MySQL Server: InnoDB storage engine | Verified (27 days) | S2 | 8.0.41, 8.0.43 | Any | Any | Assertion failure row0pread.h:306:active >= n_threads happens when create thread fail for parallel scan |
| 117927 | 2025-04-10 6:25 | 2025-04-10 7:35 | MySQL Server: JSON | Verified (157 days) | S2 | 8.0.41, 8.4 | Any | Any | duplicate key in table while using tmp table for group by a json data |
| 117707 | 2025-03-14 9:58 | 2025-03-20 12:26 | MySQL Server: Locking | Verified (178 days) | S2 | 8.0.41, 8.4.4, 9.2.0 | Oracle Linux (8.10) | x86 | FLUSH TABLES WITH READ LOCK timeout, but doesn't release the locks |
| 117717 | 2025-03-16 5:05 | 2025-03-16 11:41 | MySQL Server: InnoDB storage engine | Verified (182 days) | S2 | 8.0.41, 8.4.4, 9.2.0 | Any | Any | Import Tablespace Fails Due to Inconsistent max_prefix in dict_col_t After Dropping Index |
| 117941 | 2025-04-10 13:29 | 2025-04-10 14:45 | MySQL Server: Optimizer | Verified (157 days) | S2 | 8.0.41, 8.4.4, 9.2.0 | Any | Any | Inconsistent query results with / without NOT NULL for BLOB type |
| 117926 | 2025-04-09 19:08 | 2025-04-11 21:03 | MySQL Server: Optimizer | Not a Bug (156 days) | S2 | 8.0.41, 9.2.0, 8.4.4 | Ubuntu (22.04) | Any | INTERSECT may incorrectly eliminate duplicate |
| 118913 | 2025-08-29 3:40 | 2025-09-01 10:19 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.41, 9.4.0 | Any | Any | queries have different results for non primary key table and table with primary key |
| 118904 | 2025-08-28 3:20 | 2025-09-04 11:46 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.41+ | Any | Any | Incorrect results could be returned when using index condition pushdown and Range checked for each record |
| 118093 | 2025-04-30 7:13 | 2025-04-30 18:06 | MySQL Server: FULLTEXT search | Verified (137 days) | S2 | 8.0.42 | Any | Any | Huge memory usage when inserting into a FTS table with a single transaction. |
| 118233 | 2025-05-20 13:54 | 2025-05-20 15:04 | MySQL Server: DDL | Verified (117 days) | S2 | 8.0.42 | Any | Any | Fixed a bug in the DDL for invisible indexes. |
| 118594 | 2025-07-07 14:16 | 2025-07-07 14:58 | MySQL Server: InnoDB storage engine | Verified (69 days) | S2 | 8.0.42 | Any | Any | In-place ALTER TABLE ... ADD FOREIGN KEY can sometimes fails with unwarranted error or even crashes |
| 118602 | 2025-07-08 10:26 | 2025-08-19 0:07 | MySQL Server: Replication | Can't repeat (26 days) | S2 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.24.04.1) | x86 | SQL Thread cannot be stopped when last error was 1755 |
| 118299 | 2025-05-29 6:57 | 2025-08-21 2:18 | MySQL Server: InnoDB storage engine | Verified (24 days) | S2 | 8.0.42, 8.4.5 | Any | Any | Multi-valued Index on Composite Key Returns Incomplete Results for Rows with Empty JSON Array('[]') |
| 118356 | 2025-06-04 11:58 | 2025-07-13 10:29 | MySQL Server: Replication | Verified (95 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | MySQL attempts committing transaction not fitting on disk, then crashes. |
| 118358 | 2025-06-04 12:04 | 2025-07-13 10:14 | MySQL Server: InnoDB storage engine | Verified (72 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | Startup without Signs of Progress when Rolling-Back Big Transaction. |
| 118312 | 2025-05-30 8:12 | 2025-05-30 10:32 | MySQL Server: DML | Verified (107 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | Inconsistent results when evaluating `EXCEPT` or `INTERSECT` operations involving `NULL` |
| 118512 | 2025-06-24 7:52 | 2025-06-25 8:13 | MySQL Server: Optimizer | Verified (82 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | The missing semi join condition causes incorrect result |
| 118888 | 2025-08-25 7:19 | 2025-08-29 11:13 | MySQL Server: DDL | Verified (20 days) | S2 | 8.0.43/8.4.6 | Any | Any | DDL operation fills the entire disk space and eventually fails |
| 118941 | 2025-09-05 8:19 | 2025-09-10 14:45 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.0.x, 8.4.x | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with -0.001 Excludes 0.00 Row |
| 118955 | 2025-09-08 9:35 | 2025-09-09 23:51 | MySQL Server: Connection Handling | Not a Bug (5 days) | S1 | 8.043 | MacOS (15.6) | x86 (15.6) | Qt应用程序无法通过ODBC驱动程序从MySQL检索数据，而插入和删除操作工作正常 |
| 118624 | 2025-07-10 2:47 | 2025-07-10 8:15 | MySQL Server: InnoDB storage engine | Verified (66 days) | S1 | 8.3.0, 8.0.42, 8.3.0, 8.4.5, 9.3.0 | Any | Any | Wrong result when icp(push a 'like condition' into engine) |
| 116594 | 2024-11-08 6:13 | 2024-11-26 7:51 | MySQL Server: Compiling | Verified (292 days) | S2 | 8.4, 8.0 | Windows | x86 | [MSVC] MySQL failed to build with msvc on Windows when add ASAN option |
| 118923 | 2025-09-02 7:49 | 2025-09-04 11:46 | MySQL Server: InnoDB storage engine | Verified (11 days) | S2 | 8.4, 8.0.22, 9.4.0 | Any | Any | Abnormal read phenomena are observed under MySQL's Read Committed isolation level |
| 117735 | 2025-03-18 6:21 | 2025-03-18 12:34 | MySQL Server: DDL | Verified (180 days) | S2 | 8.4, 8.0.41 | Any | Any | Concurrent execution of transactions and DDL operations causes abnormal deadlocks. |
| 117348 | 2025-01-31 10:06 | 2025-01-31 13:56 | MySQL Server: Optimizer | Verified (226 days) | S2 | 8.4, 8.0.41, 8.4.4, 9.2.0 | Debian | x86 | Query with DISTINCT in combination with big_tables returns wrong sortorder |
| 118515 | 2025-06-24 9:08 | 2025-07-01 4:35 | MySQL Server: InnoDB storage engine | Verified (76 days) | S2 | 8.4, 8.4.5 | Any | Any | Contribution by Tencent: trx_cleanup_at_db_startup did not clean up trx_sys->shards |
| 118797 | 2025-08-07 2:08 | 2025-08-07 9:17 | MySQL Server: Replication | Verified (38 days) | S2 | 8.4, 8.4.6, 9.4.0 | Any | Any | Contribution by Tencent: previous gtids may loss xa commit/rollback gtids |
| 117691 | 2025-03-12 19:12 | 2025-07-16 6:09 | MySQL Server: InnoDB storage engine | Not a Bug (60 days) | S2 | 8.4.0, 8.4.4, 9.2.0 | Linux | Any | MySQL 8.4 and 9 are not taking advantage of the Linux Page Cache (contrarily to 8.0). |
| 117454 | 2025-02-13 2:08 | 2025-02-13 5:48 | MySQL Server: JSON | Verified (213 days) | S2 | 8.4.1 9.1.0 , 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results with JSON_VALID function in WHERE clause. |
| 117754 | 2025-03-20 7:48 | 2025-03-20 10:10 | MySQL Server: DDL | Verified (178 days) | S2 | 8.4.1 9.1.0 , 8.4.4, 8.0.41 | Windows (windows 11) | x86 (x86_64) | Row counts differ with and without an index for same table. |
| 117223 | 2025-01-17 7:33 | 2025-01-17 9:16 | MySQL Server: Data Types | Verified (240 days) | S2 | 8.4.1 9.1.0, 8.0.40 | Windows | x86 | Query results are unexpected with BIT data type and IN operator. |
| 117451 | 2025-02-13 1:33 | 2025-02-13 4:24 | MySQL Server: Optimizer | Verified (213 days) | S2 | 8.4.1 9.1.0, 8.0.41 | Windows (windows 11) | x86 (x86_64) | Comparing a BIGINT column with the result of an IF function using "=" yields unexpected results. |
| 117453 | 2025-02-13 1:51 | 2025-02-13 5:20 | MySQL Server: DML | Verified (213 days) | S2 | 8.4.1 9.1.0, 8.0.41 | Windows (windows 11) | x86 (x86_64) | Unexpected results with ACOS function in WHERE clause. |
| 117455 | 2025-02-13 2:13 | 2025-02-13 6:30 | MySQL Server: Memory storage engine | Verified (213 days) | S2 | 8.4.1 9.1.0, 8.4.4, 8.0.41 | Windows (windows 11) | x86 (x86_64) | MEMORY engine CHAR type comparison results differ from expectations. |
| 116862 | 2024-12-04 5:11 | 2024-12-04 6:51 | MySQL Server: DML | Verified (284 days) | S2 | 8.4.1, 8.0.40, 8.4.3, 9.1.0 | Red Hat (Linux 3.10.0-1160.102.1.el7.x86_64) | x86 (x86_64) | After deleting the index, the same query produces inconsistent results compared to before. |
| 117233 | 2025-01-18 6:00 | 2025-01-20 5:54 | MySQL Server: DML | Verified (237 days) | S2 | 8.4.1,9.1.0, 8.0.40, 8.4.3 | Windows | x86 | The same query involving TIME type returns different results with and without using an index. |
| 117234 | 2025-01-18 6:35 | 2025-01-20 5:58 | MySQL Server: JSON | Verified (237 days) | S2 | 8.4.1,9.1.0, 8.0.40, 8.4.3 | Windows | x86 | Unexpected results when using JSON_ARRAY(NULL) in query predicates. |
| 117232 | 2025-01-18 5:48 | 2025-01-20 5:29 | MySQL Server: Data Types | Verified (237 days) | S2 | 8.4.1,9.1.0, 8.4.0, 8.4.3 | Windows (windows 11) | x86 | Unexpected results with YEAR data type comparisons in query predicates. |
| 117660 | 2025-03-11 4:23 | 2025-03-11 23:07 | MySQL Server: Replication | Can't repeat (187 days) | S2 | 8.4.2 | Oracle Linux (8.10) | x86 | MySQL 8.4.2: InnoDB Assertion Failure on ha_innodb.cc:11675 Due to strlen(m_remote_path) != 0 After Promoting Replica |
| 116414 | 2024-10-19 6:27 | 2024-10-19 15:07 | MySQL Server: DML | Verified (330 days) | S1 | 8.4.2, 8.0.40 | Ubuntu | Any | BOLB type or operation |
| 116415 | 2024-10-19 6:27 | 2024-11-06 22:52 | MySQL Server: DML | Closed (312 days) | S1 | 8.4.2, 8.0.40 | Ubuntu | Any | Table union data error |
| 116720 | 2024-11-20 6:48 | 2024-11-20 7:37 | MySQL Server: Optimizer | Verified (298 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the combination of CASE and DATE. |
| 116721 | 2024-11-20 7:01 | 2024-11-20 7:37 | MySQL Server: Optimizer | Verified (298 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with combining COALESCE and DATE functions. |
| 116722 | 2024-11-20 7:11 | 2024-11-20 7:37 | MySQL Server: Optimizer | Verified (298 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the COALESCE function. |
| 116723 | 2024-11-20 7:35 | 2024-11-20 8:45 | MySQL Server: Optimizer | Verified (298 days) | S2 | 8.4.2, 8.0.40 | Any | Any | Issues with explicit type casting using CAST. |
| 116724 | 2024-11-20 7:44 | 2024-11-20 8:49 | MySQL Server: Optimizer | Verified (298 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 (298 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with CASE statements. |
| 116726 | 2024-11-20 8:22 | 2024-11-20 8:50 | MySQL Server: Optimizer | Verified (298 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the combination of CAST and DATE. |
| 116727 | 2024-11-20 8:27 | 2024-11-20 8:50 | MySQL Server: Optimizer | Verified (298 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with independent subqueries. |
| 116728 | 2024-11-20 8:32 | 2024-11-20 8:51 | MySQL Server: Optimizer | Verified (298 days) | S1 | 8.4.2, 8.0.40 | Any | Any | Issues with the EXCEPT operator. |
| 118007 | 2025-04-18 2:24 | 2025-04-25 13:30 | MySQL Server: DML | Not a Bug (142 days) | S2 | 8.4.3 | Any | Any | str_TO_DATE( '1980-07-06','YYYY-MM-DD HH24:MI:SS') in dml reports error |
| 118159 | 2025-05-10 2:12 | 2025-05-13 7:37 | MySQL Server: DML | Duplicate (124 days) | S2 | 8.4.3 | Any | Any | recursive CTE with float returns error: Out of range value |
| 116636 | 2024-11-13 5:25 | 2024-11-15 15:26 | MySQL Server: Optimizer | Verified (303 days) | S2 | 8.4.3, 8.0.40, 9.1.0 | Any | Any | Optimizer incorrectly ignores all indexes with NO_INDEX() in some cases |
| 118001 | 2025-04-17 4:15 | 2025-04-21 12:26 | MySQL Server: DML | Verified (146 days) | S2 | 8.4.3, 8.4.5 | Any | Any | delete sql returns error: Temporary file write failure. |
| 117072 | 2024-12-30 9:24 | 2024-12-30 10:06 | MySQL Server: Optimizer | Verified (258 days) | S2 | 8.4.3, 9.1.0, 8.0.40 | Any (Ubuntu 22.04) | Any (x86) | MAX() as a Window Function Returns NULL for the First Row Even With Non-empty Window Frame Under Specific Conditions |
| 118053 | 2025-04-24 15:47 | 2025-05-19 2:25 | MySQL Server: DML | Verified (142 days) | S2 | 8.4.3, 9.3.0, 8.4.5, 8.0.42 | CentOS | Any | cast((NULLIF) as datetime) returns incorrect result |
| 117256 | 2025-01-21 13:19 | 2025-01-28 18:24 | MySQL Server: InnoDB storage engine | Verified (229 days) | S2 | 8.4.4 | Any | Any | Repeating uncaused error "Column cannot be null" after single error on table with trigger |
| 117553 | 2025-02-24 9:15 | 2025-09-04 8:41 | MySQL Server: InnoDB storage engine | Verified (187 days) | S2 | 8.4.4 | Any | Any | Crash caused by race condition between MVCC::view_open and purge view |
| 117563 | 2025-02-25 3:25 | 2025-02-25 7:22 | MySQL Server: DDL | Verified (201 days) | S2 | 8.4.4, 8.0, 9.2.0 | Any | Any | MySQL should check the range of auto-increment values when altering a column |
| 117387 | 2025-02-05 12:39 | 2025-02-05 15:42 | MySQL Server: Optimizer | Verified (221 days) | S2 | 8.4.4, 8.0.41 | Any | Any | Query returns wrong results when using offset limit subquery in view |
| 117606 | 2025-02-28 16:01 | 2025-02-28 16:27 | MySQL Server: Optimizer | Verified (198 days) | S1 | 8.4.4, 8.0.41 | Any | Any | Incorrect query result |
| 117634 | 2025-03-06 14:00 | 2025-03-07 12:59 | MySQL Server: Optimizer | Verified (191 days) | S1 | 8.4.4, 8.0.41 | Any | Any | Incorrect query results |
| 117811 | 2025-03-27 15:19 | 2025-04-03 14:22 | MySQL Server: Optimizer | Verified (170 days) | S1 | 8.4.4, 8.0.41, 9.2.0 | Any | Any | Incorrect query results for BLOB type |
| 118151 | 2025-05-09 8:35 | 2025-06-11 5:04 | MySQL Server: DDL | Verified (95 days) | S2 | 8.4.5 | Ubuntu (22.04) | x86 | When creating an index: ERROR 1553 (HY000): Cannot drop index '<unknown key name>': needed in a foreign key constraint |
| 118217 | 2025-05-16 16:11 | 2025-05-26 10:17 | MySQL Server: Optimizer | Analyzing (111 days) | S1 | 8.4.5 | Ubuntu | x86 | Issues with the NULLIF function. |
| 118842 | 2025-08-14 8:50 | 2025-09-11 2:28 | MySQL Server: InnoDB storage engine | Verified (3 days) | S1 | 8.4.6 | Red Hat (9.4) | x86 | Transactions get stuck in stage/sql/waiting for handler commit until mysqld restart (MySQL 8.4.3), heavy concurrent DML |
| 118885 | 2025-08-24 12:05 | 2025-08-29 11:10 | MySQL Server: Compiling | Verified (20 days) | S2 | 8.4.6 | MacOS | Any | mysql8 @8.4.6: ld: unknown option: -no_warn_duplicate_libraries |
| 118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (24 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
| 117720 | 2025-03-17 2:39 | 2025-03-17 10:14 | MySQL Server: DDL | Verified (181 days) | S2 | 8030, 8.0.41, 8.4.4 | Any | Any | Instant modification causes inconsistency in double data. |
| 116715 | 2024-11-19 17:03 | 2024-11-20 17:23 | MySQL Server: InnoDB storage engine | Verified (298 days) | S2 | 9, 8.4, 8.0 | Any | Any | Optimize Normal Startup with Many Tables. |
| 116163 | 2024-09-19 14:08 | 2024-09-24 12:36 | MySQL Server: Optimizer | Verified (355 days) | S2 | 9.0 | Any | Any | COALESCE(BIT), IF(BIT) return a wrong result |
| 116300 | 2024-10-04 13:44 | 2024-10-04 14:34 | MySQL Server: JSON | Verified (345 days) | S2 | 9.0 | Any | Any | TINYBLOB and BLOB with same value, stored as JSON, become different |
| 116305 | 2024-10-06 11:05 | 2024-10-09 13:54 | MySQL Server: InnoDB storage engine | Verified (340 days) | S2 | 9.0 | Any | Any | row_search_mvcc process wrong page of small buffer pool |
| 116713 | 2024-11-19 15:57 | 2024-11-21 14:15 | MySQL Server: InnoDB storage engine | Verified (298 days) | S2 | 9.0 | Any | Any | Function rename_partition_files should not be in MySQL 9, and more. |
| 118063 | 2025-04-27 19:02 | 2025-04-28 7:39 | MySQL Server: Optimizer | Verified (139 days) | S1 | 9.0, 8.0, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Wrong Join Result after creating index on expressions |
| 118019 | 2025-04-20 16:30 | 2025-04-21 7:56 | MySQL Server: Optimizer | Verified (146 days) | S2 | 9.0, 8.0, 9.3.0, 8.4.5, 8.0.42 | Any | Any | Wrong Right Join with a subquery containing distinct and wrong NULL-value expression optimization |
| 116606 | 2024-11-10 6:44 | 2024-11-11 7:16 | MySQL Server: JSON | Verified (307 days) | S2 | 9.0, 8.0.40, 8.4.3, 9.1.0 | Any | Any | Incorrect Grouping in JSON_OBJECTAGG Aggregation for Case-Sensitive Column |
| 116895 | 2024-12-06 11:45 | 2024-12-25 3:09 | MySQL Server: Optimizer | Verified (282 days) | S2 | 9.0,8.0, 8.0.40, 8.4.3 | Any | Any | View using IN(SELECT LIMIT) has wrong result |
| 116453 | 2024-10-22 21:49 | 2024-10-23 17:27 | MySQL Server: Optimizer | Verified (326 days) | S1 | 9.0.0, 9.1.0 | Any | Any | query_rewrite.flush_rewrite_rules() does not honor binlog_row_metadata=FULL |
| 116307 | 2024-10-07 5:54 | 2024-10-07 6:43 | MySQL Server: Errors | Verified (342 days) | S2 | 9.0.1 | Any | Any | handling of fsp > 255 is incorrect |
| 116517 | 2024-10-31 7:08 | 2024-10-31 10:16 | MySQL Server: Optimizer | Duplicate (318 days) | S2 | 9.1.0 | Any | Any | inner join on = and <=> of null return wrong result |
| 117486 | 2025-02-17 8:04 | 2025-02-17 22:40 | MySQL Server: Optimizer | Verified (209 days) | S2 | 9.1.0, 8.0.41 | Ubuntu (22.04) | x86 | Incorrect Semi-join Execution |
| 117485 | 2025-02-17 7:04 | 2025-02-17 7:53 | MySQL Server: Optimizer | Verified (209 days) | S2 | 9.1.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | x86 | Incorrect Semi-join Execution |
| 117733 | 2025-03-18 2:59 | 2025-03-21 1:13 | MySQL Server: InnoDB storage engine | Verified (180 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Dirty reads due to isolation level settings |
| 117797 | 2025-03-26 5:55 | 2025-06-04 2:18 | MySQL Server: Optimizer | Not a Bug (102 days) | S1 | 9.2.0 | Any (Ubuntu 22.04) | Any | Lost Update WITH CONSISTENT SNAPSHOT |
| 117835 | 2025-03-31 10:44 | 2025-05-12 12:18 | MySQL Server: InnoDB storage engine | Verified (125 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Non Repeatable Read WITH CONSISTENT SNAPSHOT |
| 117860 | 2025-04-02 10:44 | 2025-05-12 12:20 | MySQL Server: Optimizer | Verified (125 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Read another insertion WITH CONSISTENT SNAPSHOT |
| 117911 | 2025-04-08 12:06 | 2025-04-08 14:45 | MySQL Server: Optimizer | Verified (159 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | INTERSECT operation return wrong result |
| 117945 | 2025-04-11 11:10 | 2025-04-11 12:23 | MySQL Server: Optimizer | Verified (156 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | UNION operation may return wrong result[ |
| 117959 | 2025-04-13 0:31 | 2025-04-13 16:37 | MySQL Server: Optimizer | Verified (154 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | PRIMARY KEY leads to incorrect INTERSECT result |
| 118857 | 2025-08-20 8:39 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (25 days) | S2 | 9.2.0 | Linux | Any | Bug Summary: MySQL Returns Incorrect Results for Complex Query with Set Operations |
| 118949 | 2025-09-05 13:57 | 2025-09-10 0:42 | MySQL Server: Optimizer | Verified (6 days) | S2 | 9.2.0 | Linux (ubuntu 20.04) | Any | MySQL 9.2.0: Complex CASE in JOIN makes INNER vs INTERSECT yield different rows |
| 117500 | 2025-02-18 11:40 | 2025-03-11 8:56 | MySQL Server: Optimizer | Verified (208 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Any | Any | result error when row compared with scalar subquery using '<=>' |
| 117573 | 2025-02-26 4:47 | 2025-03-21 7:12 | MySQL Server: Optimizer | Verified (177 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | x86 | Equivalent inner-join queries return different results |
| 117765 | 2025-03-21 3:09 | 2025-03-21 9:01 | MySQL Server: Optimizer | Verified (177 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Any | Any | Query result may be wrong if using compound order by inside GROUP_CONCAT |
| 118684 | 2025-07-18 14:54 | 2025-07-21 6:07 | MySQL Server: Optimizer | Verified (55 days) | S2 | 9.2.0, 8.0.42, 8.4.5 | Linux | Any | Inconsistent rows are returned |
| 118689 | 2025-07-21 11:33 | 2025-08-04 9:43 | MySQL Server: Optimizer | Not a Bug (41 days) | S2 | 9.2.0, 8.0.42, 8.4.5, 9.3.0 | Linux | Any | Inconsistent data returns when using INTERESECT operator |
| 117930 | 2025-04-10 8:29 | 2025-04-11 16:53 | MySQL Server: Optimizer | Not a Bug (156 days) | S2 | 9.2.0, 8.4.4, 8.0.41 | Ubuntu (22.04) | Any | INTERSECT operation fails on INT ZEROFILL column type. |
| 117648 | 2025-03-09 14:15 | 2025-03-10 7:19 | MySQL Server: Optimizer | Verified (188 days) | S2 | 9.2.0, 9.1.0, 8.0.41, 8.4.4, | Ubuntu (22.04) | Any | Equivalent straight-join queries with different join orders return different results. |
| 117651 | 2025-03-09 15:43 | 2025-03-10 6:50 | MySQL Server: Optimizer | Verified (188 days) | S2 | 9.2.0, 9.1.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | Any | STRAIGHT_JOIN produces inconsistent results when comparing text values |
| 117667 | 2025-03-11 12:57 | 2025-03-11 22:03 | MySQL Server: Optimizer | Not a Bug (187 days) | S2 | 9.2.0, 9.1.0, 8.0.41, 8.4.4 | Ubuntu (22.04) | Any | Both INNER JOIN and SEMI JOIN are contradictory |
| 118018 | 2025-04-20 13:49 | 2025-08-12 4:14 | MySQL Server: Optimizer | Verified (118 days) | S1 | 9.2.0, 9.3.0 | Ubuntu (22.04) | Any | A query expose a logic bug and performance bug |
| 118020 | 2025-04-20 23:23 | 2025-08-12 4:14 | MySQL Server: Optimizer | Verified (118 days) | S1 | 9.2.0, 9.3.0 | Any (22.04) | Any | A critical logic bug and performance bug |
| 118090 | 2025-04-29 17:33 | 2025-05-07 11:55 | MySQL Server: Optimizer | Can't repeat (130 days) | S1 | 9.3 | MacOS | Any | Wrong inner join result with the subquery contain -0 |
| 118061 | 2025-04-26 13:02 | 2025-04-28 7:40 | MySQL Server: Optimizer | Verified (139 days) | S1 | 9.3, 8.4.5, 8.0.42 | Any | Any | wrong inner join result when adding an additional true expression |
| 118016 | 2025-04-20 10:34 | 2025-04-21 12:52 | MySQL Server: Optimizer | Verified (147 days) | S2 | 9.3, 9.0, 8.0, 8.0.42 | Any | Any | Wrong inner join result involving subquery containing distinct |
| 118073 | 2025-04-28 15:10 | 2025-04-29 6:29 | MySQL Server: Optimizer | Verified (138 days) | S1 | 9.3,9.0,8.0, 8.0.42 | Any | Any | Wrong Inner Join Result |
| 118085 | 2025-04-29 12:14 | 2025-04-29 13:43 | MySQL Server: Optimizer | Verified (138 days) | S1 | 9.3,9.0,8.0,8.0.42, 8.4.5 | Any | Any | Wrong right join result involving subquery |
| 118024 | 2025-04-21 12:46 | 2025-04-23 8:07 | MySQL Server: Optimizer | Verified (146 days) | S1 | 9.3.0 | Any | Any | Wrong Right Join involving a predicate containing IFNULL and IN |
| 118033 | 2025-04-22 14:51 | 2025-04-23 8:09 | MySQL Server: Optimizer | Verified (144 days) | S2 | 9.3.0 | Any | Any | Wrong Result of an and expression |
| 118195 | 2025-05-14 13:34 | 2025-05-20 8:23 | MySQL Server: Optimizer | Not a Bug (117 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | The opposite WHERE clause intersects and is always an empty set. |
| 118196 | 2025-05-14 13:42 | 2025-05-19 21:16 | MySQL Server: Optimizer | Duplicate (118 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | The opposite HAVING clause intersects and is always an empty set. |
| 118198 | 2025-05-14 14:16 | 2025-05-19 22:49 | MySQL Server: Optimizer | Verified (118 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | Different intersection orders lead to more than 20,000 times performance gap |
| 118265 | 2025-05-25 23:12 | 2025-07-09 15:42 | MySQL Server: InnoDB storage engine | Verified (89 days) | S1 | 9.3.0 | MacOS (15.4.1 (24E263)) | x86 (Quad-Core Intel Core i7) | mysqld hangs durning startup |
| 118591 | 2025-07-07 11:28 | 2025-07-10 7:11 | MySQL Server: Data Types | Duplicate (66 days) | S1 | 9.3.0 | Any | Any | empty string parse to 0 in SET statement, which is different from that in the SELECT query |
| 118592 | 2025-07-07 12:12 | 2025-07-10 6:53 | MySQL Server: Prepared statements | Duplicate (66 days) | S1 | 9.3.0 | Any | Any | Unexpected result of prepared statement |
| 118595 | 2025-07-07 15:16 | 2025-07-10 7:19 | MySQL Server: Prepared statements | Not a Bug (66 days) | S1 | 9.3.0 | Any | Any | NULL are transformed to false in certain expression in prepared statement |
| 118014 | 2025-04-19 16:53 | 2025-04-20 13:53 | MySQL Server: Optimizer | Verified (147 days) | S2 | 9.3.0,8.0, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Wrong Left Join Result |
| 118982 | 2025-09-10 6:55 | 2025-09-11 12:57 | MySQL Server: Optimizer | Analyzing (3 days) | S1 | 9.4.0 | Linux | Any | Unexpected result of IN operator |
| 118808 | 2025-08-10 11:26 | 2025-08-11 7:00 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.4.0, 8.4.3, 8.4.6 | Any | Any | Different result with range scan and table scan in sql with subquery |
| 116247 | 2024-09-27 6:31 | 2024-09-28 18:10 | MySQL Server: Group Replication | Verified (352 days) | S1 | all versions | Any | Any | In the multi-primary architecture, a rule violation for SMR occurs |
| 117878 | 2025-04-03 17:41 | 2025-04-04 12:01 | MySQL Server: Row Based Replication ( RBR ) | Unsupported (163 days) | S1 | MySQL 8.0.28 | Linux | Any | Update Ignore and Replace Into Statements fails to replicate on Replica in MySQL 8.0.28 |
| 118359 | 2025-06-04 13:43 | 2025-06-16 12:33 | MySQL Server: InnoDB storage engine | Verified (95 days) | S2 | mysql-8.0.41 | Any | Any | False-negative result in row_vers_impl_x_locked_low() — may miss identifying the active transaction on a secondary rec |
| 118980 | 2025-09-10 2:52 | 2025-09-11 13:04 | MySQL Server: Optimizer | Verified (3 days) | S2 | MySQL8.0.41 | Any | Any | queries have different results using and without index |
| 116400 | 2024-10-18 4:06 | 2024-10-18 5:56 | MySQL Server: Optimizer | Verified (331 days) | S2 | trunk (9.1.0), 8.0.30, 8.4.3, 8.4.0 | Any | Any | Contribution by Tencent: crash on explain format=tree for conn with subquery |
| Showing all 241 (Edit, Save, CSV, Feed) |
