Showing all 158 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
118797 | 2025-08-07 2:08 | 2025-08-07 9:17 | MySQL Server: Replication | Verified | S2 | 8.4, 8.4.6, 9.4.0 | Any | Any | Contribution by Tencent: previous gtids may loss xa commit/rollback gtids |
118788 | 2025-08-06 9:33 | 2025-08-06 13:33 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0.41, 8.0.43 | Linux | x86 | When two tables are joined, the execution results are different in different join order. |
118785 | 2025-08-06 5:55 | 2025-08-06 14:31 | MySQL Server: Documentation | Closed (1 day) | S3 | 8.4 | Any | Any | Did 8.4.6 and 8.4.7 get released simultaneously on 2025.7.22? |
118766 | 2025-08-01 9:11 | 2025-08-01 11:03 | MySQL Server: Documentation | Verified (6 days) | S3 | 8.0 | Any | Any | default row_format should be DYNAMIC |
118765 | 2025-08-01 2:56 | 2025-08-01 5:26 | MySQL Server: DML | Verified (6 days) | S3 | 8.0, 9.0, 8.4.6, 8.0.43 | Any | Any | Substring_index with negative index returns inconsistent results across different character sets |
118755 | 2025-07-31 2:04 | 2025-07-31 7:00 | MySQL Server: DML | Verified (7 days) | S3 | 8.0.36, 8.0.43, 8.4.6 | Windows | Any | Incorrect lowercasing of word-final Greek capital Sigma (Σ) |
118750 | 2025-07-30 3:33 | 2025-07-30 5:51 | MySQL Server: Prepared statements | Analyzing (8 days) | S3 | 9.3.0 | Any | Any | binary comparison has different results in prepared statement and normal SELECT query |
118749 | 2025-07-30 2:41 | 2025-07-30 11:57 | MySQL Server: Optimizer | Duplicate (8 days) | S3 | 9.3.0 | Any | Any | internal_tmp_mem_storage_engine=memory make the query generate different result on -0 and 0 |
118729 | 2025-07-28 13:17 | 2025-07-29 6:37 | MySQL Server: Optimizer | Verified (9 days) | S3 | 8.4.4 (Any), 8.0.43, 8.4.6, 9.4.0 | Any | Any | Select Query is showing wrong column name alias from sub-query |
118724 | 2025-07-26 12:08 | 2025-07-28 13:09 | MySQL Server: Performance Schema | Analyzing (10 days) | S5 | 8.0.42 | Any | Any | optimzie for performance_schema |
118723 | 2025-07-26 11:54 | 2025-07-28 4:29 | MySQL Server: InnoDB storage engine | Verified (10 days) | S5 | 8.0.42 | Any | Any | optimize for innodb insert |
118721 | 2025-07-26 9:40 | 2025-07-27 10:44 | MySQL Server: Documentation | Not a Bug (11 days) | S3 | 8.0, 8.4, 9.x | Any | Any | Improve documentation for CREATE / ALTER USER syntax related to comments and user_attributes |
118710 | 2025-07-23 12:08 | 2025-07-23 12:42 | MySQL Server: Optimizer | Verified (15 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 |
118705 | 2025-07-23 8:06 | 2025-07-25 6:12 | MySQL Server: InnoDB storage engine | Verified (13 days) | S2 | 8.0 | Any | Any | when call que_eval_sql, may crash. |
118700 | 2025-07-22 12:55 | 2025-07-24 12:45 | MySQL Server: Replication | Need Feedback (14 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. |
118695 | 2025-07-22 7:11 | 2025-07-23 7:33 | MySQL Server: InnoDB storage engine | Verified (15 days) | S3 | 8.0 | Any | Any | This if condition seems to be useless in btr0cur.cc:1398 |
118694 | 2025-07-22 7:03 | 2025-07-22 11:45 | MySQL Server: DML | Verified (16 days) | S3 | 8.0.41 5.7, 8.0.42 | Any | Any | Item_func_between deal with decimel different from other methods |
118693 | 2025-07-22 5:52 | 2025-07-22 6:34 | MySQL Server: InnoDB storage engine | Verified (16 days) | S3 | 8.0.42 | Any | Any | Increasing length of varchar field should be inplace. |
118689 | 2025-07-21 11:33 | 2025-08-04 9:43 | MySQL Server: Optimizer | Not a Bug (3 days) | S2 | 9.2.0, 8.0.42, 8.4.5, 9.3.0 | Linux | Any | Inconsistent data returns when using INTERESECT operator |
118684 | 2025-07-18 14:54 | 2025-07-21 6:07 | MySQL Server: Optimizer | Verified (17 days) | S2 | 9.2.0, 8.0.42, 8.4.5 | Linux | Any | Inconsistent rows are returned |
118682 | 2025-07-18 3:52 | 2025-07-24 6:33 | MySQL Server: Options | Verified (14 days) | S2 | 8.0, 8.0.42 | Any | Any | connection_memory_limit and global_connection_memory_limit don't work |
118681 | 2025-07-18 2:54 | 2025-07-18 5:22 | MySQL Server: InnoDB storage engine | Verified (20 days) | S5 | 8.0.42 | Any | Any | Reduce the locking scope of dict_sys_mutex in dict_stats_drop_table |
118672 | 2025-07-16 9:31 | 2025-07-21 12:31 | MySQL Server: DML | Need Feedback (17 days) | S3 | 8.0.41 | Any | Any | do dml sql crash |
118670 | 2025-07-16 9:23 | 2025-07-21 12:37 | MySQL Server: DDL | Need Feedback (17 days) | S3 | 8.0.41 | Any | Any | add partition crash |
118669 | 2025-07-16 5:22 | 2025-07-16 6:46 | MySQL Server: Optimizer | Verified (22 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Issue in applying limit on aggregated data |
118659 | 2025-07-15 7:31 | 2025-07-21 12:37 | MySQL Server: DDL | Need Feedback (17 days) | S3 | 8.0.41 | Linux | Any | doing optimize table crash |
118658 | 2025-07-15 6:11 | 2025-07-15 6:16 | MySQL Server: Data Types | Verified (23 days) | S3 | 9.2.0, 8.0, 8.0.42 | Any | Any | Issue with NULL Detection for DATE-Type Columns in Derived Tables After Derived Merge |
118630 | 2025-07-10 9:05 | 2025-07-23 1:36 | MySQL Server: DML | Not a Bug (15 days) | S3 | 9.3.0 | Any | Any | INSERT IGNORE failed but insert a different value |
118627 | 2025-07-10 7:26 | 2025-07-23 13:04 | MySQL Server: DML | Not a Bug (15 days) | S3 | 8.0.41 | Any | Any | while exexuting prepare statement including 'order by ?', the sort of result set is not right |
118625 | 2025-07-10 3:04 | 2025-08-06 12:47 | MySQL Server: DDL | Duplicate (1 day) | S3 | 9.3.0 | Any | Any | index makes query generate incorrect result |
118624 | 2025-07-10 2:47 | 2025-07-10 8:15 | MySQL Server: InnoDB storage engine | Verified (28 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) |
118621 | 2025-07-09 12:39 | 2025-07-09 14:19 | MySQL Server: Optimizer | Verified (29 days) | S3 | 9.3.0, 8.0.42 | Any | Any | subquery_to_derived optimizer makes query produce incorrect result |
118611 | 2025-07-09 4:40 | 2025-07-09 8:27 | MySQL Server: DDL | Verified (29 days) | S3 | 8.4, 8.0.42 | Linux | Any | Creating an InnoDB table with a CONNECTION clause should not be allowed |
118602 | 2025-07-08 10:26 | 2025-07-08 15:32 | MySQL Server: Replication | Analyzing (30 days) | S2 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.24.04.1) | x86 | SQL Thread cannot be stopped when last error was 1755 |
118601 | 2025-07-08 9:30 | 2025-07-09 8:47 | MySQL Server: Prepared statements | Not a Bug (29 days) | S3 | 8.0.42, 8.4.5 | Any | Any | Inconstant type between constants in prepare statement and SELECT statement |
118595 | 2025-07-07 15:16 | 2025-07-10 7:19 | MySQL Server: Prepared statements | Not a Bug (28 days) | S1 | 9.3.0 | Any | Any | NULL are transformed to false in certain expression in prepared statement |
118594 | 2025-07-07 14:16 | 2025-07-07 14:58 | MySQL Server: InnoDB storage engine | Verified (31 days) | S2 | 8.0.42 | Any | Any | In-place ALTER TABLE ... ADD FOREIGN KEY can sometimes fails with unwarranted error or even crashes |
118592 | 2025-07-07 12:12 | 2025-07-10 6:53 | MySQL Server: Prepared statements | Duplicate (28 days) | S1 | 9.3.0 | Any | Any | Unexpected result of prepared statement |
118591 | 2025-07-07 11:28 | 2025-07-10 7:11 | MySQL Server: Data Types | Duplicate (28 days) | S1 | 9.3.0 | Any | Any | empty string parse to 0 in SET statement, which is different from that in the SELECT query |
118585 | 2025-07-03 16:35 | 2025-07-04 6:42 | MySQL Server: Optimizer | Verified (34 days) | S5 | 8.0.39, 8.0.42, 8.4.5, 9.3.0 | Ubuntu (Ubuntu 20.04.2) | Any | system variable "range_alloc_block_size" arouse different execution plan |
118575 | 2025-07-02 11:06 | 2025-07-02 14:38 | MySQL Server: DML | Not a Bug (36 days) | S3 | 8.0.42 | Any | Any | Unexpected NULL Match in <=> Comparison When Subquery Returns No Rows |
118571 | 2025-07-02 7:27 | 2025-08-06 12:50 | MySQL Server: DML | Duplicate (1 day) | S3 | 8.0.41 | Any | Any | using index lookup, the query return a wrong result; |
118570 | 2025-07-02 2:29 | 2025-07-03 9:32 | MySQL Server: DML | Verified (36 days) | S5 | 8.0.42 | Linux (22.04) | x86 | Performance regression occurs with INSERT statements after c17d86b |
118560 | 2025-06-30 11:58 | 2025-06-30 13:01 | MySQL Server: DDL | Verified (38 days) | S3 | 8.0, 8.4 | Any | Any | drop full text can not instant |
118556 | 2025-06-29 19:07 | 2025-06-30 8:14 | MySQL Server: DML | Verified (38 days) | S3 | 9.3.0 | Ubuntu | x86 | Queries on tables with same data return different results |
118555 | 2025-06-29 18:55 | 2025-06-30 8:09 | MySQL Server: DML | Verified (38 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant results in tables containing NULL values |
118554 | 2025-06-29 18:42 | 2025-06-30 8:05 | MySQL Server: DML | Verified (38 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistent results on same tables with different PRIMARY KEY constraint |
118553 | 2025-06-29 18:26 | 2025-06-30 8:03 | MySQL Server: DML | Verified (38 days) | S3 | 9.3.0 | Ubuntu | x86 | SELECT returns different results on tables with same data |
118552 | 2025-06-29 18:14 | 2025-06-30 8:00 | MySQL Server: DML | Verified (38 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant result on tables with same data but different constraints |
118551 | 2025-06-29 17:59 | 2025-06-30 7:42 | MySQL Server: DML | Verified (38 days) | S3 | 9.3.0 | Ubuntu | x86 | Inconsistant result after removing constraints on table |
118548 | 2025-06-28 7:56 | 2025-06-30 6:45 | MySQL Server: Optimizer | Verified (38 days) | S3 | 9.2.0, 9.3.0 | Linux | x86 | A potential bugs in Mysql Server |
118547 | 2025-06-27 17:26 | 2025-06-30 6:36 | MySQL Server: Information schema | Verified (38 days) | S3 | 8.0, 8.4, 8.0.42 | Any | Any | SET DEFAULT (expr) on PK column requires issuing command twice |
118544 | 2025-06-27 14:18 | 2025-06-30 6:43 | MySQL Server: Optimizer | Verified (38 days) | S3 | 9.2.0 , 9.3.0 | Linux | Any | A potential join operator bug |
118542 | 2025-06-27 8:35 | 2025-06-27 8:51 | MySQL Server: Documentation | Verified (41 days) | S3 | 8.0, 8.4 | Any | Any | The table reference in the performance_schema is incomplete |
118541 | 2025-06-27 8:31 | 2025-06-27 13:37 | MySQL Server: Optimizer | Verified (41 days) | S3 | 9.2.0 , 8.0.42 | Linux | Any | Inconsistent Results Between NATURAL JOIN and its Equivalent Form Using EXCEPT ALL with Implicit Type Casting |
118540 | 2025-06-27 7:27 | 2025-06-27 13:36 | MySQL Server: Optimizer | Verified (41 days) | S3 | 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 |
118536 | 2025-06-26 17:55 | 2025-06-27 7:24 | MySQL Server: Optimizer | Analyzing (41 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 |
118535 | 2025-06-26 17:43 | 2025-06-27 19:27 | MySQL Server: FULLTEXT search | Verified (41 days) | S3 | 9.3.0, 8.4.5, 8.0.42 | Ubuntu (25.04 Server) | x86 | Arithmetic operations fail on fulltext-indexed fields inserted with DISABLE KEYS |
118529 | 2025-06-26 9:50 | 2025-06-26 12:18 | MySQL Server: Options | Verified (42 days) | S3 | 8,9 | Any | Any | 'init_connect' not re-executed after 'COM_RESET_CONNECTION' or 'COM_CHANGE_USER' |
118516 | 2025-06-24 10:42 | 2025-07-03 18:36 | MySQL Server: InnoDB storage engine | Verified (35 days) | S3 | 8.0.39 | Any | Any | Unexpected blocked statement when different select statements are executed |
118515 | 2025-06-24 9:08 | 2025-07-01 4:35 | MySQL Server: InnoDB storage engine | Verified (38 days) | S2 | 8.4, 8.4.5 | Any | Any | Contribution by Tencent: trx_cleanup_at_db_startup did not clean up trx_sys->shards |
118512 | 2025-06-24 7:52 | 2025-06-25 8:13 | MySQL Server: Optimizer | Verified (44 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | The missing semi join condition causes incorrect result |
118510 | 2025-06-23 20:09 | 2025-07-01 12:50 | MySQL Server: FULLTEXT search | Verified (37 days) | S2 | 8.0.39 | Any | Any | InnoDB Match Against does not work properly with utf8mb4_0900_as_ci |
118499 | 2025-06-23 9:20 | 2025-06-26 1:47 | MySQL Server: Command-line Clients | Analyzing (42 days) | S2 | mysql-8.0.32 | Linux (centos7.9) | Any | .mylogin.cnf covered the command line |
118497 | 2025-06-23 1:11 | 2025-06-23 4:20 | MySQL Server: DML | Duplicate (45 days) | S3 | 8.0.41 | Any | Any | When inserting floating-point data into JSON type, the query result precision is incorrect. |
118495 | 2025-06-20 7:40 | 2025-06-20 10:32 | MySQL Server: DML | Verified (48 days) | S3 | 8.0.41 | Linux | x86 | The query returned wrong result with l"imit offset" |
118493 | 2025-06-20 6:54 | 2025-06-20 10:38 | MySQL Server: Partitions | Verified (48 days) | S3 | 8.0, 8.0.42 | Any | Any | Subpartitions can not be pruned by conditions derived from equal propagation |
118492 | 2025-06-20 3:07 | 2025-07-01 12:40 | MySQL Server: DML | Can't repeat (37 days) | S3 | 8.0.41, 8.0.42 | Linux | x86 | The result returned by the DIAMETER_TZ function is incorrect. The time after conversion is expected. |
118490 | 2025-06-19 13:00 | 2025-06-20 5:21 | MySQL Server: Optimizer | Verified (48 days) | S3 | master, 8.4 | Any | Any | hypergraph optimizer const folding caused inequivalent for join_cond_optim in Table_ref |
118486 | 2025-06-19 10:07 | 2025-07-14 12:17 | MySQL Server: Optimizer | Duplicate (24 days) | S5 | 8.4.3, 8.4.5, 9.3.0 | Any (AWS RDS) | Any | Index is ignored in case of multiple values in "select" and the length of any one value is more than column length |
118481 | 2025-06-18 20:04 | 2025-08-04 6:05 | MySQL Server: Optimizer | No Feedback (4 days) | S3 | Mysql 8.4.5 | Linux (Amazon Linux (AWS RDS managed)) | Any | MySQL 8.4.5 chooses suboptimal index for UPDATE query, leading to deadlocks and performance degradation |
118476 | 2025-06-18 8:45 | 2025-07-02 14:47 | MySQL Server: DDL | Verified (50 days) | S2 | 8.0, 8.4 | Red Hat | x86 | Unable to create partition with name '1e3fRQM2GhI' |
118475 | 2025-06-18 7:58 | 2025-06-18 8:40 | MySQL Server: DML | Verified (50 days) | S3 | 8.0.41, 8.4.5 | Any | Any | When the IF function is invoked to replace the specified column name, the returned results are inconsistent. |
118469 | 2025-06-17 9:38 | 2025-06-17 10:33 | MySQL Server: Documentation | Verified (51 days) | S3 | 9.3 | Any | Any | Connection attributes for Connector/NET are incomplete/incorrect |
118465 | 2025-06-17 7:42 | 2025-06-17 9:02 | MySQL Server: DML | Duplicate (51 days) | S3 | 8.0.41 | Any | Any | Inserting into a float value exceeding the precision, using IF function and using the column return different result. |
118464 | 2025-06-17 7:24 | 2025-06-17 9:29 | MySQL Server: DML | Analyzing (51 days) | S3 | 8.0.41 | Any | Any | Inserting into a float value exceeding the precision, using IF function and using the column return different result. |
118462 | 2025-06-17 2:56 | 2025-07-01 14:09 | MySQL Server: Replication | Can't repeat (37 days) | S3 | 8.0.39 | Red Hat (Rocky Linux 8.10) | x86 (AMD EPYC 7R32) | Executed SQL on replica is different from source |
118455 | 2025-06-16 9:52 | 2025-06-17 12:05 | MySQL Server: DML | Not a Bug (51 days) | S3 | 8.0.41 | Linux | x86 | Cannot query JSON type data using BETWEEN '{"key1": 1}' AND '{"key1": 1}' |
118447 | 2025-06-13 22:52 | 2025-06-16 5:30 | MySQL Server: Security: Privileges | Verified (52 days) | S3 | 8.4 | Any | Any | MySQL 8.4 always uses caching_sha2_password in the initial connection handshake |
118422 | 2025-06-12 2:54 | 2025-06-12 23:46 | MySQL Server: InnoDB storage engine | Can't repeat (56 days) | S2 | 8.0.41 | Any | Any | Assertion failure happens in page_is_comp(get_block->frame) == page_is_comp(page) |
118412 | 2025-06-10 23:24 | 2025-07-01 9:18 | MySQL Server: Replication | Verified (37 days) | S3 | 8.0.41, 8.0.42 | Any | Any | DML succeeds on Semi-sync without Replicas if Source is stopped |
118411 | 2025-06-10 15:52 | 2025-07-21 11:44 | MySQL Server: InnoDB storage engine | Verified (17 days) | S2 | 8.0.37, 8.0.42 | CentOS | x86 | Performance degradation in write workload after rebuilding table with row_format=compressed |
118403 | 2025-06-09 17:10 | 2025-06-20 10:13 | MySQL Server: InnoDB storage engine | Verified (48 days) | S3 | 8.0.37, 8.0.42 | Any | Any | innodb_fill_factor is not honored for InnoDB Compressed Tables |
118402 | 2025-06-09 13:38 | 2025-06-09 14:12 | MySQL Server: DML | Duplicate (59 days) | S3 | 8.0.41 | Linux | x86 | When innodb_buffer_pool_size is set a small value , the update value is abnormal. |
118401 | 2025-06-09 13:37 | 2025-06-10 6:32 | MySQL Server: DML | Verified (59 days) | S3 | 8.0.41 | Linux | x86 | When innodb_buffer_pool_size is set a small value , the update value is abnormal. |
118400 | 2025-06-09 13:34 | 2025-07-24 12:28 | MySQL Server: DML | Verified (59 days) | S3 | 8.0.41 | Linux | x86 | ERROR 3854 (HY000): Cannot convert string '\xF0\x9F\x98\xA6\xF0\x9F...' from utf8mb4 to latin1 |
118399 | 2025-06-09 12:35 | 2025-06-09 12:46 | MySQL Server: DML | Verified (59 days) | S3 | 8.0.41 | Linux | x86 | multijoin and related subqueries are used, the query result is incorrect during optimizer_switch="derived_merge=on" |
118398 | 2025-06-09 8:00 | 2025-06-11 12:40 | MySQL Server: DML | Verified (57 days) | S3 | 8.0.41 | Any | Any | Using temporary with avg cause wrong result |
118394 | 2025-06-09 2:04 | 2025-06-09 5:57 | MySQL Server: DML | Analyzing (59 days) | S3 | 8.0.41 | Any | Any | while (NOT XX NOT IN ()) return 0, the query with where (NOT XX NOT IN ()) returns a wrong result. |
118393 | 2025-06-09 1:36 | 2025-06-09 5:57 | MySQL Server: DML | Analyzing (59 days) | S3 | 8.0.41 | Any | Any | while the having subquery return NULL actually, the query using this having query returns a wrong result. |
118391 | 2025-06-08 16:43 | 2025-06-10 12:23 | MySQL Server: DML | Verified (59 days) | S3 | 8.4.2, 8.0 | Any | Any | Inconsistent BIGINT overflow behavior with unary minus operator in multiplication |
118390 | 2025-06-08 8:04 | 2025-06-10 11:11 | MySQL Server: DML | Not a Bug (58 days) | S3 | 8.0.41 | Linux | x86 | When the time type is compared with the datetime type, the returned result is error |
118375 | 2025-06-06 3:41 | 2025-06-06 3:58 | MySQL Server: DML | Analyzing (62 days) | S3 | 8.0.41 | Any | Any | while (NOT ((t0.c1) >= (t1.c2))) returns 1 actually, the query return an empty result set. |
118369 | 2025-06-05 11:21 | 2025-06-05 13:08 | MySQL Server: DML | Analyzing (63 days) | S3 | 8.0.41 | Any | Any | "having column" and "having MIN(column)" return different result.something wrong during Aggregate using temporary table |
118363 | 2025-06-04 18:00 | 2025-06-16 12:33 | MySQL Server: InnoDB storage engine | Verified (57 days) | S3 | mysql-8.0.41 | Any | Any | Another Potential Optimization in row_ins_sec_index_entry_low() |
118359 | 2025-06-04 13:43 | 2025-06-16 12:33 | MySQL Server: InnoDB storage engine | Verified (57 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 |
118358 | 2025-06-04 12:04 | 2025-07-13 10:14 | MySQL Server: InnoDB storage engine | Verified (34 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | Startup without Signs of Progress when Rolling-Back Big Transaction. |
118356 | 2025-06-04 11:58 | 2025-07-13 10:29 | MySQL Server: Replication | Verified (57 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | MySQL attempts committing transaction not fitting on disk, then crashes. |
118355 | 2025-06-04 7:41 | 2025-06-10 13:59 | MySQL Server: InnoDB Plugin storage engine | Verified (58 days) | S3 | 8.0.42 | Any | Any | Temporary file write failure when creating an index |
118352 | 2025-06-04 4:38 | 2025-06-04 8:51 | MySQL Server: Charsets | Verified (64 days) | S3 | 8.0, 8.4 | Any | Any | Illegal mix of collations when modify collation_connection |
118351 | 2025-06-04 2:24 | 2025-06-04 6:34 | MySQL Server: DML | Verified (64 days) | S3 | 8.0.41 | Linux | x86 | When Backward index scan is used for query SQL statements, the returned result is incorrect. |
118350 | 2025-06-04 2:03 | 2025-06-04 6:32 | MySQL Server: Optimizer | Verified (64 days) | S3 | 9.x | Any | Any | Contribution: Adding fuzz directory and modifications to support it. |
118349 | 2025-06-04 2:03 | 2025-06-04 19:16 | MySQL Server: Optimizer | Verified (64 days) | S3 | 9.x | Any | Any | Contribution: fuzz: parse_sql target |
118348 | 2025-06-04 1:52 | 2025-06-04 11:35 | MySQL Server: DML | Duplicate (64 days) | S3 | 8.0.41 | Any | Any | using force index(i0) and ignore index(i0) for the same query, the result set changed |
118347 | 2025-06-03 17:23 | 2025-07-12 1:00 | MySQL Server: DDL | No Feedback (27 days) | S3 | 8.4.5 | Any | Any | 8.4.5 functions in constraints, partitions, or virtual columns may have failed |
118336 | 2025-06-03 8:24 | 2025-06-03 8:30 | MySQL Server: DML | Analyzing (65 days) | S3 | 8.0.41 | Any | Any | after adding a having clause equivalent to "having 1", the returned result set is wrong |
118335 | 2025-06-03 7:50 | 2025-07-07 14:05 | MySQL Server: InnoDB storage engine | Verified (31 days) | S5 | 9.3.0 | Any | Any | drop big table affect performance when general space used |
118322 | 2025-06-01 4:47 | 2025-07-20 1:00 | MySQL Server: Replication | No Feedback (19 days) | S2 | 8.0.20 | Any | x86 | Result of `show master status` is not correct !!! |
118320 | 2025-05-31 1:14 | 2025-06-16 12:33 | MySQL Server: Command-line Clients | Verified (56 days) | S2 | 8.0.41, 8.4.5 | Any | Any | Invalid UTF-8 bytes can be returned by SHOW PROCESSLIST |
118313 | 2025-05-30 9:17 | 2025-05-30 10:19 | MySQL Server: Optimizer | Verified (69 days) | S3 | 8.0.41, 8.0.42, 8.4.5, 9.3.0 | Any | Any | The query result is incorrect. |
118312 | 2025-05-30 8:12 | 2025-05-30 10:32 | MySQL Server: DML | Verified (69 days) | S2 | 8.0.42, 8.4.5, 9.3.0 | Any | Any | Inconsistent results when evaluating `EXCEPT` or `INTERSECT` operations involving `NULL` |
118310 | 2025-05-30 3:36 | 2025-05-30 4:34 | MySQL Server: DML | Analyzing (69 days) | S3 | 8.0.41 | Any | Any | a query with a impossile having clause, return wrong results |
118302 | 2025-05-29 16:46 | 2025-05-30 4:26 | MySQL Server: InnoDB storage engine | Verified (69 days) | S3 | 9.0.0, 9.3.0 | Any | Any | Contribution: Adding \'sb\' instruction to spin_delay() for ARM v8.5 onward |
118299 | 2025-05-29 6:57 | 2025-05-29 11:33 | MySQL Server: InnoDB storage engine | Verified (70 days) | S2 | 8.0.42, 8.4.5 | Any | Any | Multi-valued Index on Composite Key Returns Incomplete Results for Rows with Empty JSON Array('[]') |
118298 | 2025-05-29 2:46 | 2025-05-29 5:03 | MySQL Server: DML | Analyzing (70 days) | S3 | 8.0.41 | Any | Any | "(t1.c4)<-(-1.7976931348623157E308)" and "(t1.c4)<(1.7976931348623157E308)" in where clause return different results |
118297 | 2025-05-29 2:39 | 2025-05-29 12:53 | MySQL Server: Security: Privileges | Verified (70 days) | S3 | 8.0.42, 8.4.5 | Any | Any | password expire and password expire interval when create user is not both work |
118296 | 2025-05-29 2:32 | 2025-05-29 6:03 | MySQL Server: DML | Verified (70 days) | S3 | 8.0.41 | Linux | x86 | When join_buffer_size is set to a different value, the query returns different results. |
118281 | 2025-05-27 15:24 | 2025-05-28 4:42 | MySQL Server: InnoDB storage engine | Verified (71 days) | S3 | 9.3.0 | Any | Any | Contribution: Fix incorrect byte size in mlog read_1_bytes comment |
118278 | 2025-05-27 8:29 | 2025-05-27 9:56 | MySQL Server: DML | Analyzing (72 days) | S3 | 8.0.41 | Any | Any | two query SQL statements filling with opposite semantics in the where clause, result same result |
118277 | 2025-05-27 8:02 | 2025-05-27 8:08 | MySQL Server: DML | Analyzing (72 days) | S3 | 8.0.41 | Any | Any | When a constant value is replaced by the IFNULL(NULL, CONST_VALUE) function, the sql returns different value; |
118269 | 2025-05-26 9:41 | 2025-05-26 12:29 | MySQL Server: Optimizer | Closed (73 days) | S2 | Any | Any | The result of anti disk hash join is wrong | |
118268 | 2025-05-26 7:47 | 2025-05-27 3:30 | MySQL Server: DML | Analyzing (72 days) | S3 | 8.0.41 | Any | Any | The returned results of two queries with the same semantics are inconsistent. |
118266 | 2025-05-26 2:29 | 2025-05-30 7:03 | MySQL Server: Options | Not a Bug (69 days) | S3 | 8.0 | Any | Any | We can't set some session variable even have super privilege |
118265 | 2025-05-25 23:12 | 2025-07-09 15:42 | MySQL Server: InnoDB storage engine | Verified (51 days) | S1 | 9.3.0 | MacOS (15.4.1 (24E263)) | x86 (Quad-Core Intel Core i7) | mysqld hangs durning startup |
118264 | 2025-05-25 15:04 | 2025-08-06 4:58 | MySQL Server: Optimizer | Verified (1 day) | S5 | 9.3.0 | Ubuntu | Any | Performance bug in SEMI JOIN with empty tables |
118252 | 2025-05-22 12:28 | 2025-06-23 1:00 | MySQL Server: DML | No Feedback (46 days) | S3 | 8.0.41 | Any | Any | When the same table is imported to different databases, the results of the same selection are different. |
118249 | 2025-05-22 9:51 | 2025-07-24 12:27 | MySQL Server: Charsets | Duplicate (14 days) | S3 | 8.0.41 | Linux | Any | Cannot convert string '\xF0\x9F\x98\xA6\xF0\x9F...' from utf8mb4 to latin1 |
118247 | 2025-05-22 6:26 | 2025-05-28 8:41 | MySQL Server: Documentation | Verified (71 days) | S3 | 5.7, 8.0, 8.4, 9.0 | Any | Any | (Documentation)The descriptions for "M" parameter not matched in different chapters |
118239 | 2025-05-21 13:05 | 2025-05-29 13:12 | MySQL Server: DML | Verified (70 days) | S3 | 9.3.0 | Ubuntu (22.04) | Any | Logical Inconsistency in MySQL String Comparison with LIKE and NOT LIKE Operators |
118238 | 2025-05-21 10:46 | 2025-06-02 11:31 | MySQL Server: FULLTEXT search | Verified (66 days) | S3 | 9.3.0,8.0.40, 8.0.42 | Any | Any | Ngram parser boolean phrase search fails with CJK punctuation |
118237 | 2025-05-21 8:44 | 2025-05-21 10:48 | MySQL Server: Charsets | Analyzing (78 days) | S3 | 9.2 | Any | Any | Inconsistent results when using prepared statement or session variables |
118233 | 2025-05-20 13:54 | 2025-05-20 15:04 | MySQL Server: DDL | Verified (79 days) | S2 | 8.0.42 | Any | Any | Fixed a bug in the DDL for invisible indexes. |
118230 | 2025-05-20 2:24 | 2025-06-11 11:02 | MySQL Server: DML | Can't repeat (57 days) | S3 | 8.0.41 | Linux | x86 | When innodb_buffer_pool_size is set to 134217728, the update value is abnormal. |
118224 | 2025-05-19 2:46 | 2025-06-03 6:43 | MySQL Server: DML | Analyzing (65 days) | S3 | 8.0.41 | Any | Any | When a constant value is replaced by the LEST function, the sql returns different value; |
118219 | 2025-05-16 18:03 | 2025-05-19 6:56 | MySQL Server: DDL | Analyzing (80 days) | S3 | 8, 9 | Linux | x86 | Name of constraint affects order of deletion, causing on delete/cascade to fail unexpectedly |
118217 | 2025-05-16 16:11 | 2025-05-26 10:17 | MySQL Server: Optimizer | Analyzing (73 days) | S1 | 8.4.5 | Ubuntu | x86 | Issues with the NULLIF function. |
118210 | 2025-05-16 10:15 | 2025-05-18 16:43 | MySQL Server: Replication | Verified (81 days) | S3 | 8.0.42 | Any | Any | Invisible Index Binlog Replay Bugfix |
118206 | 2025-05-15 13:21 | 2025-05-19 21:21 | MySQL Server: Optimizer | Not a Bug (80 days) | S5 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.20.04.1) | Any | The optimizer has chosen a poor execution plan. |
118204 | 2025-05-15 7:41 | 2025-05-19 21:22 | MySQL Server: Optimizer | Not a Bug (80 days) | S5 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.20.04.1) | Any | A poor execution plan can lead to a performance loss of nearly a hundred times. |
118200 | 2025-05-15 1:51 | 2025-05-20 12:12 | MySQL Server: DML | Duplicate (79 days) | S3 | 8.0.41 | Any | Any | The query result using index is different with not used index |
118198 | 2025-05-14 14:16 | 2025-05-19 22:49 | MySQL Server: Optimizer | Verified (80 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | Different intersection orders lead to more than 20,000 times performance gap |
118197 | 2025-05-14 13:50 | 2025-05-19 21:17 | MySQL Server: Optimizer | Duplicate (80 days) | S3 | 9.3.0 | Ubuntu (22.04) | Any | The opposite ON clause intersects and is always an empty set. |
118196 | 2025-05-14 13:42 | 2025-05-19 21:16 | MySQL Server: Optimizer | Duplicate (80 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | The opposite HAVING clause intersects and is always an empty set. |
118195 | 2025-05-14 13:34 | 2025-05-20 8:23 | MySQL Server: Optimizer | Not a Bug (79 days) | S2 | 9.3.0 | Ubuntu (22.04) | Any | The opposite WHERE clause intersects and is always an empty set. |
118193 | 2025-05-14 12:26 | 2025-05-18 16:38 | MySQL Server: Tests | Verified (81 days) | S3 | 8.0.42 | MacOS (15.5) | ARM | Test innodb.partition_upgrade_5727_mac_lctn_2 failing with a result difference |
118192 | 2025-05-14 12:05 | 2025-07-09 15:23 | MySQL Server: DML | Not a Bug (29 days) | S5 | 8.0.42 | Ubuntu (22.04) | x86 | Performance regression occurs with update statements after 6ba1fef |
118186 | 2025-05-13 15:34 | 2025-05-19 11:51 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (80 days) | S2 | 8.0.22 | Linux | Any | With row‑based replication (binlog_format = ROW), the function generates duplicate sequence values; in mixed mode (binlo |
118181 | 2025-05-13 12:36 | 2025-07-03 9:33 | MySQL Server: DML | Verified (37 days) | S5 | 8.0.42 | Linux | x86 | Performance regression on query statements after commit 0fa789a |
118180 | 2025-05-13 12:18 | 2025-05-13 12:48 | MySQL Server: Command-line Clients | Verified (86 days) | S3 | 8.0.42 | Any | Any | mysql client got segmentation fault since the mysql.charset is null during restarting |
118177 | 2025-05-13 8:53 | 2025-05-22 6:28 | MySQL Server: Optimizer | Verified (77 days) | S3 | 8.0.35 | Any | Any | Unnecessary filter operator in the execution plan |
118174 | 2025-05-13 6:43 | 2025-05-14 7:18 | MySQL Server: Optimizer | Verified (85 days) | S3 | 8.0 | Any | Any | Skip Scan doesn't support non-covering key scan |
118173 | 2025-05-13 6:42 | 2025-07-03 9:24 | MySQL Server: DML | Verified (36 days) | S5 | 8.0.42 | Ubuntu (22.04) | x86 | The insert statement suffers a performance penalty after commit cd66c5c. |
118172 | 2025-05-13 3:54 | 2025-07-23 7:57 | MySQL Server: InnoDB storage engine | Analyzing (15 days) | S3 | 8.0.31 | Windows | x86 ( x86_64) | 猜测间隙锁可以加到普通索引上,导致只能防止插入操作而不能防止select ...for update操作 |
118169 | 2025-05-12 12:38 | 2025-05-15 11:56 | MySQL Server: Tests | Verified (84 days) | S3 | 8.0.42, 8.4.5 | MacOS (15.4.1) | ARM | Test innodb.partition_upgrade_8019_mac_lctn_2_debug failing |
118168 | 2025-05-12 12:27 | 2025-07-24 8:33 | MySQL Server: Replication | Verified (86 days) | S1 | 8.0.41 | Any | Any | MySQL data dictionary fails to upgrade at startup with lock timeout on ALTER TABLE |
118164 | 2025-05-12 8:38 | 2025-05-12 13:01 | MySQL Server: DML | Verified (87 days) | S3 | 8.0.41 | Linux | x86 | When sort_buffer_size is set to a different value, group_concat returns different results. |
118159 | 2025-05-10 2:12 | 2025-05-13 7:37 | MySQL Server: DML | Duplicate (86 days) | S2 | 8.4.3 | Any | Any | recursive CTE with float returns error: Out of range value |
118158 | 2025-05-09 20:09 | 2025-05-12 12:05 | MySQL Server: Optimizer | Verified (87 days) | S5 | 8.4.5 | Any | Any | Endless loop while executing some CTE |
Showing all 158 (Edit, Save, CSV, Feed) |