| Showing 1-90 of 5766 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119225 | 2025-10-24 9:11 | 2025-10-24 9:11 | MySQL Server | Open | S3 | 8.0.43 | Any | Any | weedout not work for rematerialized temptable |
| 119223 | 2025-10-24 3:16 | 2025-10-24 3:16 | MySQL Server | Open | S3 | 8.0.30 | Any | Any | The pfs_thread.processlist_id is set to NULL after using Srv_session |
| 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 |
| 119215 | 2025-10-23 9:16 | 2025-10-23 9:36 | MySQL Server | Open (2 days) | S3 | 8.0.30 | Any | Any | pfs_thread.processlist_id will be null after select group_replication_reset_member_actions() |
| 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. |
| 119200 | 2025-10-21 8:19 | 2025-10-21 8:19 | MySQL Server | Open | S3 | 8.4.x | Any | Any | make connection access sorting rule sane and predictable |
| 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 |
| 119174 | 2025-10-16 13:18 | 2025-10-23 12:22 | MySQL Server | Open (2 days) | S3 | 9.4.0 | Any | Any | unexpected value after changing Max to Min |
| 119172 | 2025-10-16 10:00 | 2025-10-16 10:00 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result for NOT BETWEEN When Date Interval Arithmetic Produces NULLs |
| 119171 | 2025-10-16 9:34 | 2025-10-16 9:34 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result for BETWEEN NULL AND NULL on a DECIMAL Column |
| 119170 | 2025-10-16 9:23 | 2025-10-16 9:23 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result with string = SOME (DECIMAL) |
| 119169 | 2025-10-16 9:08 | 2025-10-16 9:08 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result with DAYNAME() and DECIMAL |
| 119168 | 2025-10-16 8:47 | 2025-10-16 8:47 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent results for CHAR IN (subquery returning BIT) |
| 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) |
| 119165 | 2025-10-16 5:46 | 2025-10-16 5:46 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | unexpected value after changing Max to Min |
| 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 |
| 119154 | 2025-10-14 13:24 | 2025-10-14 13:24 | MySQL Server | Open | S1 | 8.4.6 | Any | Any | Incorrect BIT_COUNT value for TEXT column |
| 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) |
| 119147 | 2025-10-13 13:39 | 2025-10-13 13:39 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | >= SOME Operator Returns Incorrect Empty Set for TIMESTAMP Comparison |
| 119146 | 2025-10-13 12:53 | 2025-10-13 12:53 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | WHERE IN with Subquery Incorrectly Matches VARCHAR to DECIMAL via Implicit Casting |
| 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. |
| 119140 | 2025-10-13 8:01 | 2025-10-13 8:01 | MySQL Server | Open | S1 | 9.4.0 | Any | Any | DISTINCT works inconsistently in normal SELECT and prepared statement for 0 and -0 |
| 119139 | 2025-10-13 7:30 | 2025-10-13 7:37 | MySQL Server | Open (12 days) | S1 | 9.4.0 | Any | Any | Unexpected error `Incorrect DECIMAL value: '0' for column '' at row -1` |
| 119138 | 2025-10-13 3:45 | 2025-10-13 3:45 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result with BINARY EXISTS(...) IN (...) on TIMESTAMP column |
| 119137 | 2025-10-13 3:23 | 2025-10-13 3:23 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for ADDTIME expression |
| 119136 | 2025-10-13 3:14 | 2025-10-13 3:14 | MySQL Server | Open | S2 | 8.4.6 | Any | Any | Incompatible behavior between integer columns when comparing with datetime |
| 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. |
| 119129 | 2025-10-10 14:13 | 2025-10-10 14:13 | MySQL Server | Open | S1 | 9.4.0 | Any | Any | Unexpected error `BIGINT value is out of range in '--9223372036854775808'` |
| 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 |
| 119114 | 2025-10-08 7:54 | 2025-10-23 12:14 | MySQL Server | Open (2 days) | S3 | 9.4.0 | Any | Any | Column Value change caused by COUNT(column) --->COUNT(DISTINCT column) |
| 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 | |
| 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 |
| 119087 | 2025-09-28 5:54 | 2025-10-11 3:24 | MySQL Server | Open (14 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for subquery with BIGINT UNSIGNED |
| 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 |
| 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 |
| 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 |
| 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 | |
| 119005 | 2025-09-15 7:56 | 2025-10-11 3:23 | MySQL Server | Open (14 days) | S3 | localhost3306 | Any | Any | wizard import bug |
| 119004 | 2025-09-12 16:07 | 2025-10-11 3:23 | MySQL Server | Open (14 days) | S2 | 8.0+ | Any | Any | UNREACHABLE member is not expelled after the group_replication_member_expel_timeout delay |
| 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) |
| Showing 1-90 of 5766 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
