| Showing all 321 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119808 | 2026-01-29 14:44 | 2026-04-20 11:52 | MySQL Server: DML | Open (41 days) | S2 | Any | Any | Error 3569 with HIGH_PRIORITY + VIEW + GROUP BY + FOR UPDATE | |
| 119820 | 2026-01-31 11:14 | 2026-01-31 12:37 | MySQL Server: DML | Not a Bug (120 days) | S2 | Any | Any | Update Temporary table: Can't reopen table | |
| 119993 | 2026-03-06 7:57 | 2026-03-09 8:14 | MySQL Server: Optimizer | Duplicate (83 days) | S2 | Linux | x86 | Incorrect result with LEFT/RIGHT JOIN when using functional index and boolean expression comparison | |
| 119994 | 2026-03-06 8:20 | 2026-03-09 8:17 | MySQL Server: Optimizer | Duplicate (83 days) | S2 | Linux | x86 | Incorrect result with LEFT/RIGHT JOIN using functional index and boolean expression comparison | |
| 120297 | 2026-04-20 8:44 | 2026-04-20 10:04 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.32 | Any | Any | query_term.cc:320 assert(false) crash — UNION query triggers unhandled AccessPath |
| 119145 | 2025-10-13 12:53 | 2026-01-21 11:10 | MySQL Server: Optimizer | Duplicate (130 days) | S2 | 8.4.6 | Any (windows ) | Any (x64) | INNER JOIN and INTERSECT of LEFT/RIGHT JOINs return different results with complex boolean conditions |
| 118916 | 2025-08-31 18:26 | 2025-09-05 8:21 | MySQL Server: Optimizer | Duplicate (268 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 | 2026-04-03 10:48 | MySQL Server: Optimizer | Duplicate (58 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 (264 days) | S2 | 9.4.0 | Any | Any | LEFT JOIN with constant functions returns incorrect results when condition is ON FALSE |
| 119068 | 2025-09-25 8:43 | 2025-10-01 14:05 | MySQL Server: Optimizer | Verified (244 days) | S2 | 9.4.0 | Linux | x86 | RIGHT JOIN on VIEW with IN subquery returns incorrect non-NULL value instead of NULL |
| 119074 | 2025-09-26 4:46 | 2026-04-02 6:15 | MySQL Server: Optimizer | Duplicate (59 days) | S2 | 9.4.0 | Linux | x86 | Incorrect result with derived_condition_pushdown optimization in correlated subquery with LEFT JOIN ON FALSE |
| 119100 | 2025-10-01 1:00 | 2026-04-02 6:17 | MySQL Server: Optimizer | Duplicate (59 days) | S2 | 9.4.0 | Linux | x86 | WHERE alias IS NULL Fails for Derived Column Using subquery |
| 120353 | 2026-04-27 11:55 | 2026-04-29 11:43 | MySQL Server: InnoDB storage engine | Can't repeat (32 days) | S2 | <=8.0.42-debug | Any | Any | InnoDB crashes with assertion failure (ut_dbg_assertion_failed) when creating index with ALGORITHM COPY on table with F |
| 119445 | 2025-11-23 4:32 | 2025-11-23 4:32 | MySQL Server: InnoDB storage engine | Open | S2 | 5.7 | Ubuntu | Any | ALTER TABLE ... AUTO_INCREMENT allows values outside column datatype range → later INSERT fails |
| 119457 | 2025-11-25 9:00 | 2025-11-27 12:42 | MySQL Server: InnoDB storage engine | Open (185 days) | S2 | 5.7 | Any | Any | import tablespace cost too long |
| 119651 | 2026-01-09 2:19 | 2026-01-09 7:39 | MySQL Server: Memory storage engine | Unsupported (142 days) | S2 | 5.7 | Any | Any | A core dump occurred during heap scan. |
| 118669 | 2025-07-16 5:22 | 2025-07-16 6:46 | MySQL Server: Optimizer | Verified (319 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 (272 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 |
| 118367 | 2025-06-05 9:18 | 2025-06-06 10:06 | MySQL Server: Data Dictionary | Verified (359 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 | 2026-01-19 21:40 | MySQL Server: InnoDB storage engine | Closed (132 days) | S2 | 8.0 | Any | Any | when call que_eval_sql, may crash. |
| 119136 | 2025-10-13 3:14 | 2026-04-22 21:05 | MySQL Server: Optimizer | Closed (39 days) | S2 | 8.0 | Any | Any | Incompatible behavior between integer columns when comparing with datetime |
| 119432 | 2025-11-20 8:47 | 2025-12-07 21:44 | MySQL Server: Data Types | Verified (175 days) | S1 | 8.0 | Any | Any | Inconsistent time conversion behaviors between text and integer |
| 119453 | 2025-11-24 14:12 | 2025-12-07 22:36 | MySQL Server: Optimizer | Verified (175 days) | S2 | 8.0 | Any | Any | DEFAULT(column) returns wrong result when column is to the right of left join |
| 119528 | 2025-12-09 9:49 | 2025-12-10 12:38 | MySQL Server: Optimizer | Verified (172 days) | S2 | 8.0 | Any | Any | hash join result incorrect |
| 119602 | 2025-12-28 21:11 | 2025-12-29 10:39 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0 | Any | Any | Inconsistent data |
| 119603 | 2025-12-29 1:19 | 2026-01-04 20:40 | MySQL Server: Optimizer | Verified (147 days) | S2 | 8.0 | Any | Any | TRUE >= ALL(...) returns incorrect result (1) when comparing against a NOT NULL column |
| 119619 | 2026-01-04 14:07 | 2026-01-04 21:17 | MySQL Server: Optimizer | Verified (147 days) | S1 | 8.0 | Any | Any | Incorrect results for REPLACE function |
| 119628 | 2026-01-05 22:20 | 2026-05-06 15:44 | MySQL Server: InnoDB storage engine | Open (25 days) | S1 | 8.0 | Any | Any | Undo Truncation Bug, not fixed in 8.0, leads to Data Corruption. |
| 119957 | 2026-02-28 7:28 | 2026-02-28 7:28 | MySQL Server: Replication | Open | S2 | 8.0 | Any | Any | Contribution by Tencent: Replica Crash Due to Stale fts_doc_id in HASH_SCAN Replication Path |
| 118682 | 2025-07-18 3:52 | 2025-10-10 7:41 | MySQL Server: Optimizer | Verified (311 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 | 2026-05-28 1:13 | MySQL Server: DDL | Patch pending (347 days) | S2 | 8.0, 8.4 | Red Hat | x86 | Unable to create partition with name '1e3fRQM2GhI' |
| 119541 | 2025-12-11 12:32 | 2025-12-12 8:19 | MySQL Server: Optimizer | Verified (170 days) | S2 | 8.0, 8.4, 9.5 | Any | Any | Performance regression due to record buffer in index range scan |
| 119944 | 2026-02-25 22:14 | 2026-02-26 13:13 | MySQL Server: Optimizer | Verified (94 days) | S1 | 8.0, 8.4, 9.X | Any | Any | Feature Request: Extend TIMESTAMP range beyond 2038-01-19 by switching to 64-bit signed storage (Year 2038 Problem) |
| 119204 | 2025-10-22 8:10 | 2025-10-23 10:04 | MySQL Server: DML | Verified (220 days) | S2 | 8.0,9.5 | Any | Any | The change of join order may lead to inconsistent update data |
| 118322 | 2025-06-01 4:47 | 2025-12-07 20:45 | MySQL Server: Replication | No Feedback (316 days) | S2 | 8.0.20 | Any | x86 | Result of `show master status` is not correct !!! |
| 120105 | 2026-03-19 7:42 | 2026-04-17 17:11 | MySQL Server: InnoDB storage engine | Can't repeat (51 days) | S2 | 8.0.22 | Any | Any | mysql crash on fil_report_invalid_page_access_low |
| 119186 | 2025-10-18 2:55 | 2025-10-18 9:06 | MySQL Server: Clone Plugin | Can't repeat (225 days) | S1 | 8.0.25 | Any | Any | after clone over,mysql crash. |
| 119041 | 2025-09-19 8:19 | 2025-09-23 9:57 | MySQL Server: Optimizer | Verified (250 days) | S2 | 8.0.25 8.0.40 | Any | Any | statistics automatic update cause poor execution plan |
| 119612 | 2025-12-31 2:10 | 2025-12-31 5:02 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.25 8.0.40 | Any | Any | dict_stats_analyze_index() may always discard optimal index-based access paths |
| 120208 | 2026-04-03 7:57 | 2026-05-04 1:00 | MySQL Server: DML | No Feedback (28 days) | S1 | 8.0.28 | Any (Aurora MySQL 3.04.4) | Any | SIGSEGV crash in TABLE_LIST::query_block_id_for_explain() when running EXPLAIN on CTE (WITH clause) query |
| 118805 | 2025-08-09 12:04 | 2026-01-15 17:12 | MySQL Server: Pluggable Authentication | Closed (136 days) | S2 | 8.0.30, 8.0.43, 8.4.6 | Windows (11 Pro) | x86 (64 bit) | mysqld fails to start |
| 119567 | 2025-12-17 2:53 | 2025-12-18 2:10 | MySQL Server: InnoDB storage engine | Open (164 days) | S2 | 8.0.30/9.4.0/8.4.6 | Any | Any | signal 6 crashed when too many connections |
| 120004 | 2026-03-07 19:38 | 2026-03-09 9:48 | MySQL Server: Optimizer | Verified (83 days) | S2 | 8.0.31 | Any | Any | IndexSkipScanIterator Assertion Failure |
| 120185 | 2026-03-31 8:58 | 2026-04-06 4:47 | MySQL Server: DML | Can't repeat (55 days) | S2 | 8.0.32-debug | Any | Any | Assertion Failure in add_key_fields with Nested CTE |
| 119458 | 2025-11-25 9:23 | 2025-11-25 9:31 | MySQL Server: Group Replication | Open (187 days) | S2 | 8.0.32, 8.4.4 | Any | Any | server cannot restart after crash when relay_log_recovery=1 and have both mgr and normal slave |
| 119630 | 2026-01-06 7:59 | 2026-01-21 18:56 | MySQL Server: Optimizer | Duplicate (130 days) | S2 | 8.0.33 | Any (22.04) | Any | Optimizer incorrectly merges derived table with type conversion and WHERE clause, causing wrong query results |
| 119631 | 2026-01-06 12:13 | 2026-01-21 12:16 | MySQL Server: Optimizer | Duplicate (130 days) | S2 | 8.0.33 | Any (22.04) | Any | CTE with type conversion and WHERE condition in IN/EXISTS subquery returns all rows instead of filtered rows |
| 119646 | 2026-01-08 7:46 | 2026-01-21 20:24 | MySQL Server: Optimizer | Duplicate (130 days) | S2 | 8.0.33 | Ubuntu (22.04) | Any | View + Type Conversion + IN Subquery Returns Wrong Result |
| 119436 | 2025-11-20 15:36 | 2025-11-27 7:03 | MySQL Server: Security: Privileges | Open | S2 | 8.0.35 | Ubuntu (EC2 instance) | x86 | User Privileges are Missed On Replica Server |
| 119441 | 2025-11-21 20:09 | 2025-11-21 20:09 | MySQL Server: Group Replication | Open | S2 | 8.0.35 | Linux (Rocky Linux release 8.10) | x86 | Group replication binds to ipv6 wildcard address |
| 119796 | 2026-01-27 19:12 | 2026-01-29 4:32 | MySQL Server: DDL | Can't repeat (122 days) | S2 | 8.0.35 | Any | Any | Encrypted data changes when adding columns |
| 120437 | 2026-05-11 8:47 | 2026-05-11 8:57 | MySQL Server: Information schema | Open (20 days) | S2 | 8.0.35, 8.4.8, 9.3.0, 9.7.0 | Any | Any | information_schema.partitions returns UINT64_MAX (18446744073709551615) for DATA_LENGTH of partition dropped during conc |
| 118710 | 2025-07-23 12:08 | 2025-07-23 12:42 | MySQL Server: Optimizer | Verified (312 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 |
| 118411 | 2025-06-10 15:52 | 2025-07-21 11:44 | MySQL Server: InnoDB storage engine | Verified (314 days) | S2 | 8.0.37, 8.0.42 | CentOS | x86 | Performance degradation in write workload after rebuilding table with row_format=compressed |
| 118510 | 2025-06-23 20:09 | 2025-07-01 12:50 | MySQL Server: FULLTEXT search | Verified (334 days) | S2 | 8.0.39 | Any | Any | InnoDB Match Against does not work properly with utf8mb4_0900_as_ci |
| 119648 | 2026-01-08 11:37 | 2026-01-09 6:09 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.39 | Any | Any | Non-repeatable Reads in REPEATABLE READ Isolation Level |
| 120170 | 2026-03-28 8:33 | 2026-03-28 8:33 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.39 | Any | Any | Missing Update in READ COMMITTED during concurrent UPDATE with row re-evaluation failure. |
| 118700 | 2025-07-22 12:55 | 2025-12-07 20:45 | MySQL Server: Replication | No Feedback (280 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 (296 days) | S1 | 8.0.40 | Ubuntu | Any | Replication Break in 8.0.40 salve when from 8.0.33 Master |
| 119396 | 2025-11-14 10:58 | 2025-11-14 15:12 | MySQL Server: InnoDB storage engine | Open (198 days) | S1 | 8.0.40 | Any | Any | Increase in undo log size , slower purging and no truncation even after restart |
| 119578 | 2025-12-19 14:06 | 2025-12-19 14:11 | MySQL Server: InnoDB storage engine | Open | S1 | 8.0.40 | Any | x86 | Repeated MySQL Crashes During Online ALTER on Multi -TB Tables |
| 118536 | 2025-06-26 17:55 | 2025-09-21 20:45 | MySQL Server: Optimizer | Analyzing (338 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 |
| 118422 | 2025-06-12 2:54 | 2025-06-12 23:46 | MySQL Server: InnoDB storage engine | Can't repeat (353 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 (285 days) | S2 | 8.0.41 | Any | Any | AHI results the mysqld hung and assertion failure: btr0sea.cc:295:sleep_counter < 60000 |
| 119049 | 2025-09-22 7:23 | 2025-09-22 7:53 | MySQL Server: Optimizer | Closed (251 days) | S2 | 8.0.41 | Linux (5.10.134-19.al8.x86_64) | x86 (x86_64) | Performance regression in 8.0.41 compared to 5.7.37 for queries using limit |
| 119156 | 2025-10-15 2:01 | 2026-01-13 11:13 | MySQL Server: Optimizer | Verified (138 days) | S2 | 8.0.41 | CentOS | x86 | Query returns incorrect result (12 vs 2) when using FORCE INDEX compared to optimizer's automatic index selection, when |
| 119241 | 2025-10-27 11:25 | 2025-10-27 11:29 | MySQL Server: DDL | Open (216 days) | S2 | 8.0.41 | Any | Any | Exception when creating index instance |
| 119467 | 2025-11-27 6:05 | 2025-11-27 6:05 | MySQL Server: DDL | Open | S2 | 8.0.41 | Any | Any | Creating the index directly works, but the operation fails when wrapped in an IF() function, |
| 119474 | 2025-11-29 9:29 | 2025-12-01 4:16 | MySQL Server: Optimizer | Verified (181 days) | S2 | 8.0.41 | Any | Any | Result error caused by the subquery_to_derived optimizer switch |
| 119492 | 2025-12-02 11:57 | 2025-12-03 3:38 | MySQL Server: Optimizer | Closed (179 days) | S2 | 8.0.41 | Any | Any | Inconsistent data types of the IN condition in JOIN queries leads to incorrect query results. |
| 119526 | 2025-12-09 3:13 | 2026-01-11 1:00 | MySQL Server: Optimizer | No Feedback (141 days) | S2 | 8.0.41 | Any | Any | Inconsistent query results caused by the NO_MERGE hint |
| 119601 | 2025-12-28 11:55 | 2026-02-08 13:32 | MySQL Server: Optimizer | Verified (112 days) | S2 | 8.0.41 | CentOS | Any (x86) | Crash for show processlist when use cursor |
| 120019 | 2026-03-10 12:29 | 2026-03-10 14:40 | MySQL Server: Optimizer | Verified (82 days) | S2 | 8.0.41 | Any | Any | query result change after removing partitioning |
| 120574 | 2026-05-29 14:05 | 2026-05-29 14:12 | MySQL Server: Optimizer | Open | S2 | 8.0.41 | Any | Any | Range optimizer exceeds memory limit and chooses bad range plan for large IN lists |
| 118818 | 2025-08-13 3:44 | 2025-10-19 17:14 | MySQL Server: InnoDB storage engine | Closed (224 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 |
| 118913 | 2025-08-29 3:40 | 2025-09-01 10:19 | MySQL Server: Optimizer | Verified (272 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 (272 days) | S2 | 8.0.41+ | Any | Any | Incorrect results could be returned when using index condition pushdown and Range checked for each record |
| 120575 | 2026-05-30 6:57 | 2026-05-30 6:57 | MySQL Server: Optimizer | Open | S2 | 8.0.41+ | Any | Any | Range optimizer chooses bad range plan for large IN lists and execution is very slow and memory usage spikes. |
| 120281 | 2026-04-17 9:21 | 2026-04-17 11:32 | MySQL Server: Replication | Open (44 days) | S2 | 8.0.42 | Linux (any) | Any | replica_preserve_commit_order causes infinite deadlock in group commit pipeline, blocking all application writes |
| 118594 | 2025-07-07 14:16 | 2025-07-07 14:58 | MySQL Server: InnoDB storage engine | Verified (328 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 (285 days) | S2 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.24.04.1) | x86 | SQL Thread cannot be stopped when last error was 1755 |
| 119133 | 2025-10-11 6:55 | 2025-10-11 6:56 | MySQL Server: InnoDB storage engine | Open (232 days) | S2 | 8.0.42 | Any | Any | Under the RC isolation level, updating data after a SELECT FOR UPDATE may lead to data read inconsistency. |
| 119606 | 2025-12-29 14:23 | 2026-01-21 20:58 | MySQL Server: Optimizer | Duplicate (135 days) | S2 | 8.0.42 | Linux (Linux (x86_64)) | Any | Assertion failure in item_func.cc:3937: !unsigned_flag || !arg_val.is_negative() during JOIN optimization |
| 119639 | 2026-01-07 9:05 | 2026-01-21 21:05 | MySQL Server: Optimizer | Duplicate (130 days) | S2 | 8.0.42 | Any | Any | Assertion Failure in LEAST() Function with Unsigned Columns |
| 119759 | 2026-01-22 18:55 | 2026-05-12 20:31 | MySQL Server: InnoDB storage engine | Open (129 days) | S2 | 8.0.42 | Any | Any | InnoDB allow reads on non-durable data, which can be lost after crash(visibility before durability window) |
| 118356 | 2025-06-04 11:58 | 2025-07-13 10:29 | MySQL Server: Replication | Verified (354 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 (331 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | Startup without Signs of Progress when Rolling-Back Big Transaction. |
| 118512 | 2025-06-24 7:52 | 2026-04-27 11:19 | MySQL Server: Optimizer | Closed (244 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | The missing semi join condition causes incorrect result |
| 119802 | 2026-01-28 13:49 | 2026-01-28 15:52 | MySQL Server: Optimizer | Verified (123 days) | S2 | 8.0.42+ | Any | Any | Assertion 'is_nullable()' failed in Item_typecast_signed::val_int() |
| 119877 | 2026-02-10 12:42 | 2026-02-11 9:52 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.42+ | Any | Any | InnoDB Buffer Pool Flush State Mutex Contention (8.0.42-debug) |
| 119256 | 2025-10-28 7:12 | 2025-10-28 7:12 | MySQL Server: Replication | Open | S2 | 8.0.43 | Any | Any | Replication with additional column on source can cause data loss and should not be allowed |
| 119554 | 2025-12-15 16:22 | 2026-05-06 4:57 | MySQL Server: InnoDB storage engine | Duplicate (25 days) | S2 | 8.0.43 | CentOS ( 7.9.2009 (Core)) | Any | CRASH SERVER after Truncate |
| 119621 | 2026-01-05 11:11 | 2026-02-24 12:06 | MySQL Server: JSON | Verified (96 days) | S2 | 8.0.43 / 8.4.7 | Any | Any | query on partitioned table report "the JSON binary value contains invalid data" |
| 120471 | 2026-05-14 0:08 | 2026-05-18 9:15 | MySQL Server: Replication | Open (17 days) | S1 | 8.0.43, 8.0.46, 8.4.9, 9.7.0 | Any (reproduced on macOS and Linux) | Any | binary log violates read after write (commit) consistency |
| 119381 | 2025-11-13 8:14 | 2026-01-13 19:17 | MySQL Server: DML | Verified (138 days) | S2 | 8.0.43, 9.4.0 | Any | Any | Contribution by Tencent: Duplicate auto-increment values happened with partitioned tables and uk conflict |
| 118888 | 2025-08-25 7:19 | 2025-09-16 11:29 | MySQL Server: DDL | Verified (257 days) | S2 | 8.0.43/8.4.6 | Any | Any | DDL operation fills the entire disk space and eventually fails |
| 119236 | 2025-10-27 4:15 | 2026-04-23 13:11 | MySQL Server: Prepared statements | Closed (38 days) | S2 | 8.0.44 | Any | Any | The SQL reprepare bug results in 100% CPU load. |
| 119451 | 2025-11-24 9:50 | 2026-01-21 3:17 | MySQL Server: Locking | Open (130 days) | S2 | 8.0.44 | Any | Any | The schema's MDL lock is held for too long after opening the table |
| 119460 | 2025-11-25 10:08 | 2026-01-21 3:17 | MySQL Server: InnoDB storage engine | Open (130 days) | S2 | 8.0.44 | Any | Any | InnoDB transaction may get stuck in an infinite loop when releasing Read Locks |
| 119570 | 2025-12-17 10:08 | 2025-12-18 6:06 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.44 | Ubuntu (24.04) | x86 (running under Virtual Box 7.2.2, Win11 host) | Reports of "database page corruption", and server restart |
| 119582 | 2025-12-22 6:49 | 2025-12-22 19:27 | MySQL Server: Optimizer | Verified (160 days) | S2 | 8.0.44 | Any | Any | Inconsistency functional dependency in ONLY_FULL_GROUP_BY mode between derived tables and physical tables |
| 119588 | 2025-12-24 3:03 | 2025-12-26 17:23 | MySQL Server: Optimizer | Verified (156 days) | S1 | 8.0.44 | Any | Any | Incorrect result in JOIN with IN subquery |
| 119591 | 2025-12-24 7:27 | 2025-12-26 17:48 | MySQL Server: Data Types | Verified (156 days) | S1 | 8.0.44 | Any | Any | Incorrect result type for NULLIF(DOUBLE,BIGINT) function |
| 119597 | 2025-12-26 2:37 | 2025-12-26 17:57 | MySQL Server: Optimizer | Verified (156 days) | S1 | 8.0.44 | Any | Any | WHERE ... IN ... incorrectly returns rows |
| 119661 | 2026-01-12 13:19 | 2026-01-12 13:19 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.44 | Any | Any | Drop multiple FTS will cause permanent leakage of its AUX tables |
| 119669 | 2026-01-13 13:27 | 2026-01-13 14:53 | MySQL Server: Optimizer | Verified (138 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal query and prepared statement |
| 119670 | 2026-01-13 13:46 | 2026-01-13 14:51 | MySQL Server: Optimizer | Verified (138 days) | S1 | 8.0.44 | Any | Any | Incorrect result caused by index |
| 119676 | 2026-01-14 6:26 | 2026-01-14 13:11 | MySQL Server: Replication | Open | S2 | 8.0.44 | Any | Any | Column statistic (histograms) is not replicated in read_only replica mode |
| 119683 | 2026-01-14 15:35 | 2026-01-15 12:57 | MySQL Server: Optimizer | Verified (136 days) | S1 | 8.0.44 | Linux | x86 | Different results for INNER JOIN and STRAIGHT_JOIN with GREATEST() IN predicate |
| 119686 | 2026-01-15 8:37 | 2026-01-15 13:11 | MySQL Server: Optimizer | Verified (136 days) | S2 | 8.0.44 | Linux | x86 | Incorrect result when joined table has PRIMARY KEY and WHERE predicate involves CASE |
| 119687 | 2026-01-15 10:23 | 2026-01-15 13:18 | MySQL Server: Optimizer | Verified (136 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal and prepared INSERT |
| 119692 | 2026-01-16 5:23 | 2026-01-16 8:09 | MySQL Server: Optimizer | Verified (135 days) | S1 | 8.0.44 | Any | Any | The normal query generated a non-optimal query plan. |
| 119708 | 2026-01-16 14:58 | 2026-02-08 12:32 | MySQL Server: Optimizer | Verified (112 days) | S2 | 8.0.44 | Linux | Any | INNER JOIN and STRAIGHT_JOIN produce different results with FLOAT UNIQUE column on MEMORY table |
| 119716 | 2026-01-19 1:36 | 2026-01-19 9:16 | MySQL Server: Optimizer | Verified (132 days) | S1 | 8.0.44 | Any | Any | Suboptimal query plan generated by normal query compare to prepared statement |
| 119741 | 2026-01-22 7:00 | 2026-01-22 8:35 | MySQL Server: Optimizer | Verified (129 days) | S1 | 8.0.44 | Any | Any | internal_tmp_mem_storage_engine = MEMORY setting makes the DISTINCTROW returns incorrect result on 0 and -0 |
| 119766 | 2026-01-23 19:18 | 2026-01-23 19:18 | MySQL Server: Performance Schema | Open | S2 | 8.0.44 | Any | Any | Rows unexpectedly added in performance_schema for failed connections |
| 119790 | 2026-01-27 10:14 | 2026-01-27 12:07 | MySQL Server: Optimizer | Verified (124 days) | S1 | 8.0.44 | Any | Any | Unexpected result of expression IN NULL |
| 120011 | 2026-03-09 10:29 | 2026-03-09 11:16 | MySQL Server: Optimizer | Verified (83 days) | S1 | 8.0.44 | Any | Any | The normal query generated a non-optimal query plan with index. |
| 120581 | 2026-05-31 9:02 | 2026-05-31 9:02 | MySQL Server: Optimizer | Open | S2 | 8.0.44 | MacOS | Any | unique index causes incorrect result for IN comparison with implicit type conversion |
| 120304 | 2026-04-20 22:05 | 2026-05-06 4:55 | MySQL Server: InnoDB storage engine | Duplicate (25 days) | S1 | 8.0.44 | CentOS (07) | x86 (x86_64) | MySQL 8.0.44 crashes with InnoDB assertion failure on replica when TRUNCATE TABLE is applied to a table whose tablespace |
| 120278 | 2026-04-17 2:44 | 2026-05-12 2:31 | MySQL Server: Replication | Open (19 days) | S2 | 8.0.44 8.4.9 | Any | Any | mts_event_coord_cmp() uses strcmp() for binlog filename comparison, causing incorrect ordering when binlog index exceeds |
| 119706 | 2026-01-16 10:46 | 2026-03-17 8:21 | MySQL Server: Optimizer | Open (75 days) | S2 | 8.0.44, 9.5.0 | Any | Any | Incorrect Results from ALL/ANY Subquery MIN/MAX Optimization with Type Mismatch |
| 119470 | 2025-11-27 14:30 | 2025-11-28 13:06 | MySQL Server: Optimizer | Verified (184 days) | S1 | 8.0.44+ | Any | Any | sql injection |
| 119487 | 2025-12-01 14:45 | 2026-02-05 19:41 | MySQL Server: Optimizer | Verified (115 days) | S2 | 8.0.45 | Ubuntu (22.04) | Any | JOIN, STRAIGHT_JOON Return Different Results |
| 119772 | 2026-01-25 11:30 | 2026-01-26 13:23 | MySQL Server: DML | Duplicate (126 days) | S2 | 8.0.45 | CentOS | Any | [8.0.45-debug] Lost connection to MySQL server during query |
| 119805 | 2026-01-29 3:21 | 2026-01-29 4:15 | MySQL Server: DML | Verified (122 days) | S2 | 8.0.45 | Any | Any | create_tmp_field assert fail |
| 119821 | 2026-01-31 16:25 | 2026-02-01 12:58 | MySQL Server: DML | Not a Bug (119 days) | S2 | 8.0.45 | Any | Any | MySQL and TiDB return different results |
| 119822 | 2026-01-31 17:35 | 2026-01-31 22:04 | MySQL Server: Optimizer | Verified (120 days) | S2 | 8.0.45 | Any | Any | MySQL and TiDB return different results |
| 119912 | 2026-02-15 4:33 | 2026-02-15 12:09 | MySQL Server: Optimizer | Verified (105 days) | S2 | 8.0.45 | Linux | Any | JOIN query returns different results depending on index visibility |
| 119927 | 2026-02-20 10:28 | 2026-02-25 8:56 | MySQL Server: Optimizer | Verified (95 days) | S2 | 8.0.45 | Linux | Any | Inconsistent results between direct query and derived table with BIGINT column and FLOAT predicate (IN clause) |
| 119947 | 2026-02-26 9:19 | 2026-02-26 9:30 | MySQL Server: Replication | Open | S2 | 8.0.45 | Any | Any | ordered_commit some transactions had flush errors, but committed successfully.resulting in master-slave inconsistency |
| 119958 | 2026-02-28 13:09 | 2026-03-02 13:02 | MySQL Server: Optimizer | Verified (90 days) | S1 | 8.0.45 | Any | Any | EXISTS subquery result behaves inconsistently based on source table |
| 119972 | 2026-03-02 19:47 | 2026-03-03 9:47 | MySQL Server: Optimizer | Verified (89 days) | S1 | 8.0.45 | Any | Any | Incorrect Result from IN Subquery with UNIQUE Index |
| 119973 | 2026-03-02 21:01 | 2026-03-03 8:45 | MySQL Server: Optimizer | Verified (89 days) | S1 | 8.0.45 | Any | Any | Inconsistent results depending on whether the column has a PRIMARY KEY index |
| 119991 | 2026-03-06 5:56 | 2026-03-06 11:27 | MySQL Server: Optimizer | Verified (86 days) | S2 | 8.0.45 | Linux | x86 | Incorrect result with LEFT/RIGHT JOIN when comparing boolean expression with = 0 in presence of functional index |
| 119992 | 2026-03-06 6:23 | 2026-03-09 8:07 | MySQL Server: Optimizer | Duplicate (83 days) | S2 | 8.0.45 | Linux | x86 | Incorrect result for LEFT/RIGHT JOIN when using IS TRUE / IS FALSE expressions on the right table with NULL padding. |
| 119995 | 2026-03-06 9:51 | 2026-04-27 10:07 | MySQL Server: Optimizer | Closed (34 days) | S2 | 8.0.45 | Any | Any | Function find_in_set return wrong result |
| 120010 | 2026-03-09 9:56 | 2026-04-03 10:55 | MySQL Server: Optimizer | Duplicate (59 days) | S1 | 8.0.45 | Any | Any | Incorrect result set when evaluating IS NULL on a derived table containing logical AND expressions |
| 120015 | 2026-03-09 13:48 | 2026-04-02 6:16 | MySQL Server: Optimizer | Duplicate (59 days) | S1 | 8.0.45 | Any | Any | Incorrect retention of NULL rows due to CASE evaluation error in WHERE clause. |
| 120051 | 2026-03-13 9:31 | 2026-03-13 21:16 | MySQL Server: Optimizer | Verified (79 days) | S1 | 8.0.45 | Linux (ubuntu 20.04) | Any | Wrong result for derived-table rewrite of GROUP BY ... HAVING query |
| 120075 | 2026-03-16 14:26 | 2026-03-25 12:47 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Linux (ubuntu 20.04) | x86 | Silent Data Truncation of DOUBLE (DBL_MAX) in Subqueries/Temporary Tables |
| 120083 | 2026-03-17 8:59 | 2026-03-17 11:38 | MySQL Server: Optimizer | Verified (75 days) | S2 | 8.0.45 | Linux | x86 | incorrect result when comparing floating constant in OUTER JOIN condition |
| 120087 | 2026-03-17 13:12 | 2026-03-18 4:58 | MySQL Server: Optimizer | Verified (74 days) | S2 | 8.0.45 | Linux | x86 | Incorrect result with RIGHT JOIN and IS NULL predicate on partitioned indexed table |
| 120094 | 2026-03-18 8:29 | 2026-03-18 9:35 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Any | Any | Query returns incorrect results due to incorrect handling of predicate logic |
| 120097 | 2026-03-18 9:34 | 2026-03-18 9:48 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Any | Any | Incorrect result set when use INTERSECT ALL |
| 120098 | 2026-03-18 9:58 | 2026-03-18 10:59 | MySQL Server: Optimizer | Verified (74 days) | S1 | 8.0.45 | Any | Any | Incorrect result when using EXISTS with INTERSECT ALL and correlated subquery |
| 120099 | 2026-03-18 12:08 | 2026-03-19 8:04 | MySQL Server: Optimizer | Verified (73 days) | S1 | 8.0.45 | Any | Any | Query returns wrong result when condition involves CAST(division AS CHAR) |
| 120106 | 2026-03-19 7:49 | 2026-03-19 8:33 | MySQL Server: Optimizer | Verified (73 days) | S1 | 8.0.45 | Any | Any | Optimizer incorrectly handles constant derived table in RIGHT JOIN |
| 120145 | 2026-03-25 6:05 | 2026-03-25 19:22 | MySQL Server: Optimizer | Verified (67 days) | S2 | 8.0.45 | Linux (ubuntu 20.04) | x86 | Incorrect empty result after relocating a HAVING predicate into a derived-table boolean column with WHERE ref1 |
| 120158 | 2026-03-26 6:04 | 2026-03-29 19:37 | MySQL Server: Optimizer | Verified (63 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Incorrect result (NULL included) in index lookup/MAX() on FLOAT ZEROFILL column when filtering by 0.0 |
| 120203 | 2026-04-02 2:35 | 2026-04-04 19:49 | MySQL Server: Optimizer | Verified (57 days) | S2 | 8.0.45 | Any | Any | MySQL returns an incorrect result for an indexed comparison between an `INT` column and a non-integer function value. |
| 120263 | 2026-04-14 5:30 | 2026-04-14 10:56 | MySQL Server: JSON | Verified (47 days) | S2 | 8.0.45 | Any | Any | Inconsistent results for query with JSON_CONTAINS and CAST(... AS SIGNED) |
| 120286 | 2026-04-19 5:14 | 2026-04-20 7:53 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Any | Any | `SUM(DISTINCT pk)` returns `NULL` with a window function when a secondary index is used for group-by scanning |
| 120270 | 2026-04-15 9:49 | 2026-04-16 21:20 | MySQL Server: Optimizer | Verified (45 days) | S1 | 8.0.45 | Any | Any | Incorrect result for INTERSECT ALL with semantically equivalent EXCEPT operands when right EXCEPT left operand is wrap |
| 120272 | 2026-04-15 11:21 | 2026-04-22 9:30 | MySQL Server: InnoDB storage engine | Verified (39 days) | S2 | 8.0.45 | Any | Any | ddl stuck in Waiting for clone PAGE_COPY state |
| 120273 | 2026-04-15 15:39 | 2026-04-16 22:33 | MySQL Server: Memory storage engine | Verified (45 days) | S2 | 8.0.45 | Ubuntu (22.04) | x86 | Incorrect COUNT result when "SET SESSION internal_tmp_mem_storage_engine = MEMORY" is used |
| 120555 | 2026-05-27 8:22 | 2026-05-27 11:39 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.0.45 | Ubuntu | Any | Equivalent VIEW and CTE queries return different row counts with EXISTS, BINARY ENUM comparison, and LEFT JOIN |
| 120533 | 2026-05-23 12:35 | 2026-05-26 8:30 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu | x86 | A LEFT JOIN over DECIMAL ZEROFILL UNIQUE wrongly loses an obvious match |
| 120531 | 2026-05-23 12:33 | 2026-05-26 7:24 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu | x86 | A NULL comparison inside an IN subquery becomes spuriously true in the original path |
| 120525 | 2026-05-22 9:41 | 2026-05-26 6:49 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Append-Only Growth Breaks Subset Monotonicity for Implicit VARCHAR-to-DECIMAL IN-Subquery Comparison |
| 120524 | 2026-05-22 9:40 | 2026-05-26 6:27 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized Correlated EXISTS Returns Positive COUNT(*) But No Rows for Implicit VARCHAR-to-YEAR Comparison |
| 120275 | 2026-04-16 7:10 | 2026-04-20 6:51 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | DATE Index Lookup Loses Existing JOIN Matches Even with Explicit CAST(MEDIUMTEXT AS DATE), Causing S1/S2 Divergence |
| 120283 | 2026-04-17 13:00 | 2026-04-20 7:22 | MySQL Server: Optimizer | Not a Bug (41 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | DATE Column Printed as NULL Still Satisfies `IS NOT NULL`,Allowing a Contradictory Predicate to Return Rows |
| 120285 | 2026-04-18 15:49 | 2026-04-18 15:54 | MySQL Server: Optimizer | Open (43 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized Semijoin + Outer ORDER BY Loses Rows for Correlated EXISTS,Causing Plan-Dependent Result Divergence |
| 120288 | 2026-04-19 14:29 | 2026-04-20 8:04 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Window function logic mismatch in indexed `NOT IN` |
| 120296 | 2026-04-20 7:50 | 2026-04-20 9:24 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized Correlated EXISTS Loses Implicit VARCHAR-to-YEAR Coercion,Causing Plan-Dependent Result Divergence |
| 120284 | 2026-04-18 15:46 | 2026-04-20 7:33 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Ubuntu (Ubuntu 20.04.4 LTS) | x86 (Intel(R) Xeon(R) Platinum 8358P @ 2.60GHz (64 Cores, 96MB L3 Cache)) | Materialized `IN (subquery)` Loses VARCHAR-to-YEAR Coercion,Causing Plan-Dependent Result Divergence |
| 120300 | 2026-04-20 9:02 | 2026-04-20 11:03 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.45 | Any (Observed on Linux via the `mysql:9.6` ) | Any | Window function logic mismatch across engines |
| 119825 | 2026-02-01 12:02 | 2026-02-02 3:51 | MySQL Server: Optimizer | Verified (118 days) | S2 | 8.0.45, 8.4.8, 9.6 | Any | Any | Inconsistent results between INNER JOIN and STRAIGHT_JOIN when comparing DOUBLE constant with INT UNIQUE column |
| 119938 | 2026-02-25 7:36 | 2026-03-04 3:50 | MySQL Server: Partitions | Verified (88 days) | S2 | 8.0.45, 8.4.8, 9.6.0 | Any | Any | select partition table with virtual column return wong result |
| 120456 | 2026-05-12 15:02 | 2026-05-17 23:00 | MySQL Server: Optimizer | Verified (14 days) | S2 | 8.0.46 | Linux | Any | Semijoin Nested Loop index lookup uses raw VARCHAR keys against a DOUBLE B-tree, causing mismatches when the string over |
| 120370 | 2026-04-28 16:33 | 2026-05-22 14:45 | MySQL Server: DDL | Open (9 days) | S2 | 8.0.46 | Any | Any | Regression (from 8.0.45) on Row size too large |
| 120491 | 2026-05-18 5:53 | 2026-05-18 12:22 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.46 | CentOS | Any | Semijoin returns wrong results for VARCHAR-to-DECIMAL comparison with non-canonical numeric strings |
| 120356 | 2026-04-27 14:52 | 2026-04-27 17:21 | MySQL Server: DDL | Duplicate (34 days) | S2 | 8.0.46 | Linux (Debian 12) | x86 | ERROR 1118 Row size too large (> 8126) on 8.0.46 |
| 120475 | 2026-05-14 9:09 | 2026-05-18 10:20 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.46 | Linux | Any | Index Merge Intersection incorrectly drops matching rows in SELECT with OR predicate, returning wrong result count |
| 120403 | 2026-05-05 13:47 | 2026-05-28 1:13 | MySQL Server: Optimizer | Documenting (25 days) | S2 | 8.0.46, 8.4.9, 9.7.0 | Any | Any | Regression in MySQL 8.0.46, 8.4.9 & 9.7.0: WHERE equality condition fails to match existing row |
| 118941 | 2025-09-05 8:19 | 2025-09-10 14:45 | MySQL Server: Optimizer | Verified (263 days) | S2 | 8.0.x, 8.4.x | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with -0.001 Excludes 0.00 Row |
| 119004 | 2025-09-12 16:07 | 2026-01-13 1:00 | MySQL Server: Group Replication | No Feedback (139 days) | S2 | 8.0+ | Any | Any | UNREACHABLE member is not expelled after the group_replication_member_expel_timeout delay |
| 118955 | 2025-09-08 9:35 | 2025-09-09 23:51 | MySQL Server: Connection Handling | Not a Bug (264 days) | S1 | 8.043 | MacOS (15.6) | x86 (15.6) | Qt应用程序无法通过ODBC驱动程序从MySQL检索数据，而插入和删除操作工作正常 |
| 118624 | 2025-07-10 2:47 | 2026-05-28 1:13 | MySQL Server: InnoDB storage engine | Patch pending (325 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) |
| 119140 | 2025-10-13 8:01 | 2026-01-06 14:56 | MySQL Server: Optimizer | Verified (145 days) | S1 | 8.4 | Any | Any | DISTINCT works inconsistently in normal SELECT and prepared statement for 0 and -0 |
| 119521 | 2025-12-08 3:23 | 2025-12-10 6:47 | MySQL Server: InnoDB storage engine | Open | S2 | 8.4 | Any | Any | False positive deadlock detected involving SELECT FOR SHARE / LOCK IN SHARE MODE |
| 119770 | 2026-01-24 19:09 | 2026-01-27 10:03 | MySQL Server: Optimizer | Duplicate (124 days) | S2 | 8.4 | Any | Any | MySQL 8.4 optimizer uses full table scan for IN (...) on prefix index, but works in 8.0 |
| 119800 | 2026-01-28 8:53 | 2026-01-28 11:54 | MySQL Server: Compiling | Open (123 days) | S1 | 8.4 | Any | Any | An error occurred in ssl.cmake reading version information from opensslv.h, causing HAVE_TLSv13 to fail to compile. |
| 120326 | 2026-04-22 19:32 | 2026-04-23 6:32 | MySQL Server: Data Dictionary | Verified (38 days) | S2 | 8.4 | Any | Any | Upgrade fails on partitioned tables due to stale THD error from stored procedure compilation |
| 119152 | 2025-10-14 12:01 | 2025-10-14 12:01 | MySQL Server: InnoDB storage engine | Open | S2 | 8.4, 8.0.22 | Any | Any | Anomalous transaction snapshot version behavior under the RR isolation level. |
| 118923 | 2025-09-02 7:49 | 2025-09-04 11:46 | MySQL Server: InnoDB storage engine | Verified (270 days) | S2 | 8.4, 8.0.22, 9.4.0 | Any | Any | Abnormal read phenomena are observed under MySQL's Read Committed isolation level |
| 118515 | 2025-06-24 9:08 | 2026-01-16 16:44 | MySQL Server: InnoDB storage engine | Closed (135 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-12-18 6:35 | MySQL Server: Replication | Verified (297 days) | S2 | 8.4, 8.4.6, 9.4.0 | Any | Any | Contribution by Tencent: previous gtids may loss xa commit/rollback gtids |
| 118842 | 2025-08-14 8:50 | 2025-09-22 3:27 | MySQL Server: InnoDB storage engine | Verified (251 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 | 2026-01-09 13:51 | MySQL Server: Compiling | Not a Bug (142 days) | S2 | 8.4.6 | MacOS | Any | mysql8 @8.4.6: ld: unknown option: -no_warn_duplicate_libraries |
| 119117 | 2025-10-09 4:15 | 2025-12-16 9:22 | MySQL Server: Optimizer | Duplicate (166 days) | S2 | 8.4.6 | Windows | Other (x64) | INNER JOIN returns results when join condition evaluates to false |
| 119121 | 2025-10-09 11:06 | 2025-12-16 9:26 | MySQL Server: Optimizer | Duplicate (166 days) | S2 | 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns fewer rows than expected when ON condition is true for multiple rows |
| 119127 | 2025-10-10 11:58 | 2025-12-17 8:20 | MySQL Server: Optimizer | Verified (165 days) | S2 | 8.4.6 | Any | Any | INNER JOIN and INTERSECT of LEFT/RIGHT JOINs return different results when unique index is present |
| 119144 | 2025-10-13 12:49 | 2026-01-06 12:48 | MySQL Server: Optimizer | Verified (145 days) | S2 | 8.4.6 | Windows | Any (x64) | INNER JOIN and STRAIGHT_JOIN return different results with identical ABS function conditions |
| 119154 | 2025-10-14 13:24 | 2026-01-13 10:22 | MySQL Server: Data Types | Verified (138 days) | S1 | 8.4.6 | Any | Any | Incorrect BIT_COUNT value for TEXT column |
| 119198 | 2025-10-20 19:44 | 2026-05-28 1:13 | MySQL Server: Optimizer | Documenting (221 days) | S2 | 8.4.6 | Any | Any | Optimizer with reverse index range scan gives incorrect query result |
| 119220 | 2025-10-23 14:55 | 2025-11-07 9:22 | MySQL Server: Optimizer | Verified (205 days) | S2 | 8.4.6 | Any | x86 | Subquery materialization in LEFT JOIN ON clause loses WHERE conditions |
| 119273 | 2025-10-30 14:14 | 2026-01-15 10:29 | MySQL Server: InnoDB storage engine | Open (213 days) | S2 | 8.4.6 | Red Hat (5.14.0-570.25.1.el9_6.x86_64) | x86 | disk-based Temptable gives "Table './tmp/#sql2730_2b2_4' doesn't exist" |
| 119433 | 2025-11-20 9:30 | 2025-12-07 21:58 | MySQL Server: Data Types | Verified (175 days) | S1 | 8.4.6 | Any | Any | Inconsistent date conversion behaviors between text and integer |
| 119553 | 2025-12-15 14:00 | 2025-12-15 14:00 | MySQL Server: Federated storage engine | Open | S2 | 8.4.6 | Linux | x86 | Mutex deadlock between THR_LOCK_servers and federated_mutex |
| 120274 | 2026-04-16 5:53 | 2026-05-12 6:59 | MySQL Server: Connection Handling | Open | S2 | 8.4.6 | Red Hat (Rocky Linux 8.8) | x86 (4.18.0-477.27.1.el8_8.x86_64) | Specific account authentication permanently fails with "Public Key Retrieval is not allowed" after FLUSH PRIVILEGES |
| 119471 | 2025-11-27 17:03 | 2026-05-06 17:03 | MySQL Server: Connection Handling | Open (25 days) | S2 | 8.4.7 | Ubuntu (25.10 questing) | x86 (64 bits) | "Bad handshake" during each connection to a replication source server |
| 119491 | 2025-12-02 8:21 | 2025-12-08 21:10 | MySQL Server: Optimizer | Verified (174 days) | S1 | 8.4.7 | Any | Any | Incorrect results for make_set operation against longtext column |
| 119530 | 2025-12-09 12:38 | 2025-12-11 9:31 | MySQL Server: Optimizer | Verified (171 days) | S1 | 8.4.7 | Any | Any | Incorrect results for NULLIF functions |
| 119586 | 2025-12-23 9:09 | 2025-12-26 16:50 | MySQL Server: Data Types | Verified (156 days) | S1 | 8.4.7 | Any | Any | Inconsistent results for date conversion |
| 120005 | 2026-03-08 0:14 | 2026-03-10 8:04 | MySQL Server: Optimizer | Verified (82 days) | S2 | 8.4.7 | Any | Any | Wrong results with subquery with semijoin=on and antijoin optimization |
| 119498 | 2025-12-03 9:07 | 2026-01-09 1:00 | MySQL Server: Optimizer | No Feedback (143 days) | S1 | 8.4.7-TLS | Any | Any | The different sorting results are caused by the range query. |
| 120255 | 2026-04-13 11:24 | 2026-04-13 13:04 | MySQL Server: Optimizer | Verified (48 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes grouped results when replacing a grouped CTE or derived input |
| 120256 | 2026-04-13 11:44 | 2026-04-13 12:48 | MySQL Server: Optimizer | Verified (48 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization turns zero datetime values into runtime timestamps in UNION ALL output |
| 120258 | 2026-04-14 2:07 | 2026-04-14 4:45 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes NULL aggregate outputs into numeric values after GROUP BY |
| 120259 | 2026-04-14 2:43 | 2026-04-14 4:49 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes byte-valued UNION results |
| 120260 | 2026-04-14 2:48 | 2026-04-14 4:42 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes byte-valued outputs after aggregate or window processing |
| 120261 | 2026-04-14 2:52 | 2026-04-14 4:32 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes a key scalar output |
| 120262 | 2026-04-14 2:54 | 2026-04-16 20:55 | MySQL Server: Optimizer | Not a Bug (45 days) | S2 | 8.4.8 | Any | Any | CREATE VIEW materialization changes INTERSECT result cardinality for an aggregate branch |
| 120543 | 2026-05-25 9:57 | 2026-05-27 5:37 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.4.8 | Any | Any | MySQL `MERGE` vs `TEMPTABLE` view evaluation changes `MAX(SET)` result |
| 119743 | 2026-01-22 9:16 | 2026-01-22 9:20 | MySQL Server: Packaging | Open (129 days) | S2 | 8.4.8,9.6.0 | Fedora (43) | x86 | Removing mysql-community-server causes issues |
| 120482 | 2026-05-15 10:46 | 2026-05-24 15:09 | MySQL Server: Data Dictionary | Open (12 days) | S2 | 8.4.9 | Linux (Red Hat Enterprise Linux 9.6 (Plow ) | x86 | Upgrade from 8.0.35 to 8.0.45 or 8.4.9 failed due [ERROR] [MY-013135] and [Warning] [MY-014078] |
| 120488 | 2026-05-17 11:04 | 2026-05-18 7:14 | MySQL Server: Group Replication | Open | S2 | 8.4.9 | Linux (rocky linux 9.7) | x86 (9.7) | MySQL 8.4 Group Replication memory pools not released to OS srv_worker_thread 44,772x total/current ratio; xcom_cache ho |
| 120323 | 2026-04-22 12:51 | 2026-05-22 13:34 | MySQL Server: DDL | Verified (38 days) | S1 | 8.4.9 | Debian (12) | x86 | Regression : "Row size too large (> 8126)" error with table using InnoDb DYNAMIC row format |
| 118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (283 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
| 119654 | 2026-01-09 10:01 | 2026-01-09 10:01 | MySQL Server: InnoDB storage engine | Open | S2 | 8.x | Linux | Any | assert fail at mach_write_to_2 with a value larger than 0xFFFF. |
| 118857 | 2025-08-20 8:39 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (284 days) | S2 | 9.2.0 | Linux | Any | Bug Summary: MySQL Returns Incorrect Results for Complex Query with Set Operations |
| 118858 | 2025-08-20 8:51 | 2025-09-23 4:03 | MySQL Server: Optimizer | Verified (250 days) | S2 | 9.2.0 | Linux | Any | Inconsistency between the results returned by MySQL and other vendors' database systems was found during differentiation |
| 118949 | 2025-09-05 13:57 | 2025-09-10 0:42 | MySQL Server: Optimizer | Verified (265 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 |
| 119032 | 2025-09-18 7:52 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (251 days) | S2 | 9.2.0 | Any | Any | Inconsistency with MySQL 8.0.36 in MySQL 9.2.0: Equivalent INTERSECT query does not match INNER JOIN result and returns |
| 118540 | 2025-06-27 7:27 | 2025-09-23 4:02 | MySQL Server: Optimizer | Verified (250 days) | S2 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent results between NATURAL JOIN and INNER JOIN simulated via LEFT JOIN, RIGHT JOIN, and EXCEPT ALL with NULL v |
| 118541 | 2025-06-27 8:31 | 2025-09-23 4:02 | MySQL Server: Optimizer | Verified (250 days) | S2 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent Results Between NATURAL JOIN and its Equivalent Form Using EXCEPT ALL with Implicit Type Casting |
| 118544 | 2025-06-27 14:18 | 2025-09-23 4:03 | MySQL Server: Optimizer | Verified (250 days) | S2 | 9.2.0 , 9.3.0 | Linux | Any | A potential join operator bug |
| 118684 | 2025-07-18 14:54 | 2025-07-21 6:07 | MySQL Server: Optimizer | Verified (314 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 (300 days) | S2 | 9.2.0, 8.0.42, 8.4.5, 9.3.0 | Linux | Any | Inconsistent data returns when using INTERESECT operator |
| 118548 | 2025-06-28 7:56 | 2025-09-23 6:56 | MySQL Server: Optimizer | Not a Bug (250 days) | S2 | 9.2.0, 9.3.0 | Linux | x86 | A potential bugs in Mysql Server |
| 119059 | 2025-09-23 3:44 | 2025-09-25 16:07 | MySQL Server: Optimizer | Verified (250 days) | S2 | 9.2.0, 9.4.0 | Any | Any | Inconsistent result behavior when using EXCEPT equivalent NATRUAL JOIN |
| 118591 | 2025-07-07 11:28 | 2025-07-10 7:11 | MySQL Server: Data Types | Duplicate (325 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 (325 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 (325 days) | S1 | 9.3.0 | Any | Any | NULL are transformed to false in certain expression in prepared statement |
| 119290 | 2025-11-02 15:06 | 2025-11-07 7:43 | MySQL Server: InnoDB storage engine | Open (205 days) | S2 | 9.3.0, 9.5.0 | Any | Any | SELECT statement is affected by concurrent transaction under Read Uncommitted |
| 118982 | 2025-09-10 6:55 | 2025-09-26 12:01 | MySQL Server: Optimizer | Not a Bug (247 days) | S1 | 9.4.0 | Linux | Any | Unexpected result of IN operator |
| 119022 | 2025-09-17 12:40 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (251 days) | S2 | 9.4.0 | Any | Any | column value change cased by Union ALL |
| 119048 | 2025-09-21 12:57 | 2025-09-23 1:27 | MySQL Server: Prepared statements | Verified (251 days) | S2 | 9.4.0 | Any | Any | inconsistent result of two equivalent query with operator ~ |
| 119058 | 2025-09-23 0:57 | 2025-09-25 16:08 | MySQL Server: Prepared statements | Verified (250 days) | S1 | 9.4.0 | Any | Any | `\` is inconsistent in prepared statement and normal query |
| 119110 | 2025-10-07 5:19 | 2026-04-02 9:45 | MySQL Server: Optimizer | Duplicate (59 days) | S2 | 9.4.0 | Linux | x86 | Incorrect NULL filtering in CTE with UNION ALL over view containing LEFT JOIN on FALSE |
| 119139 | 2025-10-13 7:30 | 2025-12-18 8:56 | MySQL Server: Optimizer | Verified (164 days) | S1 | 9.4.0 | Any | Any | Unexpected error `Incorrect DECIMAL value: '0' for column '' at row -1` |
| 119159 | 2025-10-15 9:23 | 2025-10-15 9:23 | MySQL Server: InnoDB storage engine | Open | S2 | 9.4.0 | Any | Any | Some data is not rolled back successfully |
| 119187 | 2025-10-18 4:41 | 2026-04-02 9:30 | MySQL Server: Optimizer | Duplicate (59 days) | S2 | 9.4.0 | Linux | x86 | CTE with correlated EXISTS subquery causes incorrect NULL handling in WHERE clause with IS NULL predicate |
| 119386 | 2025-11-13 11:44 | 2026-01-15 12:35 | MySQL Server: Optimizer | Verified (136 days) | S1 | 9.4.0 | Any | Any | unexpected error "Can't write; duplicate key in table '/tmp/#sql1_372_1'" |
| 119454 | 2025-11-24 16:04 | 2025-11-27 5:11 | MySQL Server: Optimizer | Verified (185 days) | S2 | 9.4.0 | Any | Any | Hash join has wrong result when the join equality involves FLOAT or DECIMAL column |
| 119667 | 2026-01-13 11:42 | 2026-01-26 14:07 | MySQL Server: InnoDB storage engine | Open (125 days) | S2 | 9.4.0 | Ubuntu (22.04) | x86 (x86_64) | Assertion failure ddl0buffer.cc:197 with innodb-ddl-threads=4 + O_DIRECT |
| 119769 | 2026-01-24 14:46 | 2026-03-09 10:48 | MySQL Server: InnoDB storage engine | Open (84 days) | S2 | 9.4.0 | Any | Any | The transaction reads the value inserted by the blocked statement |
| 120199 | 2026-04-01 8:00 | 2026-04-01 8:00 | MySQL Server: InnoDB storage engine | Open | S2 | 9.4.0 | Any | Any | Two transactions simultaneously acquire the same exclusive lock |
| 120204 | 2026-04-02 7:52 | 2026-04-02 7:52 | MySQL Server: InnoDB storage engine | Open | S2 | 9.4.0 | Any | Any | UPDATE statements fail to update rows or acquire locks after being released |
| 118808 | 2025-08-10 11:26 | 2025-08-11 7:00 | MySQL Server: Optimizer | Verified (293 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 |
| 119488 | 2025-12-01 14:52 | 2025-12-02 4:37 | MySQL Server: Optimizer | Verified (180 days) | S2 | 9.4.0, 9.5.0 | Ubuntu (22.04) | Any | NTERSECT Bug: NULL-Handling Inconsistency Returns Non-Intersecting Row from Outer Joins with NULL Comparisons |
| 119280 | 2025-10-31 11:55 | 2026-05-29 10:58 | MySQL Server: InnoDB storage engine | Open (2 days) | S2 | 9.5.0 | Any | Any | INSTANT ADD succeeds even when the size of a row crosses row_size_limit |
| 119325 | 2025-11-07 7:33 | 2025-11-07 7:33 | MySQL Server: InnoDB storage engine | Open | S2 | 9.5.0 | Any | Any | SELECT does not create a snapshot when the WHERE condition evaluates to false |
| 119463 | 2025-11-26 6:23 | 2026-02-05 20:07 | MySQL Server: Charsets | Verified (115 days) | S2 | 9.5.0 | Any | Any | some charactor may be truncated use utf8mb4_general_ci collation_connection |
| 119520 | 2025-12-06 17:55 | 2025-12-08 3:51 | MySQL Server: Optimizer | Verified (174 days) | S2 | 9.5.0 | Ubuntu (22.04) | Any | Inconsistent NULL and Negative Zero Handling in EXISTS Subquery with HAVING Clause |
| 119590 | 2025-12-24 6:41 | 2025-12-26 6:22 | MySQL Server: Optimizer | Verified (156 days) | S1 | 9.5.0 | Any | Any | EXCEPT (SELECT NULL) returns incorrect result (missing row) on DECIMAL primary key column |
| 119594 | 2025-12-24 14:03 | 2025-12-26 6:21 | MySQL Server: Optimizer | Verified (156 days) | S1 | 9.5.0 | Any | Any | INTERSECT (SELECT NULL) incorrectly returns non-NULL rows when column is PRIMARY KEY |
| 119650 | 2026-01-09 2:04 | 2026-04-22 20:58 | MySQL Server: Optimizer | Closed (39 days) | S1 | 9.5.0 | Any | Any | IN operator returns unexpected result when one of values in the list is NULL |
| 119652 | 2026-01-09 5:20 | 2026-01-09 8:45 | MySQL Server: Optimizer | Not a Bug (142 days) | S2 | 9.5.0 | Windows | Any | Inconsistent behavior: Query throws "Incorrect arguments" vs returns Empty Set depending on execution plan |
| 119793 | 2026-01-27 10:32 | 2026-02-04 16:32 | MySQL Server: Prepared statements | Verified (116 days) | S1 | 9.5.0 | Any | Any | Incorrect result of prepared SELECT when running with JDBC |
| 119909 | 2026-02-12 21:31 | 2026-02-12 21:31 | MySQL Server: Optimizer | Open | S2 | 9.5.0 | Any | Any | Wrong result due to unsafe Item_max optimization triggering on homogeneous subqueries but not heterogeneous ones |
| 119949 | 2026-02-26 14:21 | 2026-03-03 9:28 | MySQL Server: InnoDB storage engine | Open (89 days) | S2 | 9.5.0 | Any | Any | DELETE statement fails to delete the row after blocking is resumed |
| 120045 | 2026-03-13 2:54 | 2026-03-30 13:41 | MySQL Server: Optimizer | Duplicate (62 days) | S1 | 9.5.0 | Any | Any | INTERSECT Returns Inconsistent Results Based on optimizer_switch and WHERE Clause |
| 120053 | 2026-03-13 10:58 | 2026-03-13 15:09 | MySQL Server: Optimizer | Duplicate (79 days) | S1 | 9.5.0 | Any | Any | EXCEPT Returns Different Results Based on Composite Primary Key, WHERE Conditions, BNL Optimization |
| 120121 | 2026-03-20 4:51 | 2026-03-20 9:41 | MySQL Server: Optimizer | Duplicate (72 days) | S1 | 9.5.0 | Any | Any | Phantom Drift: Wrong Result in INTERSECT with NULL caused by Prefix Primary Key and Cartesian Join |
| 119485 | 2025-12-01 14:10 | 2025-12-02 5:32 | MySQL Server: Optimizer | Verified (180 days) | S2 | 9.5.0,8.0.41 | Any | Any | Wrong result with left joins |
| 119499 | 2025-12-03 15:20 | 2026-05-28 1:13 | MySQL Server: Optimizer | Documenting (177 days) | S2 | 9.5.0,8.0.41 | Any | Any | Item_view_ref::used_tables() is wrong, leads to wrong query result |
| 119996 | 2026-03-06 11:07 | 2026-05-28 1:13 | MySQL Server: DDL | Documenting (75 days) | S2 | 9.6 | Any | Any | Row delete from a table with selfreferental FK breaks replication |
| 120289 | 2026-04-19 14:35 | 2026-04-20 8:13 | MySQL Server: Optimizer | Verified (41 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Mismatch in indexed `IN` under windows function query |
| 120299 | 2026-04-20 9:00 | 2026-04-20 10:41 | MySQL Server: Optimizer | Verified (41 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | mismatch in `DELETE ... EXISTS` under window function query |
| 120307 | 2026-04-21 14:02 | 2026-04-22 4:23 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for `<= ANY (subquery)` in a window-function query |
| 120308 | 2026-04-21 14:03 | 2026-04-22 4:27 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for string-vs-`BIT` comparison in a window-function query |
| 120310 | 2026-04-21 16:45 | 2026-04-22 4:34 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for MAX(BIT(8)) UNION ALL BLOB after view extraction in a window-function workload |
| 120311 | 2026-04-21 16:52 | 2026-04-22 4:38 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for grouped SUM(DISTINCT ...) with DENSE_RANK() after view extraction |
| 120312 | 2026-04-21 16:58 | 2026-04-22 4:40 | MySQL Server: Optimizer | Verified (39 days) | S2 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result for MIN(TIME) UNION ALL DATE after view extraction |
| 120313 | 2026-04-21 17:11 | 2026-04-22 4:43 | MySQL Server: Optimizer | Verified (39 days) | S1 | 9.6 | Linux (Observed on Linux via the `mysql:9.6` ) | Any | Wrong result when only GROUP BY key order is changed in a join query with nested window-function input |
| 120302 | 2026-04-20 9:51 | 2026-04-20 11:26 | MySQL Server: Optimizer | Verified (41 days) | S2 | 9.6.0 | Any | Any | Inconsistent results between VIEW and CTE involving YEAR(DATETIME), UNION, and JOIN. |
| 120562 | 2026-05-28 12:53 | 2026-05-28 12:53 | MySQL Server: InnoDB storage engine | Open | S1 | 9.6.0 | Linux | Any | InnoDB crashes with assertion failure when UPDATE touches a table with many secondary indexes |
| 120291 | 2026-04-19 16:45 | 2026-04-27 13:16 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.6.0 | Any | Any | Inconsistent results between VIEW and CTE involving EXISTS subquery and LEFT JOIN |
| 120539 | 2026-05-24 15:26 | 2026-05-24 15:26 | MySQL Server: FULLTEXT search | Open | S2 | 9.6.0 | Linux | Any | Duplicate FULLTEXT index on a column returns wrong MATCH...AGAINST results when combined with a STORED generated column |
| 120527 | 2026-05-22 11:47 | 2026-05-27 11:56 | MySQL Server: Optimizer | Can't repeat (4 days) | S2 | 9.6.0 | Linux | Any | FULLTEXT index scan with ORDER BY and numeric WHERE filter returns empty result set |
| 120499 | 2026-05-20 5:02 | 2026-05-20 5:02 | MySQL Server: Stored Routines | Open | S2 | 9.6.0 | Linux | x86 (AMD EPYC 9K65) | Recursive stored procedure with max_sp_recursion_depth >= 250 crashes mysqld |
| 120344 | 2026-04-26 6:43 | 2026-04-27 4:04 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.6.0 | Any | Any | VIEW and equivalent CTE return different results with UNION, YEAR(0), and repeated reference in subquery |
| 120476 | 2026-05-14 11:53 | 2026-05-18 8:25 | MySQL Server: Optimizer | Verified (13 days) | S2 | 9.6.0 | Linux | Any | Index Merge Union returns duplicate row for overlapping OR conditions, producing wrong result count |
| 120350 | 2026-04-27 8:35 | 2026-04-28 4:31 | MySQL Server: Optimizer | Verified (33 days) | S2 | 9.6.0 | Linux | Any | Prefix index on TEXT column causes range scan to miss qualifying rows in MySQL |
| 120352 | 2026-04-27 9:34 | 2026-04-28 4:26 | MySQL Server: Optimizer | Verified (33 days) | S2 | 9.6.0 | Linux | Any | Prefix index with length 1 causes incorrect "Zero rows" optimization with float overflow literal in range condition |
| 119744 | 2026-01-22 9:52 | 2026-01-22 9:52 | MySQL Server: InnoDB storage engine | Open | S2 | 9.6.0 | Any | Any | mysqlbackup_page_track_purge_up_to not working |
| 119767 | 2026-01-24 12:57 | 2026-01-24 12:57 | MySQL Server: Compiling | Open | S2 | 9.6.0 | FreeBSD (15) | x86 | MySQL fails to build on FreeBSD |
| 119775 | 2026-01-26 6:37 | 2026-01-26 6:37 | MySQL Server: MyISAM storage engine | Open | S2 | 9.6.0 | Any | Any | External locking should be removed |
| 119918 | 2026-02-17 8:12 | 2026-02-17 8:31 | MySQL Server: Optimizer | Verified (103 days) | S2 | 9.6.0 | Any | Any | Tree based explain format doesn't work well with MySQL Client or MySQL Shell |
| 120013 | 2026-03-09 11:27 | 2026-03-09 13:50 | MySQL Server: Optimizer | Not a Bug (83 days) | S1 | 9.6.0 | Any | Any | Inconsistent results between equivalent queries involving logical predicates and set operations |
| 120146 | 2026-03-25 6:22 | 2026-05-28 14:53 | MySQL Server: Optimizer | Open (3 days) | S2 | 9.6.0 | Linux (ubuntu 20.04) | x86 | Wrong result due to incorrect const-table pruning for NOT IN on FLOAT UNIQUE column in MEMORY engine |
| 120206 | 2026-04-02 19:48 | 2026-04-02 19:48 | MySQL Server: Partitions | Open | S2 | 9.6.0 | Any | Any | EXCHANGE PARTITION bypasses CHECK CONSTRAINT validation |
| 120222 | 2026-04-07 12:02 | 2026-04-09 19:30 | MySQL Server: Data Types | Verified (52 days) | S2 | 9.6.0 | Linux | Any | VECTOR(n) dimension silently wraps to wrong value due to integer overflow in parser |
| 120223 | 2026-04-07 12:06 | 2026-04-09 19:33 | MySQL Server: Data Types | Verified (52 days) | S2 | 9.6.0 | Linux | Any | VECTOR(0) silently accepted, produces unusable column with corrupted metadata (dimension 4294967295) |
| 120244 | 2026-04-10 12:40 | 2026-04-10 13:51 | MySQL Server: DDL | Open | S1 | 9.6.0 | Any | Any | Unexpected error `'0' for column '' at row -1` triggered by ALTER |
| 120245 | 2026-04-10 13:14 | 2026-04-10 13:55 | MySQL Server: DDL | Open | S1 | 9.6.0 | Any | Any | Unexpected error `Got error -1 - 'Unknown error -1' from storage engine` |
| 120251 | 2026-04-12 11:47 | 2026-04-13 4:58 | MySQL Server: DDL | Verified (48 days) | S2 | 9.6.0 | Any | Any | REPLACE INTO silently bypasses ON DELETE FK rules with innodb_native_foreign_keys=OFF |
| 120254 | 2026-04-13 10:04 | 2026-04-14 8:48 | MySQL Server: Optimizer | Not a Bug (47 days) | S1 | 9.6.0 | Any | Any | Equivalent queries show different behavior due to short-circuit optimization failure |
| 120265 | 2026-04-14 8:24 | 2026-04-14 9:47 | MySQL Server: Optimizer | Verified (47 days) | S1 | 9.6.0 | Any | Any | Query returns with UNION, INTERSECT ALL and Derived SELECT DISTINCT |
| 120293 | 2026-04-19 17:10 | 2026-04-27 14:10 | MySQL Server: Optimizer | Verified (34 days) | S1 | 9.6.0; 8.0.45 | Any | Any | Query result inconsistency between VIEW and CTE involving a UNION of scalar aggregation and grouped aggregation |
| 120292 | 2026-04-19 17:01 | 2026-04-27 14:09 | MySQL Server: Optimizer | Verified (34 days) | S2 | 9.6.0; 8.0.45 | Any | Any | Inconsistent results between VIEW and CTE involving IN subquery and RIGHT JOIN |
| 120457 | 2026-05-12 15:03 | 2026-05-28 1:13 | MySQL Server: Optimizer | Patch pending (14 days) | S2 | 9.7 | CentOS | x86 | Hypergraph optimizer returns wrong results for LEFT JOIN LATERAL with SEMI JOIN when derived_merge |
| 120399 | 2026-05-04 9:31 | 2026-05-04 9:31 | MySQL Server: Packaging | Open | S2 | 9.7.0 | Any | Any | missing build dependency: lz4-devel |
| 120398 | 2026-05-04 9:29 | 2026-05-04 9:29 | MySQL Server: Packaging | Open | S2 | 9.7.0 | Any | Any | missing build dependency: libevent-devel |
| 120429 | 2026-05-10 7:04 | 2026-05-28 1:13 | MySQL Server: Optimizer | Documenting (20 days) | S2 | 9.7.0 | Windows (Windows Server 2022) | Any | IFNULL function does not handle NULL |
| 120397 | 2026-05-04 9:27 | 2026-05-04 9:27 | MySQL Server: Packaging | Open | S2 | 9.7.0 | Any | Any | missing build dependency: libzstd-devel |
| 120540 | 2026-05-25 1:44 | 2026-05-29 5:20 | MySQL Server: Optimizer | Patch pending (4 days) | S2 | 9.7.0 | Ubuntu | x86 | A negated `IS TRUE` guard can still match a DECIMAL row for which the guarded predicate is true |
| 120394 | 2026-05-04 5:31 | 2026-05-04 5:31 | MySQL Server: Packaging | Open | S2 | 9.7.0 | Any | Any | missing build dependency: libedit-devel |
| 120538 | 2026-05-24 13:46 | 2026-05-27 13:53 | MySQL Server: Optimizer | Duplicate (4 days) | S2 | 9.7.0 | Ubuntu | x86 | A RIGHT JOIN predicate treats IFNULL(NULL, non-NULL DECIMAL ZEROFILL) as non-matching and drops obvious rows |
| 120532 | 2026-05-23 12:34 | 2026-05-27 13:43 | MySQL Server: Optimizer | Duplicate (4 days) | S2 | 9.7.0 | Ubuntu | x86 | An unused derived subquery triggers a DISTINCT/IFNULL wrong-result in the original path |
| 120422 | 2026-05-08 8:56 | 2026-05-08 8:56 | MySQL Server: Optimizer | Open | S2 | 9.7.0 (also reproducible in 8.0.x) | Any | Any | ORDER BY ignored when internal_tmp_mem_storage_engine = TempTable with GROUP BY on CTE |
| 119444 | 2025-11-22 11:32 | 2026-02-05 20:32 | MySQL Server: Optimizer | Not a Bug (115 days) | S2 | any | Any | Any | Union with bound variable silently trims result |
| 120327 | 2026-04-23 7:46 | 2026-04-23 12:40 | MySQL Server: Replication | Open | S2 | MySQL 8.4 | Any | Any | Unsigned integer wraparound in Binlog_sender::run() when binlog_row_event_max_size is set to a large value |
| 119097 | 2025-09-30 9:04 | 2025-12-15 11:15 | MySQL Server: Optimizer | Verified (167 days) | S2 | MySQL 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns different results compared to INNER JOIN with identical conditions |
| 120319 | 2026-04-22 7:11 | 2026-04-22 9:43 | MySQL Server: Optimizer | Duplicate (39 days) | S2 | MySQL 8.4.6 LTS | Any | Any | IN() clause containing over-length string values for VARCHAR(N) column causes full table scan in MySQL 8.4.x, while sing |
| 118359 | 2025-06-04 13:43 | 2025-06-16 12:33 | MySQL Server: InnoDB storage engine | Verified (354 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-15 16:00 | MySQL Server: Optimizer | Verified (262 days) | S2 | MySQL8.0.41 | Any | Any | queries have different results using and without index |
| 120441 | 2026-05-11 11:29 | 2026-05-12 2:31 | MySQL Server: InnoDB storage engine | Open (19 days) | S2 | trunk 8.0.24 8.4.9 | Any | Any | InnoDB btr_create() can hold page latches for a long time because buf_stat_per_index->inc() may synchronously run ut_loc |
| Showing all 321 (Edit, Save, CSV, Feed) |
