| Showing all 187 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119572 | 2025-12-18 3:42 | 2025-12-18 3:42 | MySQL Server: Prepared statements | Open | S2 | Any | Any | Contribution by Tencent: Prepared statement reprepare with optimizer trace crashes in decimal2string | |
| 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 |
| 119569 | 2025-12-17 7:40 | 2025-12-18 9:32 | MySQL Server: Optimizer | Verified | S3 | 8.0 | Any | Any | any_value within window function returns wrong result |
| 119567 | 2025-12-17 2:53 | 2025-12-18 2:10 | MySQL Server: InnoDB storage engine | Open | 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 (2 days) | S3 | 8.4.7 | Any | Any | SHOW BINLOG EVENTS fails with Event too big |
| 119554 | 2025-12-15 16:22 | 2025-12-18 16:02 | MySQL Server: InnoDB storage engine | Open | S2 | 8.043 | CentOS ( 7.9.2009 (Core)) | Any | CRASH SERVER after Truncate |
| 119547 | 2025-12-12 11:23 | 2025-12-12 11:23 | MySQL Server: InnoDB storage engine | Open | S1 | mysql-8.0 | Any | Any | InnoDB crash occurred due to the invalid phy_pos in dict_index_t |
| 119545 | 2025-12-12 7:27 | 2025-12-12 8:41 | MySQL Server: DML | Not a Bug (6 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 (6 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 (6 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 (3 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 (7 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 (8 days) | S2 | 8.0 | Any | Any | hash join result incorrect |
| 119526 | 2025-12-09 3:13 | 2025-12-10 11:59 | MySQL Server: Optimizer | Need Feedback (8 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 (10 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 (3 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 (14 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 (13 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 | 2025-12-08 5:08 | MySQL Server: Optimizer | Need Feedback (10 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 (15 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 (10 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 (16 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 (16 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 (16 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 (17 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 (15 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 (17 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 (19 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 (17 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 (20 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-11-27 6:59 | 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 | 2025-11-25 10:26 | MySQL Server: InnoDB storage engine | Open | 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 (21 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 (20 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 (21 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 (11 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 | 2025-11-24 10:47 | MySQL Server: Locking | Open (24 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 (21 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 (21 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 (26 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 (21 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 (11 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 (11 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 (28 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 (15 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 (11 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 (11 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 (11 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 (11 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 (29 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 (11 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 (11 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 (10 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 (11 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 (11 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 (11 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 (34 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 (4 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() |
| 119385 | 2025-11-13 9:41 | 2025-12-06 22:51 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.41 | Any | Any | After replacing the expressions inside BETWEEN ... AND with constants, the results become inconsistent. |
| 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 (12 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 (12 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 (12 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 (12 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 (36 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 (12 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 (12 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 (12 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 (28 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 (28 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 (28 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 (28 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 (28 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 (28 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 (36 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-11-20 11:20 | MySQL Server: Optimizer | Verified (28 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 (37 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 (37 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 (37 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 (41 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 (41 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 (41 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 (41 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 (41 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 (41 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 (12 days) | S3 | 8.0.41 | Any | Any | BETWEEN clause returns incorrect results when comparing numeric literal with DATETIME columns |
| 119306 | 2025-11-05 7:02 | 2025-11-06 5:34 | MySQL Server: Optimizer | Verified (42 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 (2 days) | S3 | 8.0.41 | Linux | x86 | The query results of enabling and disabling materialization are inconsistent. |
| 119303 | 2025-11-05 1:49 | 2025-11-05 5:00 | MySQL Server: DML | Verified (43 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 (44 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 (41 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 (44 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 (44 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 (47 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 (17 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 (14 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 |
| 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 |
| 119262 | 2025-10-29 9:01 | 2025-11-04 23:01 | MySQL Server: Optimizer | Verified (44 days) | S3 | 8.0.44,8.4.6,9.4.0 | Any | Any | Incorrect result on comparison between a float expression and an indexed SMALLINT column. |
| 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 |
| 119255 | 2025-10-28 7:08 | 2025-10-28 7:08 | MySQL Server: InnoDB storage engine | Open | S3 | mysql-8.0.44 | Any | Any | Assertion failure triggered by temporary table dirty page flush |
| 119253 | 2025-10-28 4:57 | 2025-10-28 4:58 | MySQL Server: InnoDB storage engine | Open (51 days) | S3 | 9.5.0 | MacOS (26.0.1) | ARM | innodb.tablespace_encrypt_9 crashing the server with assertion failure |
| 119248 | 2025-10-27 16:46 | 2025-10-27 16:54 | MySQL Server: Security: Privileges | Open (52 days) | S3 | 9.4.0 | Any | Any | CHECK TABLE command can be executed by users with the table-level GRANT OPTION privilege |
| 119247 | 2025-10-27 16:09 | 2025-10-28 7:29 | MySQL Server: Tests | Open (51 days) | S3 | 8.0.44, 9.5.0 | MacOS (26.0.1) | ARM | Test main.log_buffered-big failure |
| 119241 | 2025-10-27 11:25 | 2025-10-27 11:29 | MySQL Server: DDL | Open (52 days) | S2 | 8.0.41 | Any | Any | Exception when creating index instance |
| 119236 | 2025-10-27 4:15 | 2025-11-04 23:07 | MySQL Server: Prepared statements | Verified (48 days) | S2 | 8.0.44 | Any | Any | The SQL reprepare bug results in 100% CPU load. |
| 119235 | 2025-10-27 2:47 | 2025-11-10 14:16 | MySQL Server: InnoDB storage engine | Open (38 days) | S3 | 9.5.0 | Any | Any | Crash due to race condition between buf_LRU_check_size_of_non_data_objects and buf_pool_resize |
| 119225 | 2025-10-24 9:11 | 2025-10-31 5:22 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.0.43 | Any | Any | weedout not work for rematerialized temptable |
| 119220 | 2025-10-23 14:55 | 2025-11-07 9:22 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.4.6 | Any | x86 | Subquery materialization in LEFT JOIN ON clause loses WHERE conditions |
| 119214 | 2025-10-23 3:16 | 2025-10-23 3:16 | MySQL Server: Documentation | Open | S3 | Any | Any | Document the handling of NULL to NOT NULL conversion in MySQL replication | |
| 119204 | 2025-10-22 8:10 | 2025-10-23 10:04 | MySQL Server: DML | Verified (56 days) | S2 | 8.0,9.5 | Any | Any | The change of join order may lead to inconsistent update data |
| 119203 | 2025-10-21 12:46 | 2025-11-04 23:25 | MySQL Server: Optimizer | Verified (44 days) | S3 | 8.0.41 | Any | Any | An expression that returns NULL instead of NULL is used to perform the <=> operation. the sql retrun wrong result. |
| 119198 | 2025-10-20 19:44 | 2025-10-22 6:59 | MySQL Server: Optimizer | Verified (57 days) | S2 | 8.4.6 | Any | Any | Optimizer with reverse index range scan gives incorrect query result |
| 119190 | 2025-10-19 12:28 | 2025-10-19 12:30 | MySQL Server: Optimizer | Open | S5 | 8.4.6 | Any | Any | Comparing the result of EXISTS(subquery) with a constant severely reduces query performance |
| 119188 | 2025-10-18 9:10 | 2025-10-18 9:10 | MySQL Server: Documentation | Open | S3 | 9.2.0 | Ubuntu (Ubuntu 20.04 LTS) | x86 (AMD EPYC 7742, 128 Cores, 2.25 GHz) | Incorrect documentation: ALTER TABLE does not always require CREATE and INSERT privileges |
| 119187 | 2025-10-18 4:41 | 2025-10-18 4:41 | MySQL Server: Optimizer | Open | S2 | 9.4.0 | Linux | x86 | CTE with correlated EXISTS subquery causes incorrect NULL handling in WHERE clause with IS NULL predicate |
| 119167 | 2025-10-16 8:28 | 2025-11-17 1:00 | MySQL Server: Optimizer | No Feedback (32 days) | S3 | 8.0.25 | Linux (ARM Kylin v10) | ARM (ARM Kylin v10) | SIGSEGV in calc_row_difference()/memcmp during GROUP BY + MAX(CONCAT(...)) (temporary table update path) |
| 119164 | 2025-10-16 3:35 | 2025-11-05 1:42 | MySQL Server: DML | Open (43 days) | S3 | 8.0.41 | Any | Any | CASE expression evaluation incorrectly validates REGEXP_INSTR arguments when branch is not executed |
| 119160 | 2025-10-15 9:32 | 2025-10-15 9:32 | MySQL Server: DML | Open | S3 | 8.0.41 | Any | Any | Found different values set for sql_buffer_result and materialization lead to different query results. |
| 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 |
| 119156 | 2025-10-15 2:01 | 2025-10-15 2:01 | MySQL Server: Optimizer | Open | 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 |
| 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. |
| 119148 | 2025-10-14 7:54 | 2025-11-15 1:00 | MySQL Server: InnoDB storage engine | No Feedback (34 days) | S3 | 8.0.41 | Any | Any | InnoDB crash with Assertion failure: trx0trx.cc:1988:UT_LIST_GET_LEN(trx->lock.trx_locks) |
| 119145 | 2025-10-13 12:53 | 2025-10-13 12:53 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Any (windows ) | Any (x64) | INNER JOIN and INTERSECT of LEFT/RIGHT JOINs return different results with complex boolean conditions |
| 119144 | 2025-10-13 12:49 | 2025-10-13 12:49 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Windows | Any (x64) | INNER JOIN and STRAIGHT_JOIN return different results with identical ABS function conditions |
| 119143 | 2025-10-13 12:37 | 2025-10-13 12:37 | MySQL Server: Optimizer | Open | S3 | 8.4.6 | Any | Any | INNER JOIN and STRAIGHT_JOIN return different results with ATAN function |
| 119141 | 2025-10-13 8:21 | 2025-10-13 8:21 | MySQL Server: DML | Open | S3 | 8.0.41 | Linux | x86 | The results returned by the prepare query are different from those returned by the non-prepare query. |
| 119139 | 2025-10-13 7:30 | 2025-12-18 8:56 | MySQL Server: Optimizer | Verified | S1 | 9.4.0 | Any | Any | Unexpected error `Incorrect DECIMAL value: '0' for column '' at row -1` |
| 119133 | 2025-10-11 6:55 | 2025-10-11 6:56 | MySQL Server: InnoDB storage engine | Open (68 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. |
| 119132 | 2025-10-11 3:44 | 2025-12-18 8:37 | MySQL Server: DML | Verified | S3 | 8.0.41 | Any | Any | Unexpected query result when using complex boolean expressions with UNION ALL and LIKE in SELECT query |
| 119131 | 2025-10-11 2:35 | 2025-12-18 8:14 | MySQL Server: Optimizer | Duplicate | S3 | 8.0.41 | Any | Any | The query is normal without using the histogram, but an error occurs when using the histogram |
| 119130 | 2025-10-11 2:30 | 2025-12-17 9:33 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0.41 | Any | Any | Different values set for sql_buffer_result and materialization lead to different query results. |
| 119127 | 2025-10-10 11:58 | 2025-12-17 8:20 | MySQL Server: Optimizer | Verified (1 day) | S2 | 8.4.6 | Any | Any | INNER JOIN and INTERSECT of LEFT/RIGHT JOINs return different results when unique index is present |
| 119125 | 2025-10-10 3:52 | 2025-12-17 8:10 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0.41 | Any | Any | after modifying the insertion sequence of the table,the results of the same query are inconsistent. |
| 119124 | 2025-10-10 3:28 | 2025-12-16 9:19 | MySQL Server: DML | Verified (2 days) | S3 | 8.0.41 | Any | Any | The result of the COALESCE function varies depending on its different parameters. |
| 119122 | 2025-10-09 11:53 | 2025-12-16 9:14 | MySQL Server: DML | Verified (2 days) | S3 | 8.0.41 | Any | Any | The query is normal without using the histogram, but an error occurs when using the histogram |
| 119121 | 2025-10-09 11:06 | 2025-12-16 9:26 | MySQL Server: Optimizer | Duplicate (2 days) | S2 | 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns fewer rows than expected when ON condition is true for multiple rows |
| 119118 | 2025-10-09 8:17 | 2025-12-15 12:50 | MySQL Server: Optimizer | Verified (3 days) | S3 | 8.0.41 | Any | Any | The difference in results caused by enabling or disabling the optimizer's index_merge_union. |
| 119117 | 2025-10-09 4:15 | 2025-12-16 9:22 | MySQL Server: Optimizer | Duplicate (2 days) | S2 | 8.4.6 | Windows | Other (x64) | INNER JOIN returns results when join condition evaluates to false |
| 119111 | 2025-10-07 5:22 | 2025-12-15 11:36 | MySQL Server: Optimizer | Not a Bug (3 days) | S3 | 9.4.0 | Any | Any | Column Value change caused by MIN(column) --->-MAX(-column) |
| 119110 | 2025-10-07 5:19 | 2025-12-15 11:22 | MySQL Server: Optimizer | Verified (3 days) | S2 | 9.4.0 | Linux | x86 | Incorrect NULL filtering in CTE with UNION ALL over view containing LEFT JOIN on FALSE |
| 119101 | 2025-10-02 4:44 | 2025-10-11 3:25 | MySQL Server: Logging | Open (68 days) | S3 | 8.0.43 | Any | Any | Incorrect query_time is logged in the slow log when adjusting system time backward |
| 119100 | 2025-10-01 1:00 | 2025-10-06 4:18 | MySQL Server: Optimizer | Verified (73 days) | S2 | 9.4.0 | Linux | x86 | WHERE alias IS NULL Fails for Derived Column Using subquery |
| 119097 | 2025-09-30 9:04 | 2025-12-15 11:15 | MySQL Server: Optimizer | Verified (3 days) | S2 | MySQL 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns different results compared to INNER JOIN with identical conditions |
| 119094 | 2025-09-29 13:03 | 2025-12-12 13:38 | MySQL Server: Optimizer | Verified (6 days) | S3 | Any | Any | Performance optimization patches | |
| 119091 | 2025-09-29 9:56 | 2025-12-07 20:45 | MySQL Server: Replication | Duplicate (68 days) | S3 | Any | Any | Purge Relaylog Leads To Semi-sync Increased Response even set relay_log_space_limit=0 | |
| 119088 | 2025-09-28 6:31 | 2025-12-15 11:05 | MySQL Server: Optimizer | Verified (3 days) | S3 | 9.2,9.4 | Any | Any | sort with limit in hypergraph gets wrong result |
| 119087 | 2025-09-28 5:54 | 2025-12-12 9:33 | MySQL Server: Optimizer | Verified (6 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for subquery with BIGINT UNSIGNED |
| 119084 | 2025-09-27 14:14 | 2025-09-29 17:27 | MySQL Server: Documentation | Not a Bug (80 days) | S3 | Any | Any | The initial default values of the character_set_connection GLOBAL variable and the SESSION variable are inconsistent | |
| 119083 | 2025-09-27 14:11 | 2025-10-11 3:23 | MySQL Server: Documentation | Open (68 days) | S3 | Any | Any | The default value of skip_name_resolve in the document is different from actual | |
| 119081 | 2025-09-27 8:35 | 2025-10-02 7:12 | MySQL Server: Optimizer | Verified (80 days) | S3 | 8.0.43 | Any | Any | UPDATE with CASE/IFNULL expression produces unexpected error: Incorrect DECIMAL value: '0' for column '' at row -1 |
| 119080 | 2025-09-27 8:16 | 2025-10-01 13:58 | MySQL Server: Optimizer | Verified (80 days) | S3 | 8.0.43 | Any | Any | SELECT vs. TLP partitioning query returns different cardinalities (cardinality mismatch) |
| 119074 | 2025-09-26 4:46 | 2025-10-01 13:59 | MySQL Server: Optimizer | Verified (80 days) | S2 | 9.4.0 | Linux | x86 | Incorrect result with derived_condition_pushdown optimization in correlated subquery with LEFT JOIN ON FALSE |
| 119073 | 2025-09-26 3:29 | 2025-10-01 13:59 | MySQL Server: InnoDB storage engine | Verified (80 days) | S3 | 9.4.0 8.4.6 | Any | x86 | Inconsistent Type Conversion Behavior for TIMESTAMP Column Based on UNIQUE Constraint |
| 119068 | 2025-09-25 8:43 | 2025-10-01 14:05 | MySQL Server: Optimizer | Verified (80 days) | S2 | 9.4.0 | Linux | x86 | RIGHT JOIN on VIEW with IN subquery returns incorrect non-NULL value instead of NULL |
| 119066 | 2025-09-24 13:06 | 2025-10-03 11:03 | MySQL Server: Optimizer | Verified (80 days) | S5 | 8.0.40+ | Any | Any | MySQL 8.0.40+ is about 2-3x times slower than 8.0.39 in particular index scan scenario |
| 119065 | 2025-09-24 12:32 | 2025-12-07 20:45 | MySQL Server: Locking | Duplicate (80 days) | S3 | 8.4.4 (Any) | Any | Any | Why does the EXISTS operator not create an S lock in the first case, but create one in the second? |
| 119063 | 2025-09-24 3:45 | 2025-10-01 14:04 | MySQL Server: InnoDB storage engine | Verified (80 days) | S3 | 8.0.43 | Any | Any | Unused variable 'fk_max_recusive_level' |
| 119062 | 2025-09-23 11:08 | 2025-09-25 16:09 | MySQL Server: Optimizer | Verified (86 days) | S5 | 9.4.0 | Any | Any | A missed optimization opportunity of "FALSE and any_expr" in WHERE clause |
| 119059 | 2025-09-23 3:44 | 2025-09-25 16:07 | MySQL Server: Optimizer | Verified (86 days) | S2 | 9.2.0, 9.4.0 | Any | Any | Inconsistent result behavior when using EXCEPT equivalent NATRUAL JOIN |
| 119058 | 2025-09-23 0:57 | 2025-09-25 16:08 | MySQL Server: Prepared statements | Verified (86 days) | S1 | 9.4.0 | Any | Any | `\` is inconsistent in prepared statement and normal query |
| 119056 | 2025-09-22 15:21 | 2025-09-23 2:40 | MySQL Server: Optimizer | Verified (86 days) | S3 | 9.4.0 | Any | Any | column value change cased by SUM(DISTINCT) changed to AVG(DISTINCT)*COUNT(DISTINCT) |
| 119053 | 2025-09-22 9:22 | 2025-09-23 2:40 | MySQL Server: Optimizer | Verified (86 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect filtering for NOT BETWEEN on a FLOAT PRIMARY KEY |
| 119052 | 2025-09-22 9:22 | 2025-09-23 2:43 | MySQL Server: Optimizer | Verified (86 days) | S5 | 8.0.43 | Linux (5.10.134-19.al8.x86_64) | x86 (x86_64) | Performance regression in 8.0.40 |
| 119049 | 2025-09-22 7:23 | 2025-09-22 7:53 | MySQL Server: Optimizer | Closed (87 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 |
| 119048 | 2025-09-21 12:57 | 2025-09-23 1:27 | MySQL Server: Prepared statements | Verified (87 days) | S2 | 9.4.0 | Any | Any | inconsistent result of two equivalent query with operator ~ |
| Showing all 187 (Edit, Save, CSV, Feed) |
