| Showing all 151 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119220 | 2025-10-23 14:55 | 2025-10-23 14:55 | MySQL Server: Optimizer | Open | 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 (2 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-10-22 1:38 | MySQL Server: DML | Open (3 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 (3 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-10-16 14:49 | MySQL Server: Optimizer | Need Feedback (9 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-10-16 3:35 | MySQL Server: Query Cache | Open | 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-10-14 8:46 | MySQL Server: InnoDB storage engine | Need Feedback (11 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. |
| 119133 | 2025-10-11 6:55 | 2025-10-11 6:56 | MySQL Server: InnoDB storage engine | Open (14 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-10-11 3:44 | MySQL Server: DML | Open | 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-10-11 2:35 | MySQL Server: DML | Open | 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-10-11 2:30 | MySQL Server: DML | Open | 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-10-10 11:58 | MySQL Server: Optimizer | Open | 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-10-10 3:52 | MySQL Server: DML | Open | 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-10-10 3:28 | MySQL Server: DML | Open | 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-10-09 11:53 | MySQL Server: DML | Open | 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-10-09 11:06 | MySQL Server: Optimizer | Open | 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-10-09 8:17 | MySQL Server: Optimizer | Open | 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-10-09 4:15 | MySQL Server: Optimizer | Open | S2 | 8.4.6 | Windows | Other (x64) | INNER JOIN returns results when join condition evaluates to false |
| 119111 | 2025-10-07 5:22 | 2025-10-11 3:21 | MySQL Server: Optimizer | Open (14 days) | S3 | 9.4.0 | Any | Any | Column Value change caused by MIN(column) --->-MAX(-column) |
| 119110 | 2025-10-07 5:19 | 2025-10-11 3:25 | MySQL Server: Optimizer | Open (14 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 (14 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 (19 days) | S2 | 9.4.0 | Linux | x86 | WHERE alias IS NULL Fails for Derived Column Using subquery |
| 119097 | 2025-09-30 9:04 | 2025-10-11 3:24 | MySQL Server: Optimizer | Open (14 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-10-11 3:24 | MySQL Server: Optimizer | Open (14 days) | S3 | Any | Any | Performance optimization patches | |
| 119091 | 2025-09-29 9:56 | 2025-10-11 8:51 | MySQL Server: Replication | Duplicate (14 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-10-11 3:24 | MySQL Server: Optimizer | Open (14 days) | S3 | 9.2,9.4 | Any | Any | sort with limit in hypergraph gets wrong result |
| 119084 | 2025-09-27 14:14 | 2025-09-29 17:27 | MySQL Server: Documentation | Not a Bug (26 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 (14 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 (26 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 (26 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 (26 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 (26 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 (26 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 (26 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-09-29 13:08 | MySQL Server: Locking | Duplicate (26 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 (26 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 (32 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 (32 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 (32 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 (32 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 (32 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 (32 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 (33 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 (33 days) | S2 | 9.4.0 | Any | Any | inconsistent result of two equivalent query with operator ~ |
| 119043 | 2025-09-19 9:14 | 2025-09-23 2:39 | MySQL Server: InnoDB storage engine | Verified (32 days) | S3 | 8.0.41 | Any | Any | in certain situations the table space will be greatly wasted |
| 119041 | 2025-09-19 8:19 | 2025-09-23 9:57 | MySQL Server: Optimizer | Verified (32 days) | S2 | 8.0.25 8.0.40 | Any | Any | statistics automatic update cause poor execution plan |
| 119040 | 2025-09-19 6:46 | 2025-09-23 1:39 | MySQL Server: Optimizer | Verified (36 days) | S3 | 8.0.41 | Linux | x86 | The execution performance of the default execution plan is poor. If ignore index is used, the query performance is great |
| 119038 | 2025-09-19 5:33 | 2025-09-25 16:08 | MySQL Server: Documentation | Verified (32 days) | S3 | 8.0, 8.4 | Any | Any | binlog_row_image=MINIMAL on replica only contains a full after row image |
| 119035 | 2025-09-18 10:11 | 2025-09-23 0:48 | MySQL Server: Optimizer | Verified (33 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for BETWEEN with mixed types on a BINARY column with a UNIQUE key |
| 119034 | 2025-09-18 9:34 | 2025-09-23 0:50 | MySQL Server: Optimizer | Verified (33 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result when comparing a numeric string literal to a BIT column with a UNIQUE key |
| 119033 | 2025-09-18 9:16 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (33 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect filtering when comparing a BINARY-cast integer to a BIT column with a UNIQUE key |
| 119032 | 2025-09-18 7:52 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (33 days) | S2 | 9.2.0 | Any | Any | Inconsistency with MySQL 8.0.36 in MySQL 9.2.0: Equivalent INTERSECT query does not match INNER JOIN result and returns |
| 119031 | 2025-09-18 6:12 | 2025-09-23 5:39 | MySQL Server: Parser | Not a Bug (32 days) | S3 | 8.4.6 | MacOS | Any | HAVING clause fails with "Unknown column" for a subquery alias that is valid in GROUP BY |
| 119030 | 2025-09-18 5:07 | 2025-09-23 11:56 | MySQL Server: Optimizer | Can't repeat (32 days) | S5 | 9.4.0 | Ubuntu (22.04) | Any | Significant performance regression of INTERSECT operation in MySQL 9.4.0 |
| 119029 | 2025-09-18 0:40 | 2025-09-22 14:34 | MySQL Server: Optimizer | Verified (36 days) | S5 | 9.4.0 | Any | Any | Two missed optimization opportunities of "TRUE OR any_expr" |
| 119028 | 2025-09-18 0:20 | 2025-09-22 14:33 | MySQL Server: Optimizer | Verified (36 days) | S5 | 9.4.0 | Any | Any | two missed optimization oppotunities of "FALSE and any_expr" |
| 119022 | 2025-09-17 12:40 | 2025-09-23 0:51 | MySQL Server: Optimizer | Verified (33 days) | S2 | 9.4.0 | Any | Any | column value change cased by Union ALL |
| 119014 | 2025-09-16 3:49 | 2025-09-23 0:52 | MySQL Server: Documentation | Verified (33 days) | S3 | Any | Any | The document uses the incorrect example replicate-wild-do-table=db6.channel_1.t1% | |
| 119013 | 2025-09-16 3:06 | 2025-09-23 0:52 | MySQL Server: Documentation | Verified (33 days) | S3 | Any | Any | can't set more than one tables using option --replicate-wild-ignore-table | |
| 118999 | 2025-09-12 10:03 | 2025-09-23 7:52 | MySQL Server: Locking | Verified (33 days) | S3 | 8.4.6 | Linux | Any | Unexpected background histogram update warnings(MY-015116) |
| 118987 | 2025-09-10 14:53 | 2025-09-15 16:07 | MySQL Server: Documentation | Verified (44 days) | S3 | Any | Any | Contribution: docs: typo unrwapped -> unwrapped | |
| 118984 | 2025-09-10 7:05 | 2025-09-15 16:01 | MySQL Server: InnoDB storage engine | Verified (43 days) | S3 | 9.4.0 | Any | Any | fts_optimize_read_deleted_doc_id_snapshot reads BEING_DELETED table twice |
| 118983 | 2025-09-10 6:59 | 2025-09-15 16:03 | MySQL Server: InnoDB storage engine | Verified (44 days) | S3 | 8.0.43 | Any | Any | PCursor::move_to_next_block is not functioning as expected |
| 118982 | 2025-09-10 6:55 | 2025-09-26 12:01 | MySQL Server: Optimizer | Not a Bug (29 days) | S1 | 9.4.0 | Linux | Any | Unexpected result of IN operator |
| 118981 | 2025-09-10 3:41 | 2025-09-22 14:32 | MySQL Server: DML | Verified (36 days) | S3 | 8.0.41 | Any | Any | adding DEFAULT FUNCTION in the where clause, the query returns a wrong result caused by the cached value. |
| 118980 | 2025-09-10 2:52 | 2025-09-15 16:00 | MySQL Server: Optimizer | Verified (44 days) | S2 | MySQL8.0.41 | Any | Any | queries have different results using and without index |
| 118976 | 2025-09-09 12:43 | 2025-09-11 13:07 | MySQL Server: Performance Schema | Not a Bug (44 days) | S3 | 8.0.41 | Any | Any | Executing "show full columns from table" under high concurrency results in poor performance. |
| 118961 | 2025-09-09 3:43 | 2025-09-10 6:45 | MySQL Server: Optimizer | Not a Bug (45 days) | S3 | 8.0.41 | Any | Any | float in large value query no result |
| 118960 | 2025-09-09 2:57 | 2025-09-09 7:12 | MySQL Server: Optimizer | Verified (46 days) | S5 | 9.2, 8.0, 8.4 | Any | Any | Sort optimization fails as primary key info in secondary index is not considered after hint-enforced secondary index |
| 118957 | 2025-09-08 12:24 | 2025-09-08 15:18 | MySQL Server: Documentation | Not a Bug (47 days) | S3 | 8.0.35 | Any | Any | Documentation says you can use a HEX value for ALTER user passwords, but you can't. |
| 118949 | 2025-09-05 13:57 | 2025-09-10 0:42 | MySQL Server: Optimizer | Verified (47 days) | S2 | 9.2.0 | Linux (ubuntu 20.04) | Any | MySQL 9.2.0: Complex CASE in JOIN makes INNER vs INTERSECT yield different rows |
| 118941 | 2025-09-05 8:19 | 2025-09-10 14:45 | MySQL Server: Optimizer | Verified (45 days) | S2 | 8.0.x, 8.4.x | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with -0.001 Excludes 0.00 Row |
| 118937 | 2025-09-04 4:36 | 2025-09-10 0:43 | MySQL Server: Optimizer | Verified (46 days) | S2 | 9.4.0 | Any | Any | LEFT JOIN with constant functions returns incorrect results when condition is ON FALSE |
| 118927 | 2025-09-02 21:41 | 2025-09-22 14:28 | MySQL Server: Parser | Verified (37 days) | S3 | 9.4 | Any | ARM (arm64) | Incorrect Binary Library Hex Representation Due to Sign Extension in SHOW CREATE LIBRARY |
| 118923 | 2025-09-02 7:49 | 2025-09-04 11:46 | MySQL Server: InnoDB storage engine | Verified (52 days) | S2 | 8.4, 8.0.22, 9.4.0 | Any | Any | Abnormal read phenomena are observed under MySQL's Read Committed isolation level |
| 118918 | 2025-09-01 7:30 | 2025-09-04 11:47 | MySQL Server: Optimizer | Verified (52 days) | S2 | 9.4.0 | Any | Any | Inconsistent NULL handling in CTE LEFT JOIN results |
| 118916 | 2025-08-31 18:26 | 2025-09-05 8:21 | MySQL Server: Optimizer | Duplicate (50 days) | S2 | 9.4.0 | Any | Any | Incorrect result set when querying view with LEFT JOIN, COALESCE and EXISTS subquery |
| 118913 | 2025-08-29 3:40 | 2025-09-01 10:19 | MySQL Server: Optimizer | Verified (54 days) | S2 | 8.0.41, 9.4.0 | Any | Any | queries have different results for non primary key table and table with primary key |
| 118912 | 2025-08-28 16:24 | 2025-09-04 11:48 | MySQL Server: Optimizer | Verified (54 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Mismatch in Column values with SUM of IFNULL vs IFNULL of SUM |
| 118909 | 2025-08-28 11:04 | 2025-09-04 11:49 | MySQL Server: Optimizer | Verified (52 days) | S3 | 8.0.41, 9.4.0 | Linux | x86 | Inconsistent evaluation of WHERE predicate between table-scan and covering-index paths; result set changes with projecti |
| 118905 | 2025-08-28 6:47 | 2025-08-28 10:44 | MySQL Server: Optimizer | Not a Bug (58 days) | S3 | 8.0.41 | Linux | x86 | Inconsistent evaluation of WHERE predicate between table-scan and covering-index paths; result set changes with projecti |
| 118904 | 2025-08-28 3:20 | 2025-09-04 11:46 | MySQL Server: Optimizer | Verified (54 days) | S2 | 8.0.41+ | Any | Any | Incorrect results could be returned when using index condition pushdown and Range checked for each record |
| 118903 | 2025-08-28 2:20 | 2025-10-02 1:00 | MySQL Server: Optimizer | No Feedback (24 days) | S3 | Any | Any | Incorrect results could be returned when using index condition pushdown | |
| 118902 | 2025-08-27 14:16 | 2025-08-28 2:25 | MySQL Server: InnoDB storage engine | Closed (58 days) | S5 | 8.0.42 | Any | Any | no need to set rec_new_set_instant in row_upd_rec_in_place |
| 118893 | 2025-08-26 8:31 | 2025-09-04 11:53 | MySQL Server: Optimizer | Verified (54 days) | S3 | 9.4.0-1.el9 | Linux | Any | "SELECT AUTO_INCREMENT FROM information_schema.TABLES" reports a value that is reduced by one |
| 118890 | 2025-08-25 12:32 | 2025-09-04 11:52 | MySQL Server: Documentation | Verified (54 days) | S3 | 8.0, 8.4, 9.2 | Any | Any | wrong supported ranges in the manual |
| 118888 | 2025-08-25 7:19 | 2025-09-16 11:29 | MySQL Server: DDL | Verified (39 days) | S2 | 8.0.43/8.4.6 | Any | Any | DDL operation fills the entire disk space and eventually fails |
| 118887 | 2025-08-25 2:49 | 2025-08-29 11:06 | MySQL Server: Optimizer | Verified (61 days) | S3 | 9.4.0 | CentOS | Any | Zero '0000-00-00 00:00:00' datetime returned when SQL_BUFFER_RESULT is used |
| 118876 | 2025-08-21 13:22 | 2025-08-25 12:00 | MySQL Server: Documentation | Verified (65 days) | S3 | 9.4 | Any | Any | Contribution: docs: update protocol description |
| 118875 | 2025-08-21 12:42 | 2025-08-21 13:16 | MySQL Server: DML | Verified (65 days) | S3 | 8.0.41, 8.0.43 | Any | Any | set optimizer_switch='block_nested_loop=off/on', result is different. |
| 118872 | 2025-08-21 5:01 | 2025-08-21 6:31 | MySQL Server: InnoDB storage engine | Verified (65 days) | S3 | 8.0.40 | Any | Any | Innodb_data_written lacks statistics for double-write files |
| 118871 | 2025-08-21 2:37 | 2025-08-29 11:12 | MySQL Server: Optimizer | Verified (61 days) | S3 | 8.0.43 MySQL Community Server - GPL | Linux (Linux (Rocky Linux release 8.8 (Green Obsidian))) | Any | Constant conditions in SQL with derived views are not passed.new |
| 118870 | 2025-08-21 2:22 | 2025-08-21 2:33 | MySQL Server: Optimizer | Closed (65 days) | S3 | 8.0.43 MySQL Community Server - GPL | Linux (Rocky Linux release 8.8 (Green Obsidian)) | Any | Constant conditions in SQL with derived views are not passed. |
| 118867 | 2025-08-20 18:35 | 2025-09-01 11:12 | MySQL Server: InnoDB storage engine | Verified (65 days) | S3 | 9.4 | Any | Any | Contribution: Optimize NUMA Scheduling |
| 118866 | 2025-08-20 18:17 | 2025-09-26 8:43 | MySQL Server: InnoDB storage engine | Verified (65 days) | S3 | 9.4 | Any | Any | Contribution: Optimize hash_table_locks |
| 118865 | 2025-08-20 18:17 | 2025-08-21 6:21 | MySQL Server: Performance Schema | Verified (65 days) | S3 | 9.4 | Any | Any | Contribution: Optimize process of thread counter |
| 118864 | 2025-08-20 18:17 | 2025-09-16 1:31 | MySQL Server: InnoDB storage engine | Verified (65 days) | S3 | 9.4 | Any | Any | Contribution: Optimize undo spaces lock |
| 118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (65 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
| 118862 | 2025-08-20 14:05 | 2025-08-21 6:28 | MySQL Server: Optimizer | Verified (65 days) | S3 | 8.0.x, 8.4.x, 8.0.43 | Any | Any | MySQL Returns Incorrect Results for Complex Query with Set Operations |
| 118858 | 2025-08-20 8:51 | 2025-09-23 4:03 | MySQL Server: Optimizer | Verified (32 days) | S2 | 9.2.0 | Linux | Any | Inconsistency between the results returned by MySQL and other vendors' database systems was found during differentiation |
| 118857 | 2025-08-20 8:39 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (66 days) | S2 | 9.2.0 | Linux | Any | Bug Summary: MySQL Returns Incorrect Results for Complex Query with Set Operations |
| 118853 | 2025-08-19 9:58 | 2025-08-19 11:32 | MySQL Server: Documentation | Closed (67 days) | S3 | 8.0.43, 8.4.5, 9.4.0 | Any | Any | Wrong description for TEXT datatype (and its variants) maximum length in the refman. |
| 118849 | 2025-08-18 12:14 | 2025-08-18 23:50 | MySQL Server: Optimizer | Verified (68 days) | S3 | 8.0.41 | Any | Any | after add HINT:JOIN_ORDER, the result is wrong. |
| 118848 | 2025-08-15 21:07 | 2025-09-19 1:00 | MySQL Server: Errors | No Feedback (37 days) | S3 | 8.0.43 | Windows (Microsoft Windows 11 Home) | Any | My screen is black when i try to open an EER diagram |
| 118846 | 2025-08-15 8:50 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (67 days) | S3 | 9.3.0 | Ubuntu | Any | column name change cased by where |
| 118845 | 2025-08-15 7:32 | 2025-08-18 9:41 | MySQL Server: DML | Not a Bug (68 days) | S3 | 8.0.41 | Any | Any | After a prepare stmt is declared, switch to a new database and run the stmt,the result is still result in the last DB. |
| 118844 | 2025-08-14 23:06 | 2025-08-16 5:57 | MySQL Server: Information schema | Verified (70 days) | S3 | 9.4.0 | Any | Any | In MySQL 9.4.0, Reserved is set 0 in information schema for one of the new keyword out of 2 |
| 118842 | 2025-08-14 8:50 | 2025-09-22 3:27 | MySQL Server: InnoDB storage engine | Verified (33 days) | S1 | 8.4.6 | Red Hat (9.4) | x86 | Transactions get stuck in stage/sql/waiting for handler commit until mysqld restart (MySQL 8.4.3), heavy concurrent DML |
| 118840 | 2025-08-14 3:33 | 2025-08-19 7:49 | MySQL Server: DML | Not a Bug (67 days) | S3 | 8.0.41 | Any | Any | a query including where (NOT XX NOT IN ()) returns a wrong nonempty result while (NOT XX NOT IN ()) returns 0. |
| 118839 | 2025-08-14 3:13 | 2025-08-18 23:50 | MySQL Server: DML | Verified (68 days) | S3 | 8.0.41 | Any | Any | a query including the having subclause that returns NULL, return a wrong nonempty result. |
| 118838 | 2025-08-14 3:10 | 2025-08-18 15:21 | MySQL Server: DML | Closed (68 days) | S3 | 8.0.41 | Any | Any | A query containing a where subclause returnning true, the query result is empty. |
| 118837 | 2025-08-14 3:05 | 2025-08-18 23:51 | MySQL Server: Optimizer | Verified (68 days) | S3 | 8.0.41 | Any | Any | After having(col) in the query statement is changed to having min(col), the returned result is incorrect. |
| 118836 | 2025-08-14 3:01 | 2025-08-18 23:56 | MySQL Server: Optimizer | Verified (68 days) | S3 | 8.0.41 | Any | Any | adding a having clause that return 1/TRUE, the query returns a different and wrong empty result. |
| 118835 | 2025-08-14 2:56 | 2025-08-19 0:17 | MySQL Server: Optimizer | Verified (67 days) | S3 | 8.0.41 | Any | Any | A query statement that returns 0/FALSE in the having clause, the returned result is not null. |
| 118834 | 2025-08-14 2:54 | 2025-08-19 0:16 | MySQL Server: DML | Closed (67 days) | S3 | 8.0.41 | Any | Any | Change a number in the query statement to -(-NUMBER), the query return different results. |
| 118833 | 2025-08-14 2:43 | 2025-08-19 0:36 | MySQL Server: Optimizer | Verified (67 days) | S3 | 8.0.41 | Any | Any | Two queries that use the where clause with opposite semantics return the same result. |
| 118832 | 2025-08-14 2:39 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (67 days) | S3 | 8.0.41, 9.4.0 | Any | Any | using the return value replacing the IFNUILL function , the query returns different value; |
| 118831 | 2025-08-14 2:33 | 2025-08-19 10:51 | MySQL Server: Optimizer | Verified (67 days) | S3 | 8.0.41, 9.4.0 | Any | Any | !(expression1 or expression2) return a different result from !(expression1), while expression2 is 0. |
| 118830 | 2025-08-14 2:26 | 2025-08-19 10:51 | MySQL Server: DML | Verified (67 days) | S3 | 8.0.41, 9.4.0 | Any | Any | After a constant value is replaced by a LEAST function returnning the same value, the sql returns different result; |
| 118820 | 2025-08-13 7:39 | 2025-08-20 6:01 | MySQL Server: InnoDB storage engine | Verified (67 days) | S2 | 8.0.41 | Any | Any | AHI results the mysqld hung and assertion failure: btr0sea.cc:295:sleep_counter < 60000 |
| 118819 | 2025-08-13 5:53 | 2025-09-18 9:59 | MySQL Server: Command-line Clients | Not a Bug (37 days) | S2 | 9.4.0 | Any | Any | Vertical (\G) doesn't work in MySQL 9.4.0 |
| 118818 | 2025-08-13 3:44 | 2025-10-19 17:14 | MySQL Server: InnoDB storage engine | Closed (6 days) | S2 | 8.0.41, 8.0.43 | Any | Any | Assertion failure row0pread.h:306:active >= n_threads happens when create thread fail for parallel scan |
| 118817 | 2025-08-12 11:35 | 2025-08-13 7:23 | MySQL Server: DDL | Verified (73 days) | S3 | 8.0 | Any | Any | Code Comment Error for row_import::m_n_instant_cols in storage/innobase/row/row0import.cc |
| 118814 | 2025-08-12 3:47 | 2025-10-11 3:22 | MySQL Server: Windows | Open (14 days) | S2 | 8.0.39 | Windows | Any | I/O error while writing to file: .\#ib_16384_0.dblwr |
| 118813 | 2025-08-12 3:20 | 2025-08-21 12:49 | MySQL Server: DML | Not a Bug (65 days) | S3 | 8.0.41, 8.0.43, 8.4.6 | Any | Any | utf8mb4_0900_ai_ci check different string mark as duplicate |
| 118811 | 2025-08-11 3:31 | 2025-08-11 12:02 | MySQL Server: Optimizer | Verified (75 days) | S3 | 8.0.43 | Linux | x86 | When hints are added, different execution plans are used for query. The query result are different. |
| 118810 | 2025-08-11 3:19 | 2025-08-11 10:35 | MySQL Server: Optimizer | Verified (75 days) | S3 | 8.0.41, 8.0.43, 8.4.6 | Linux | x86 | he query result are inconsistent，when select difference indexes |
| 118808 | 2025-08-10 11:26 | 2025-08-11 7:00 | MySQL Server: Optimizer | Verified (75 days) | S2 | 9.4.0, 8.4.3, 8.4.6 | Any | Any | Different result with range scan and table scan in sql with subquery |
| 118806 | 2025-08-09 13:00 | 2025-08-11 5:39 | MySQL Server: Optimizer | Verified (75 days) | S3 | 8.0,9.0, 8.0.43, 8.4.6, 9.4.0 | Ubuntu | x86 | NULLIF with VARCHAR omits rows unexpectedly |
| 118798 | 2025-08-07 9:22 | 2025-08-08 7:36 | MySQL Server: Replication | Verified (78 days) | S1 | 8.0.40 | Ubuntu | Any | Replication Break in 8.0.40 salve when from 8.0.33 Master |
| 118797 | 2025-08-07 2:08 | 2025-08-07 9:17 | MySQL Server: Replication | Verified (79 days) | 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-21 8:59 | MySQL Server: Optimizer | Verified (80 days) | 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 (80 days) | 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-18 14:18 | MySQL Server: Documentation | Closed (68 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 (85 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-08-21 12:32 | MySQL Server: DML | Not a Bug (65 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-09-21 20:45 | MySQL Server: Prepared statements | Analyzing (87 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 (87 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 (88 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 |
| Showing all 151 (Edit, Save, CSV, Feed) |
