| Showing all 227 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119797 | 2026-01-27 20:09 | 2026-01-27 20:09 | MySQL Server: General | Open | S3 | Any | Any | Contribution: Feat: Native Vector Search with HNSW Indexing | |
| 119796 | 2026-01-27 19:12 | 2026-01-27 19:50 | MySQL Server: DDL | Open | S2 | 8.0.35 | Any | Any | Encrypted data changes when adding columns |
| 119790 | 2026-01-27 10:14 | 2026-01-27 12:07 | MySQL Server: Optimizer | Verified (1 day) | S1 | 8.0.44 | Any | Any | Unexpected result of expression IN NULL |
| 119784 | 2026-01-27 0:53 | 2026-01-27 1:26 | MySQL Server: Partitions | Open (1 day) | S3 | 8.0.42 and later | Any | Any | Fix partition pruning with non-constant defaults regression |
| 119782 | 2026-01-26 17:22 | 2026-01-27 8:36 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: Fix partition pruning with non-constant defaults regression | |
| 119780 | 2026-01-26 14:40 | 2026-01-26 15:15 | MySQL Server: Optimizer | Verified (2 days) | S3 | 8.0.44 | Ubuntu (22.04) | Any | UNION ALL + AND + WHERE IS UNKNOWN query results are incorrect |
| 119778 | 2026-01-26 12:56 | 2026-01-26 15:01 | MySQL Server: Optimizer | Verified (2 days) | S3 | 8.0.x, 8.4.x | Any | Any | after changing SUM(distinct x) to - SUM(distinct -x),the value unexpectedly change |
| 119776 | 2026-01-26 9:31 | 2026-01-26 13:51 | MySQL Server: Optimizer | Verified (2 days) | S3 | 8.0.41 | Any | Any | Semantically identical SQLs yield different result sets. |
| 119772 | 2026-01-25 11:30 | 2026-01-26 13:23 | MySQL Server: DML | Duplicate (3 days) | S2 | 8.0.45 | CentOS | Any | [8.0.45-debug] Lost connection to MySQL server during query |
| 119770 | 2026-01-24 19:09 | 2026-01-27 10:03 | MySQL Server: Optimizer | Duplicate (1 day) | S2 | 8.4 | Any | Any | MySQL 8.4 optimizer uses full table scan for IN (...) on prefix index, but works in 8.0 |
| 119769 | 2026-01-24 14:46 | 2026-01-26 18:21 | MySQL Server: InnoDB storage engine | Open | S2 | 9.4.0 | Any | Any | The transaction reads the value inserted by the blocked statement |
| 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 |
| 119759 | 2026-01-22 18:55 | 2026-01-27 8:06 | MySQL Server: InnoDB storage engine | Open (6 days) | S2 | 8.0.42 | Any | Any | InnoDB allow reads on non-durable data, which can be lost after crash(visibility before durability window) |
| 119752 | 2026-01-22 15:08 | 2026-01-22 21:36 | MySQL Server: Optimizer | Verified (6 days) | S3 | 8.0.44 | Any | Any | after changing MINUTE(subq.c1) to MINUTE(subq.c1 + INTERVAL '60' MINUTE),the result become empty. |
| 119745 | 2026-01-22 10:24 | 2026-01-27 7:03 | MySQL Server: Documentation | Verified (1 day) | S3 | 9.6.0 | Any | Any | documentation: mysql 9.6 release notes - classic_hashing |
| 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 |
| 119741 | 2026-01-22 7:00 | 2026-01-22 8:35 | MySQL Server: Optimizer | Verified (6 days) | S1 | 8.0.44 | Any | Any | internal_tmp_mem_storage_engine = MEMORY setting makes the DISTINCTROW returns incorrect result on 0 and -0 |
| 119735 | 2026-01-21 14:21 | 2026-01-21 14:21 | MySQL Server: Tests | Open | S3 | 8.4.8 | MacOS (26.2) | ARM | Unhandled error log warning in main.initialize-sha256 |
| 119731 | 2026-01-21 3:10 | 2026-01-21 3:13 | MySQL Server: InnoDB storage engine | Open | S3 | MySQL 8.4 | Any | Any | mysql 8.4 ut_a is invalid |
| 119727 | 2026-01-20 10:11 | 2026-01-27 18:37 | MySQL Server: Data Types | Verified (8 days) | S3 | 8.0.44 | Any | Any | wrong result for 'value between a and null' for certain temporal types |
| 119724 | 2026-01-20 5:55 | 2026-01-20 8:08 | MySQL Server: Optimizer | Verified (8 days) | S3 | 8.0.44 | Any | Any | after changing asin function in group clause,column's value unexpectedly change |
| 119716 | 2026-01-19 1:36 | 2026-01-19 9:16 | MySQL Server: Optimizer | Verified (9 days) | S1 | 8.0.44 | Any | Any | Suboptimal query plan generated by normal query compare to prepared statement |
| 119715 | 2026-01-18 13:14 | 2026-01-18 13:14 | MySQL Server: Documentation | Open | S3 | 8.4, 9.5 | Any | Any | Connection compression for MySQL Classic should include reference to net_buffer_length |
| 119714 | 2026-01-18 12:26 | 2026-01-19 9:01 | MySQL Server: Optimizer | Verified (9 days) | S3 | 8.0.44 | Any | Any | after changing ASIN(hpg31.c1) in group clause,the col_1’s value unexpectedly change. |
| 119713 | 2026-01-18 11:19 | 2026-01-20 9:37 | MySQL Server: Optimizer | Verified (8 days) | S3 | 8.0.39, 8.0.44, 8.4.6 | Any | Any | MySQL has hard time using the right indexes |
| 119710 | 2026-01-17 8:16 | 2026-01-19 8:03 | MySQL Server: Optimizer | Not a Bug (9 days) | S3 | 8.0.x, 8.4.x | Any | Any | column value unexpectedly change ,after changing atan2 function |
| 119708 | 2026-01-16 14:58 | 2026-01-17 5:22 | MySQL Server: Optimizer | Open (11 days) | S2 | 8.0.44 | Linux | Any | INNER JOIN and STRAIGHT_JOIN produce different results with FLOAT UNIQUE column on MEMORY table |
| 119707 | 2026-01-16 11:27 | 2026-01-16 11:27 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | SERIALIZABLE Isolation Level: Concurrent Transactions with AUTO_INCREMENT Produce Non-Serializable Result |
| 119706 | 2026-01-16 10:46 | 2026-01-16 10:49 | MySQL Server: Optimizer | Open | S2 | 8.0.44, 9.5.0 | Any | Any | Incorrect Results from ALL/ANY Subquery MIN/MAX Optimization with Type Mismatch |
| 119704 | 2026-01-16 8:20 | 2026-01-16 8:20 | MySQL Server: Documentation | Open | S2 | 8.4 | Any | Any | Outdated IPv6 Broker documentation |
| 119701 | 2026-01-16 7:18 | 2026-01-16 9:45 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.44 | Any | Any | after changing FLOOR function,col_1’s value unexpectedly change |
| 119700 | 2026-01-16 7:14 | 2026-01-22 13:16 | MySQL Server: Optimizer | Duplicate (6 days) | S3 | 8.0.44 | Any | Any | column value unexpectedly change after adding distinct |
| 119698 | 2026-01-16 7:08 | 2026-01-16 9:16 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0. | Any | Any | rows become less unexpectedly caused by on clause |
| 119697 | 2026-01-16 7:06 | 2026-01-22 13:08 | MySQL Server: Optimizer | Duplicate (6 days) | S3 | 8.0.44 | Any | Any | Bit value changed after adding DISTINCT in query |
| 119696 | 2026-01-16 7:03 | 2026-01-16 8:58 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.44 | Any | Any | float value Precision loss caused by removing distinct |
| 119695 | 2026-01-16 6:59 | 2026-01-16 8:48 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.44 | Any | Any | The appearance of rows that should not exist caused by on clause |
| 119694 | 2026-01-16 6:56 | 2026-01-16 8:39 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.44 | Any | Any | rows unexpectedly become less after changing INNER to LEFT |
| 119693 | 2026-01-16 6:39 | 2026-01-16 8:28 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.44 | Any | Any | column value change after changing INNER to LEFT |
| 119692 | 2026-01-16 5:23 | 2026-01-16 8:09 | MySQL Server: Optimizer | Verified (12 days) | S1 | 8.0.44 | Any | Any | The normal query generated a non-optimal query plan. |
| 119687 | 2026-01-15 10:23 | 2026-01-15 13:18 | MySQL Server: Optimizer | Verified (13 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal and prepared INSERT |
| 119686 | 2026-01-15 8:37 | 2026-01-15 13:11 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.44 | Linux | x86 | Incorrect result when joined table has PRIMARY KEY and WHERE predicate involves CASE |
| 119684 | 2026-01-14 18:11 | 2026-01-15 9:33 | MySQL Server: Documentation | Verified (13 days) | S3 | 9.5.0 | Any | Any | 9.5.0 release notes explain the enforce_gitd_consistency change incorrectly |
| 119683 | 2026-01-14 15:35 | 2026-01-15 12:57 | MySQL Server: Optimizer | Verified (13 days) | S1 | 8.0.44 | Linux | x86 | Different results for INNER JOIN and STRAIGHT_JOIN with GREATEST() IN predicate |
| 119681 | 2026-01-14 14:19 | 2026-01-15 12:47 | MySQL Server: Optimizer | Verified (13 days) | S3 | 9.5.0 | Any | Any | Floating-point precision loss occurs when changing avg(x) to -avg(-x) |
| 119680 | 2026-01-14 13:51 | 2026-01-15 12:25 | MySQL Server: Optimizer | Verified (13 days) | S3 | 8.0.44 | Any | Any | after changing AVG(cte.col_2) to -AVG(-cte.col_2) ,rows become less |
| 119679 | 2026-01-14 13:40 | 2026-01-15 11:25 | MySQL Server: Optimizer | Verified (13 days) | S3 | 8.0.45 | Any | Any | after changing SUM(t3.c9) to -SUM(-t3.c9),the rows become less |
| 119678 | 2026-01-14 12:37 | 2026-01-14 12:38 | MySQL Server: C API (client library) | Open | S3 | 8.0.44 | Any | Any | Async client use-after-free issues from valgrind |
| 119677 | 2026-01-14 9:08 | 2026-01-14 9:08 | MySQL Server: Documentation | Open | S3 | 8.4, 9.5 | Any | Any | Session Tracking example doesn't work |
| 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 |
| 119672 | 2026-01-13 14:54 | 2026-01-14 9:35 | MySQL Server: Stored Routines | Open (14 days) | S3 | all versions > 8.0 | Any | Any | [ERROR] [MY-013235] [Server] Error in parsing Event while upgrading MySQL version if Event was created in ANSI sql_mode |
| 119670 | 2026-01-13 13:46 | 2026-01-13 14:51 | MySQL Server: Optimizer | Verified (15 days) | S1 | 8.0.44 | Any | Any | Incorrect result caused by index |
| 119669 | 2026-01-13 13:27 | 2026-01-13 14:53 | MySQL Server: Optimizer | Verified (15 days) | S1 | 8.0.44 | Any | Any | Inconsistent behaviour between normal query and prepared statement |
| 119667 | 2026-01-13 11:42 | 2026-01-26 14:07 | MySQL Server: InnoDB storage engine | Open (2 days) | S2 | 9.4.0 | Ubuntu (22.04) | x86 (x86_64) | Assertion failure ddl0buffer.cc:197 with innodb-ddl-threads=4 + O_DIRECT |
| 119666 | 2026-01-13 7:37 | 2026-01-13 8:16 | MySQL Server: Optimizer | Verified (15 days) | S3 | 8.0.41 | Any | Any | YEAR column IN (1,2) does not match expected conversion behavior |
| 119664 | 2026-01-13 5:16 | 2026-01-13 7:59 | MySQL Server: Optimizer | Not a Bug (15 days) | S3 | 9.3.0-cluster | Ubuntu | Any | Inconsistant result when modifying tables' partition strategy |
| 119663 | 2026-01-13 4:24 | 2026-01-13 7:46 | MySQL Server: Optimizer | Verified (15 days) | S3 | 9.3.0 | Ubuntu | Any | Query reports error when turn on optimizer_switch |
| 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 |
| 119656 | 2026-01-12 2:35 | 2026-01-12 2:35 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.41 | Any | Any | after crash recovery check table warning: Index xxx is marked as corrupted |
| 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. |
| 119653 | 2026-01-09 9:39 | 2026-01-09 9:39 | MySQL Server: InnoDB storage engine | Open | S5 | 8.0.44 | Any | Any | Reduce unnecessary if checks in core logic |
| 119652 | 2026-01-09 5:20 | 2026-01-09 8:45 | MySQL Server: Optimizer | Not a Bug (19 days) | S2 | 9.5.0 | Windows | Any | Inconsistent behavior: Query throws "Incorrect arguments" vs returns Empty Set depending on execution plan |
| 119650 | 2026-01-09 2:04 | 2026-01-09 7:34 | MySQL Server: Optimizer | Verified (19 days) | S1 | 9.5.0 | Any | Any | IN operator returns unexpected result when one of values in the list is NULL |
| 119649 | 2026-01-08 12:18 | 2026-01-08 12:18 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | SERIALIZABLE Isolation Violation with Consistent Snapshot in MySQL |
| 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 |
| 119646 | 2026-01-08 7:46 | 2026-01-21 20:24 | MySQL Server: Optimizer | Duplicate (7 days) | S2 | 8.0.33 | Ubuntu (22.04) | Any | View + Type Conversion + IN Subquery Returns Wrong Result |
| 119644 | 2026-01-07 20:26 | 2026-01-07 20:26 | MySQL Server: Security: Privileges | Open | S3 | 9.5.0 | Any | Any | Incorrect Column-level Privilege Checks of the CREATE TABLE ... LIKE Commands |
| 119643 | 2026-01-07 18:53 | 2026-01-08 5:48 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.44 | Linux | x86 | Undo log purging goes through purge boundary overwrites undo log |
| 119639 | 2026-01-07 9:05 | 2026-01-21 21:05 | MySQL Server: Optimizer | Duplicate (7 days) | S2 | 8.0.42 | Any | Any | Assertion Failure in LEAST() Function with Unsigned Columns |
| 119638 | 2026-01-07 8:40 | 2026-01-07 9:59 | MySQL Server: Optimizer | Verified (21 days) | S3 | 8.0.42 | Any | Any | Incorrect Condition Evaluation for BETWEEN with NULL Upper Bound |
| 119636 | 2026-01-07 7:55 | 2026-01-07 9:20 | MySQL Server: Optimizer | Verified (21 days) | S3 | 8.0 | Any | Any | Incorrect Condition Evaluation for float unsigned zerofill Columns |
| 119635 | 2026-01-07 7:27 | 2026-01-07 11:07 | MySQL Server: Optimizer | Verified (21 days) | S3 | 8.0.42+ | Any | Any | Returns incorrect query results when using the between keyword |
| 119632 | 2026-01-06 12:48 | 2026-01-06 12:48 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | Inconsistent Auto-increment Primary Key Allocation Under Concurrent Operations Violates Transaction Consistency |
| 119631 | 2026-01-06 12:13 | 2026-01-21 12:16 | MySQL Server: Optimizer | Duplicate (7 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 |
| 119630 | 2026-01-06 7:59 | 2026-01-21 18:56 | MySQL Server: Optimizer | Duplicate (7 days) | S2 | 8.0.33 | Any (22.04) | Any | Optimizer incorrectly merges derived table with type conversion and WHERE clause, causing wrong query results |
| 119628 | 2026-01-05 22:20 | 2026-01-05 22:20 | MySQL Server: InnoDB storage engine | Open | S1 | 8.0 | Any | Any | Undo Truncation Bug, not fixed in 8.0, leads to Data Corruption. |
| 119626 | 2026-01-05 13:33 | 2026-01-06 1:30 | MySQL Server: InnoDB storage engine | Open (22 days) | S3 | 8.0.41 | Any | Any | Adding an index using the inplace algorithm will result in a "Duplicate entry" error in the replace into syntax. |
| 119623 | 2026-01-05 12:06 | 2026-01-05 12:35 | MySQL Server: DDL | Open (23 days) | S3 | 8.0.43 | CentOS | x86 | Cannot add or update a child row: a foreign key constraint fails |
| 119619 | 2026-01-04 14:07 | 2026-01-04 21:17 | MySQL Server: Optimizer | Verified (24 days) | S1 | 8.0 | Any | Any | Incorrect results for REPLACE function |
| 119618 | 2026-01-04 8:39 | 2026-01-04 8:39 | MySQL Server: Information schema | Open | S3 | 9.4 | Any | Any | misleading name of external temp table in I_S.INNODB_TEMP_TABLE_INFO |
| 119617 | 2026-01-03 8:02 | 2026-01-03 8:04 | MySQL Server: Documentation | Open (25 days) | S1 | Any | Any | Documentation is inconsistent/misleading | |
| 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 |
| 119608 | 2025-12-30 3:39 | 2025-12-30 3:39 | MySQL Server: InnoDB storage engine | Open | S3 | 9.3.0 | Any | Any | UPDATE is not blocked by SELECT ... FOR SHARE under READ COMMITTED isolation level |
| 119607 | 2025-12-30 2:53 | 2025-12-30 2:53 | MySQL Server: Errors | Open | S3 | Any | Any | can't imorte csv. | |
| 119606 | 2025-12-29 14:23 | 2026-01-21 20:58 | MySQL Server: Optimizer | Duplicate (12 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 |
| 119605 | 2025-12-29 9:37 | 2025-12-29 13:00 | MySQL Server: Optimizer | Verified (30 days) | S3 | 8.0.27 | Any | Any | GROUP BY brings unnecessary order columns |
| 119603 | 2025-12-29 1:19 | 2026-01-04 20:40 | MySQL Server: Optimizer | Verified (24 days) | S2 | 8.0 | Any | Any | TRUE >= ALL(...) returns incorrect result (1) when comparing against a NOT NULL column |
| 119602 | 2025-12-28 21:11 | 2025-12-29 10:39 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0 | Any | Any | Inconsistent data |
| 119600 | 2025-12-28 4:45 | 2025-12-28 4:45 | MySQL Server: Documentation | Open | S3 | 8.4+ | Any | Any | FOUND_ROWS not marked as deprecated |
| 119599 | 2025-12-27 2:30 | 2025-12-29 4:51 | MySQL Server: Optimizer | Verified (30 days) | S3 | 8.0.41 | Any | Any | Under the same SQL, the results of hash join and nested loop join are inconsistent |
| 119598 | 2025-12-26 6:46 | 2025-12-29 4:52 | MySQL Server: DDL | Open | S3 | Any | Any | ALTER TABLE will report Deadlock found ... when do a RENAME to itself and ENABLE KEYS. | |
| 119597 | 2025-12-26 2:37 | 2025-12-26 17:57 | MySQL Server: Optimizer | Verified (33 days) | S1 | 8.0.44 | Any | Any | WHERE ... IN ... incorrectly returns rows |
| 119596 | 2025-12-26 2:01 | 2025-12-29 4:55 | MySQL Server: Optimizer | Verified (30 days) | S3 | 9.2,9.4 | Any | Any | Inconsistent results use IFNULL with different query plan |
| 119594 | 2025-12-24 14:03 | 2025-12-26 6:21 | MySQL Server: Optimizer | Verified (33 days) | S1 | 9.5.0 | Any | Any | INTERSECT (SELECT NULL) incorrectly returns non-NULL rows when column is PRIMARY KEY |
| 119593 | 2025-12-24 8:36 | 2025-12-24 8:36 | MySQL Server: Row Based Replication ( RBR ) | Open | S3 | 8.0.* | Any | Any | Generated Column Calculation on the replica ERROR |
| 119591 | 2025-12-24 7:27 | 2025-12-26 17:48 | MySQL Server: Data Types | Verified (33 days) | S1 | 8.0.44 | Any | Any | Incorrect result type for NULLIF(DOUBLE,BIGINT) function |
| 119590 | 2025-12-24 6:41 | 2025-12-26 6:22 | MySQL Server: Optimizer | Verified (33 days) | S1 | 9.5.0 | Any | Any | EXCEPT (SELECT NULL) returns incorrect result (missing row) on DECIMAL primary key column |
| 119588 | 2025-12-24 3:03 | 2025-12-26 17:23 | MySQL Server: Optimizer | Verified (33 days) | S1 | 8.0.44 | Any | Any | Incorrect result in JOIN with IN subquery |
| 119586 | 2025-12-23 9:09 | 2025-12-26 16:50 | MySQL Server: Data Types | Verified (33 days) | S1 | 8.4.7 | Any | Any | Inconsistent results for date conversion |
| 119585 | 2025-12-23 3:17 | 2025-12-23 5:43 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.30/9.4.0/8.4.6 | Any | Any | In extreme cases, sync_array_get_and_reserve_cell fails to obtain a cell even have space |
| 119584 | 2025-12-22 16:09 | 2025-12-22 19:42 | MySQL Server: Optimizer | Verified (37 days) | S3 | 8.0.44 | Any | Any | The HAVING clause cannot recognize alias columns defined by Boolean expressions in derived tables |
| 119583 | 2025-12-22 7:34 | 2025-12-22 19:35 | MySQL Server: Optimizer | Verified (37 days) | S3 | 8.0.44 | Any | Any | Create index can lead to incorrect results |
| 119582 | 2025-12-22 6:49 | 2025-12-22 19:27 | MySQL Server: Optimizer | Verified (37 days) | S2 | 8.0.44 | Any | Any | Inconsistency functional dependency in ONLY_FULL_GROUP_BY mode between derived tables and physical tables |
| 119581 | 2025-12-20 14:54 | 2025-12-22 19:17 | MySQL Server: Optimizer | Verified (37 days) | S3 | 8.0.33 | Ubuntu (22.04) | Any | FLOOR function shows inconsistent overflow handling |
| 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 |
| 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 |
| 119567 | 2025-12-17 2:53 | 2025-12-18 2:10 | MySQL Server: InnoDB storage engine | Open (41 days) | S2 | 8.0.30/9.4.0/8.4.6 | Any | Any | signal 6 crashed when too many connections |
| 119565 | 2025-12-17 1:06 | 2025-12-17 1:06 | MySQL Server: Optimizer | Open | S3 | 8.0.41 | Any | Any | Temporary table causes incorrect conversion from TIME to JSON type |
| 119564 | 2025-12-16 12:51 | 2025-12-16 12:51 | MySQL Server: InnoDB storage engine | Open | S3 | 9.5.0 | Any | Any | for REPEATABLE READ TRANSACTION ISOLATION, data should not be read if deleted |
| 119558 | 2025-12-16 8:39 | 2025-12-16 8:57 | MySQL Server: Replication | Open (43 days) | S3 | 8.4.7 | Any | Any | SHOW BINLOG EVENTS fails with Event too big |
| 119554 | 2025-12-15 16:22 | 2025-12-29 14:36 | MySQL Server: InnoDB storage engine | Verified (30 days) | S2 | 8.0.43 | CentOS ( 7.9.2009 (Core)) | Any | CRASH SERVER after Truncate |
| 119545 | 2025-12-12 7:27 | 2025-12-12 8:41 | MySQL Server: DML | Not a Bug (47 days) | S3 | 9.5.0 | Any | Any | sql using in subquery execute unexpectly successful |
| 119542 | 2025-12-11 18:59 | 2025-12-11 18:59 | MySQL Server: Documentation | Open | S3 | 8.0, 8.4, 9.x | Any | Any | Wrong links in Undo Tablespaces Documentation. |
| 119541 | 2025-12-11 12:32 | 2025-12-12 8:19 | MySQL Server: Optimizer | Verified (47 days) | S2 | 8.0, 8.4, 9.5 | Any | Any | Performance regression due to record buffer in index range scan |
| 119538 | 2025-12-11 1:54 | 2025-12-12 5:12 | MySQL Server: Optimizer | Verified (47 days) | S3 | 8.0.41 | Any | Any | different values set for sql_buffer_result and materialization lead to different query results. |
| 119531 | 2025-12-09 14:40 | 2025-12-15 14:58 | MySQL Server: Optimizer | Verified (44 days) | S5 | 8.4.6 | Any | Any | Optimizer should use a short-circuit DESC scan for SELECT MAX(PK) WHERE ... |
| 119530 | 2025-12-09 12:38 | 2025-12-11 9:31 | MySQL Server: Optimizer | Verified (48 days) | S1 | 8.4.7 | Any | Any | Incorrect results for NULLIF functions |
| 119528 | 2025-12-09 9:49 | 2025-12-10 12:38 | MySQL Server: Optimizer | Verified (49 days) | S2 | 8.0 | Any | Any | hash join result incorrect |
| 119526 | 2025-12-09 3:13 | 2026-01-11 1:00 | MySQL Server: Optimizer | No Feedback (18 days) | S2 | 8.0.41 | Any | Any | Inconsistent query results caused by the NO_MERGE hint |
| 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 |
| 119520 | 2025-12-06 17:55 | 2025-12-08 3:51 | MySQL Server: Optimizer | Verified (51 days) | S2 | 9.5.0 | Ubuntu (22.04) | Any | Inconsistent NULL and Negative Zero Handling in EXISTS Subquery with HAVING Clause |
| 119517 | 2025-12-05 15:25 | 2025-12-15 5:26 | MySQL Server: InnoDB storage engine | Open (44 days) | S3 | 8.0.44 | Any | Any | Importing Table with Instant Drop Column not fix index col name pointer |
| 119508 | 2025-12-04 11:35 | 2025-12-04 12:02 | MySQL Server: DDL | Open | S3 | 8.0.43 | Any | Any | Parallel `ALTER TABLE … CONVERT TO utf8mb4` on tables used by views leaves missing tablespaces on 8.0 and 8.4. |
| 119503 | 2025-12-03 16:45 | 2025-12-04 20:12 | MySQL Server: InnoDB storage engine | Open (55 days) | S3 | 8.4.6 | Linux | x86 | [InnoDB] Partitioned tables in reserved db name 'aux' act as missing tablespaces after restart |
| 119499 | 2025-12-03 15:20 | 2025-12-05 5:05 | MySQL Server: Optimizer | Verified (54 days) | S2 | 9.5.0,8.0.41 | Any | Any | Item_view_ref::used_tables() is wrong, leads to wrong query result |
| 119498 | 2025-12-03 9:07 | 2026-01-09 1:00 | MySQL Server: Optimizer | No Feedback (20 days) | S1 | 8.4.7-TLS | Any | Any | The different sorting results are caused by the range query. |
| 119497 | 2025-12-03 7:58 | 2025-12-03 8:42 | MySQL Server: DDL | Open | S3 | 8.0.44 | Any | Any | Failed if execute multiple times DDL on same column in one query |
| 119495 | 2025-12-02 21:50 | 2025-12-02 21:50 | MySQL Server: Documentation | Open | S3 | Any | Any | Incomplete documentation for innodb_max_purge_lag. | |
| 119492 | 2025-12-02 11:57 | 2025-12-03 3:38 | MySQL Server: Optimizer | Closed (56 days) | S2 | 8.0.41 | Any | Any | Inconsistent data types of the IN condition in JOIN queries leads to incorrect query results. |
| 119491 | 2025-12-02 8:21 | 2025-12-08 21:10 | MySQL Server: Optimizer | Verified (51 days) | S1 | 8.4.7 | Any | Any | Incorrect results for make_set operation against longtext column |
| 119490 | 2025-12-02 7:48 | 2025-12-02 7:57 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.41 | Any | Any | savepoint |
| 119489 | 2025-12-02 4:44 | 2025-12-02 4:46 | MySQL Server: Replication | Open (57 days) | S3 | 8.4.7 | Any | Any | GTID tags can violate restrictions |
| 119488 | 2025-12-01 14:52 | 2025-12-02 4:37 | MySQL Server: Optimizer | Verified (57 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 |
| 119485 | 2025-12-01 14:10 | 2025-12-02 5:32 | MySQL Server: Optimizer | Verified (57 days) | S2 | 9.5.0,8.0.41 | Any | Any | Wrong result with left joins |
| 119482 | 2025-12-01 12:00 | 2025-12-01 12:04 | MySQL Server: Security: Privileges | Open (58 days) | S3 | 9.5.0 | Linux | Any | OPTIMIZE_LOCAL_TABLE does not support databse-level and table-level granting, which is inconsistent to the documentation |
| 119480 | 2025-12-01 9:38 | 2025-12-03 9:43 | MySQL Server: InnoDB storage engine | Verified (56 days) | S3 | Any | Any | Full table scans on primary keys, MySQL 8.0 performance degradation than MySQL 5.7. | |
| 119474 | 2025-11-29 9:29 | 2025-12-01 4:16 | MySQL Server: Optimizer | Verified (58 days) | S2 | 8.0.41 | Any | Any | Result error caused by the subquery_to_derived optimizer switch |
| 119473 | 2025-11-29 8:17 | 2025-11-30 15:03 | MySQL Server: InnoDB storage engine | Open (60 days) | S3 | 8.0.41 | Any | Any | InnoDB Mutex Deadlock Cause Mysql Crash |
| 119472 | 2025-11-29 8:01 | 2025-12-01 10:23 | MySQL Server: DML | Not a Bug (58 days) | S3 | Any | Any | insert a char column like value 'aaaa ', but insert result is 'aaaa' | |
| 119470 | 2025-11-27 14:30 | 2025-11-28 13:06 | MySQL Server: Optimizer | Verified (61 days) | S1 | 8.0.44+ | Any | Any | sql injection |
| 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, |
| 119465 | 2025-11-26 10:11 | 2025-11-26 10:11 | MySQL Server: Tests | Open | S3 | 9.5.0 | Any | Any | rpl_insert_id test started to fail sporadically after mysql-9.5.0 made GTID mode default |
| 119463 | 2025-11-26 6:23 | 2025-12-25 12:24 | MySQL Server: Charsets | Open | S2 | 9.5.0 | Any | Any | some charactor may be truncated use utf8mb4_general_ci collation_connection |
| 119460 | 2025-11-25 10:08 | 2026-01-21 3:17 | MySQL Server: InnoDB storage engine | Open (7 days) | S2 | 8.0.44 | Any | Any | InnoDB transaction may get stuck in an infinite loop when releasing Read Locks |
| 119457 | 2025-11-25 9:00 | 2025-11-27 12:42 | MySQL Server: InnoDB storage engine | Open (62 days) | S2 | 5.7 | Any | Any | import tablespace cost too long |
| 119456 | 2025-11-25 6:52 | 2025-11-28 14:55 | MySQL Server: Optimizer | Verified (61 days) | S3 | 8.0.44, 8.4.7, 9.5 | Any | Any | Query block name uses mixed decimal/hexadecimal in optimizer trace and hint |
| 119454 | 2025-11-24 16:04 | 2025-11-27 5:11 | MySQL Server: Optimizer | Verified (62 days) | S2 | 9.4.0 | Any | Any | Hash join has wrong result when the join equality involves FLOAT or DECIMAL column |
| 119453 | 2025-11-24 14:12 | 2025-12-07 22:36 | MySQL Server: Optimizer | Verified (52 days) | S2 | 8.0 | Any | Any | DEFAULT(column) returns wrong result when column is to the right of left join |
| 119451 | 2025-11-24 9:50 | 2026-01-21 3:17 | MySQL Server: Locking | Open (7 days) | S2 | 8.0.44 | Any | Any | The schema's MDL lock is held for too long after opening the table |
| 119447 | 2025-11-23 8:34 | 2025-11-27 5:04 | MySQL Server: Optimizer | Verified (62 days) | S5 | 8.0.41 | CentOS | x86 | Prepare Statement execute much slower than normal select query |
| 119446 | 2025-11-23 6:46 | 2025-11-27 4:57 | MySQL Server: Optimizer | Verified (62 days) | S3 | 9.4.0 | Any | Any | rows become more after changing COUNT to COUNT(DISTINCT) |
| 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 |
| 119444 | 2025-11-22 11:32 | 2025-11-27 7:01 | MySQL Server: Optimizer | Open (67 days) | S2 | any | Any | Any | Union with bound variable silently trims result |
| 119443 | 2025-11-22 2:36 | 2025-11-22 2:36 | MySQL Server: Charsets | Open | S3 | mysql-9.5.0 | Any | Any | LOWER() truncation with utf8mb4_0900_ai_ci due to byte expansion (In-place modification failure) |
| 119442 | 2025-11-21 20:13 | 2025-11-27 4:53 | MySQL Server: Optimizer | Verified (62 days) | S5 | 8.4.4 | Any | Any | Optimizer fails to simplify ORDER BY when column is filtered by IS NULL, causing filesort |
| 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 |
| 119433 | 2025-11-20 9:30 | 2025-12-07 21:58 | MySQL Server: Data Types | Verified (52 days) | S1 | 8.4.6 | Any | Any | Inconsistent date conversion behaviors between text and integer |
| 119432 | 2025-11-20 8:47 | 2025-12-07 21:44 | MySQL Server: Data Types | Verified (52 days) | S1 | 8.0 | Any | Any | Inconsistent time conversion behaviors between text and integer |
| 119425 | 2025-11-19 6:59 | 2025-11-20 13:13 | MySQL Server: Optimizer | Can't repeat (69 days) | S3 | 8.0.22 | Any | Any | mysqld crash in JOIN::make_sum_func_list() |
| 119421 | 2025-11-18 12:51 | 2025-12-03 11:36 | MySQL Server: Optimizer | Duplicate (56 days) | S5 | 8.4 | Linux | Any | Regression in 8.4 vs 8.0 where an index with a second column being a prefix value is not used for a range scan |
| 119416 | 2025-11-18 6:11 | 2025-12-07 21:23 | MySQL Server: Optimizer | Verified (52 days) | S3 | 9.4.0 | Any | Any | Incorrect in Subquery on MEMORY Engine |
| 119415 | 2025-11-18 6:07 | 2025-12-07 21:17 | MySQL Server: Optimizer | Verified (52 days) | S3 | 9.4.0 | Any | Any | Incorrect IN Subquery on ARCHIVE Engine |
| 119414 | 2025-11-17 23:55 | 2025-12-07 21:11 | MySQL Server: Optimizer | Not a Bug (52 days) | S3 | mysql Ver 9.4. | MacOS | Any | 0.0 is treated differently |
| 119413 | 2025-11-17 23:52 | 2025-12-07 21:06 | MySQL Server: Optimizer | Verified (52 days) | S3 | mysql Ver 9.4. | Any | Any | Intersection order |
| 119409 | 2025-11-17 9:32 | 2025-11-17 9:32 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | Update fails to update data consistently after locking is released |
| 119407 | 2025-11-17 6:17 | 2025-12-07 21:04 | MySQL Server: Locking | Open (70 days) | S3 | 8.0.41 | Any | Any | Isolation Level Settings |
| 119405 | 2025-11-17 3:12 | 2025-12-07 21:03 | MySQL Server: Locking | Open | S3 | 8.0.41 | Any | Any | Set @@transaction_isolation does not take effect. |
| 119403 | 2025-11-15 9:38 | 2025-12-07 20:55 | MySQL Server: Optimizer | Verified (52 days) | S3 | 9.4.0 | Any | Any | INTERSECT operation incorrectly gets rows with NULL and non-NULL combination |
| 119402 | 2025-11-15 8:39 | 2025-12-07 20:50 | MySQL Server: Optimizer | Verified (52 days) | S3 | 9.4.0 | Any | Any | EXCEPT operation incorrectly removes rows with NULL and non-NULL combination when subtracting sets with NULL values |
| 119401 | 2025-11-15 8:08 | 2025-12-08 8:01 | MySQL Server: Optimizer | Can't repeat (51 days) | S3 | 9.4.0 | Any | Any | rows become less after adding an or condition |
| 119400 | 2025-11-15 7:20 | 2025-12-07 20:08 | MySQL Server: Optimizer | Verified (52 days) | S3 | 8.0 | Any | Any | rows become less after changing join clause |
| 119399 | 2025-11-15 7:00 | 2025-12-07 19:31 | MySQL Server: Optimizer | Verified (52 days) | S3 | 9.4.0 | Any | Any | Column name change after adding DISTINCT |
| 119398 | 2025-11-15 6:56 | 2025-12-07 19:21 | MySQL Server: Optimizer | Verified (52 days) | S3 | 9.4.0 | Any | Any | rows become less after removing Except clause |
| 119396 | 2025-11-14 10:58 | 2025-11-14 15:12 | MySQL Server: InnoDB storage engine | Open (75 days) | S1 | 8.0.40 | Any | Any | Increase in undo log size , slower purging and no truncation even after restart |
| 119395 | 2025-11-14 9:20 | 2025-11-15 12:34 | MySQL Server: InnoDB storage engine | Open | S3 | 8.4 | Any | Any | WL #12527 may cause performance jitter under heavy write workloads |
| 119394 | 2025-11-14 9:02 | 2025-12-14 12:06 | MySQL Server: Optimizer | Open (45 days) | S3 | Any | Any | Join order specified in the hint is different, the query results are incorrect. | |
| 119393 | 2025-11-14 7:54 | 2025-11-14 8:07 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0 | Any | Any | Wrong db_name asing for acquire_uncached_table() |
| 119386 | 2025-11-13 11:44 | 2026-01-15 12:35 | MySQL Server: Optimizer | Verified (13 days) | S1 | 9.4.0 | Any | Any | unexpected error "Can't write; duplicate key in table '/tmp/#sql1_372_1'" |
| 119385 | 2025-11-13 9:41 | 2025-12-06 22:51 | MySQL Server: Optimizer | Verified (53 days) | S3 | 8.0.41 | Any | Any | After replacing the expressions inside BETWEEN ... AND with constants, the results become inconsistent. |
| 119381 | 2025-11-13 8:14 | 2026-01-13 19:17 | MySQL Server: DML | Verified (15 days) | S2 | 8.0.43, 9.4.0 | Any | Any | Contribution by Tencent: Duplicate auto-increment values happened with partitioned tables and uk conflict |
| 119379 | 2025-11-13 0:42 | 2025-11-13 0:42 | MySQL Server: DDL | Open | S3 | 8.0.41 | Linux (AlmaLinux 9.6) | x86 (XEON) | `AUTO_INCREMENT value ignored after CREATE TABLE in MySQL 8.0.41 (starts from 1 instead of specified value)` |
| 119370 | 2025-11-12 10:07 | 2025-12-06 22:40 | MySQL Server: Optimizer | Verified (53 days) | S3 | 9.4.0 8.4.6 | Any | Any | FLOAT Value Returned by CASE Statement Evaluates Incorrectly in Bitwise Operation |
| 119367 | 2025-11-12 6:18 | 2025-12-06 22:33 | MySQL Server: DML | Not a Bug (53 days) | S3 | 9.1.0 | Any | Any | query function coalesce occur error 'Cannot convert string 'xxx from binary to utf8mb4' |
| 119365 | 2025-11-12 3:14 | 2025-12-06 22:25 | MySQL Server: Optimizer | Verified (53 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect NOT IN Evaluation for NULL on Indexed TEXT Column |
| 119364 | 2025-11-12 3:01 | 2025-12-06 22:14 | MySQL Server: Optimizer | Verified (53 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect Evaluation of = ANY Subquery with NULL on Indexed DECIMAL Column |
| 119363 | 2025-11-12 2:52 | 2025-11-12 3:10 | MySQL Server: Optimizer | Verified (77 days) | S3 | 9.4.0 8.4.6 | Any | Any | Complex WHERE Expression on Indexed FLOAT Column Evaluates Incorrectly |
| 119360 | 2025-11-11 8:42 | 2025-11-11 8:42 | MySQL Server: Optimizer | Open | S3 | 8.0.41 | Any | Any | Result inconsistency due to sorting in temporary tables |
| 119356 | 2025-11-10 16:20 | 2025-12-06 22:04 | MySQL Server: Charsets | Verified (53 days) | S3 | Any | Any | Contribution: Fix NUL characters in FORMAT() output | |
| 119355 | 2025-11-10 16:15 | 2025-12-06 22:02 | MySQL Server: Optimizer | Verified (53 days) | S3 | 9.4.0 8.4.6 | Any | Any | BETWEEN ... AND NULL evaluates incorrectly with bitwise shift |
| 119354 | 2025-11-10 15:51 | 2025-12-06 21:52 | MySQL Server: Optimizer | Verified (53 days) | S3 | 9.4.0 8.4.6 | Any | Any | IN subquery evaluates incorrectly when using IFNULL and CAST AS DATETIME |
| 119353 | 2025-11-10 14:30 | 2025-12-06 21:38 | MySQL Server: Optimizer | Open | S3 | 9.4.0 | Any | Any | Column Value change after removing DISTINCT in query |
| 119352 | 2025-11-10 13:11 | 2025-12-06 21:37 | MySQL Server: Optimizer | Open | S3 | 9.4.0 | Any | Any | row number become less after changing where clause |
| 119350 | 2025-11-10 12:14 | 2025-11-20 13:15 | MySQL Server: Optimizer | Verified (69 days) | S3 | 8.0 | Any | Any | Column name change after changing having clause |
| 119349 | 2025-11-10 12:06 | 2025-11-20 13:05 | MySQL Server: Optimizer | Verified (69 days) | S3 | 9.4.0 | Any | Any | Incorrect String Comparison with MyISAM BIT Column in IN Subquery |
| 119348 | 2025-11-10 11:01 | 2025-11-20 12:58 | MySQL Server: Optimizer | Verified (69 days) | S3 | 8.0 | Any | Any | Incorrect row number after changing having clause |
| 119347 | 2025-11-10 10:43 | 2025-11-20 12:48 | MySQL Server: Optimizer | Verified (69 days) | S3 | 8.0 | Any | Any | IN predicate incorrectly evaluates RADIANS() and TINYINT with key |
| 119346 | 2025-11-10 9:43 | 2025-11-20 12:40 | MySQL Server: Optimizer | Verified (69 days) | S3 | 8.0 | Any | Any | CASE expression evaluates incorrectly |
| 119345 | 2025-11-10 9:21 | 2025-11-20 11:33 | MySQL Server: Optimizer | Verified (69 days) | S3 | 8.0 | Any | Any | Presence of UNIQUE index on INT column causes inconsistent results for IF with ANY subquery |
| 119344 | 2025-11-10 8:47 | 2025-11-12 3:04 | MySQL Server: Optimizer | Verified (77 days) | S3 | 9.4.0 | Any | Any | Floating-point precision loss happen after changing UNION to UNION ALL |
| 119343 | 2025-11-10 8:40 | 2025-12-22 20:51 | MySQL Server: Optimizer | Verified (69 days) | S3 | 8.0 | Any | Any | NOT BETWEEN evaluates incorrectlywhen FROM_UNIXTIME operates on a FLOAT column |
| 119342 | 2025-11-10 8:26 | 2025-11-11 8:10 | MySQL Server: Optimizer | Verified (78 days) | S3 | 9.4.0 | Any | Any | Bits value change after changing UNION to UNION ALL |
| 119341 | 2025-11-10 8:24 | 2025-11-11 7:56 | MySQL Server: Optimizer | Verified (78 days) | S3 | 9.4.0 | Any | Any | ALL subquery evaluates incorrectly in SELECT list when comparing against a BIT column |
| 119339 | 2025-11-08 17:27 | 2025-11-11 7:31 | MySQL Server: Optimizer | Verified (78 days) | S3 | 8.0.41 | Any | Any | The results are different after extracting the value of the COALESCE function |
| 119336 | 2025-11-07 18:21 | 2025-11-07 18:49 | MySQL Server: Command-line Clients | Open (82 days) | S3 | 5.7 8.0 8.4 | Any | Any | extra whitespace in grant statement results in syntax error |
| 119329 | 2025-11-07 8:13 | 2025-11-11 14:02 | MySQL Server: Optimizer | Verified (82 days) | S3 | 8.0.44 | Any | Any | Column name unexpectedly change after changing COUNT to COUNT(DISTINCT) |
| 119326 | 2025-11-07 7:40 | 2025-11-07 9:07 | MySQL Server: Optimizer | Verified (82 days) | S3 | 8.0.41 | Any | Any | Using the COALESCE function, two opposite conditions return the same result. |
| 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 |
| 119323 | 2025-11-07 5:59 | 2025-11-07 7:26 | MySQL Server: Optimizer | Verified (82 days) | S3 | 9.4.0 | Any | Any | row number become less after changing COUNT(DISTINCT) to COUNT |
| 119322 | 2025-11-07 4:58 | 2025-11-07 7:29 | MySQL Server: Optimizer | Verified (82 days) | S3 | 9.4.0 | Any | Any | Unexpected None after adding a window column |
| 119321 | 2025-11-07 4:35 | 2025-11-07 7:37 | MySQL Server: Optimizer | Verified (82 days) | S3 | 9.4.0 | Any | Any | Unexpected None after changing SUM to SUM (x*2) |
| 119313 | 2025-11-06 3:03 | 2025-12-06 21:22 | MySQL Server: Optimizer | Verified (53 days) | S3 | 8.0.41 | Any | Any | BETWEEN clause returns incorrect results when comparing numeric literal with DATETIME columns |
| 119312 | 2025-11-05 17:30 | 2026-01-13 11:33 | MySQL Server: Replication | Open | S3 | 8.4.x | Any | Any | `start replica` command adds an invalid record to mysql.slave_master_info |
| 119309 | 2025-11-05 13:37 | 2026-01-20 10:16 | MySQL Server: Partitions | Verified (8 days) | S3 | 8.0.42 | Any | Any | An insert prepared statement fails to write across partitions |
| 119306 | 2025-11-05 7:02 | 2025-11-06 5:34 | MySQL Server: Optimizer | Verified (83 days) | S3 | 8.0, 9.5 | Any | Any | The EXPLAIN plan may be inconsistent with the actual execution. |
| 119305 | 2025-11-05 4:02 | 2025-12-16 13:55 | MySQL Server: Optimizer | Verified (43 days) | S3 | 8.0.41 | Linux | x86 | The query results of enabling and disabling materialization are inconsistent. |
| 119304 | 2025-11-05 2:08 | 2026-01-15 10:31 | MySQL Server: Replication | Open (84 days) | S3 | 5.7，8.0 | Any | Any | SQL_LOAD-xxxx file exists when the SQL thread checks permissions, causing the SQL thread fail to start |
| 119303 | 2025-11-05 1:49 | 2025-11-05 5:00 | MySQL Server: DML | Verified (84 days) | S3 | 8.0.41 | Any | Any | The query is normal without using the histogram, but an error occurs when using the histogram |
| 119300 | 2025-11-04 10:46 | 2025-11-04 10:56 | MySQL Server: InnoDB storage engine | Open (85 days) | S3 | 8.0.44 | Any | Any | Debug assertion failure: field.field_no < dict_index_get_n_fields(index) |
| 119290 | 2025-11-02 15:06 | 2025-11-07 7:43 | MySQL Server: InnoDB storage engine | Open (82 days) | S2 | 9.3.0, 9.5.0 | Any | Any | SELECT statement is affected by concurrent transaction under Read Uncommitted |
| 119287 | 2025-11-01 10:08 | 2025-11-04 21:01 | MySQL Server: Optimizer | Verified (85 days) | S3 | 8.0.41 | Any | Any | Decimal Precision Mismatch in UNION Query with CONCAT Function |
| 119286 | 2025-11-01 9:57 | 2025-11-06 9:40 | MySQL Server: DML | Duplicate (85 days) | S3 | 8.0.41 | Any | Any | Query Results Incorrect Due to Indexed String Field |
| 119285 | 2025-11-01 6:16 | 2025-11-01 6:25 | MySQL Server: InnoDB storage engine | Open (88 days) | S5 | 8.0.44 | Any | Any | resue read-view for read_only mode |
| 119281 | 2025-10-31 14:10 | 2025-12-02 1:00 | MySQL Server: Optimizer | No Feedback (58 days) | S3 | mysql:8.0.41 | Any | Any | The crash occured |
| 119280 | 2025-10-31 11:55 | 2025-12-04 2:27 | MySQL Server: InnoDB storage engine | Open (55 days) | S2 | 9.5.0 | Any | Any | INSTANT ADD succeeds even when the size of a row crosses row_size_limit |
| 119279 | 2025-10-31 10:48 | 2025-10-31 10:48 | MySQL Server: Tests | Open | S3 | 8.4.6 | Any | Any | The default value of innodb_read_io_threads uses too many system resources with mysql-test.run.pl |
| 119276 | 2025-10-31 6:05 | 2026-01-13 11:34 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.44 | Any | Any | ALTER TABLE ANALYZE PARTITION statement causes incorrect results in the mysql.table_table_stats |
| 119273 | 2025-10-30 14:14 | 2026-01-15 10:29 | MySQL Server: InnoDB storage engine | Open (90 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" |
| 119270 | 2025-10-30 9:12 | 2025-10-30 16:03 | MySQL Server: Replication | Open | S3 | MySQL8.0,5.7 | Any | Any | Single-statement transactions can cause latency spikes on the replica |
| Showing all 227 (Edit, Save, CSV, Feed) |
