| Showing all 106 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119075 | 2025-09-26 6:42 | 2025-10-11 3:23 | MySQL Server: Connection Handling | Open (35 days) | S3 | Windows | Any | Issues with home page | |
| 119094 | 2025-09-29 13:03 | 2025-10-11 3:24 | MySQL Server: Optimizer | Open (35 days) | S3 | Any | Any | Performance optimization patches | |
| 119237 | 2025-10-27 5:02 | 2025-10-27 5:02 | MySQL Server | Open | S3 | Any | Any | my sql workbench | |
| 119356 | 2025-11-10 16:20 | 2025-11-10 16:42 | MySQL Server: General | Open | S3 | Any | Any | Contribution: Fix NUL characters in FORMAT() output | |
| 119378 | 2025-11-12 16:41 | 2025-11-12 16:41 | MySQL Server | Open | S3 | Any | Any | Bug issue | |
| 119394 | 2025-11-14 9:02 | 2025-11-14 9:02 | MySQL Server: Optimizer | Open (1 day) | S3 | Any | Any | Join order specified in the hint is different, the query results are incorrect. | |
| 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 |
| 71334 | 2014-01-09 20:26 | 2025-09-11 8:32 | MySQL Server | Open (65 days) | S3 | 5.6.15-enterprise-commercial-advanced-lo | Solaris | Any | Small join on composite PK not performing well versus IN-list |
| 119304 | 2025-11-05 2:08 | 2025-11-05 2:12 | MySQL Server | Open (10 days) | S3 | 5.7，8.0 | Any | Any | SQL_LOAD-xxxx file exists when the SQL thread checks permissions, causing the SQL thread fail to start |
| 119392 | 2025-11-14 7:29 | 2025-11-14 8:06 | MySQL Server: Optimizer | Open | S2 | 8.0 | Any | Any | Use-after-free of TABLE::read_set in DynamicRangeIterator |
| 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() |
| 119215 | 2025-10-23 9:16 | 2025-10-23 9:36 | MySQL Server | Open (23 days) | S3 | 8.0.30 | Any | Any | pfs_thread.processlist_id will be null after select group_replication_reset_member_actions() |
| 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 |
| 118814 | 2025-08-12 3:47 | 2025-10-11 3:22 | MySQL Server: Windows | Open (35 days) | S2 | 8.0.39 | Windows | Any | I/O error while writing to file: .\#ib_16384_0.dblwr |
| 119396 | 2025-11-14 10:58 | 2025-11-14 15:12 | MySQL Server: InnoDB storage engine | Open (1 day) | S1 | 8.0.40 | Any | Any | Increase in undo log size , slower purging and no truncation even after restart |
| 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. |
| 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 |
| 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. |
| 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. |
| 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. |
| 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 |
| 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 |
| 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. |
| 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 |
| 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. |
| 119164 | 2025-10-16 3:35 | 2025-11-05 1:42 | MySQL Server: DML | Open (10 days) | S3 | 8.0.41 | Any | Any | CASE expression evaluation incorrectly validates REGEXP_INSTR arguments when branch is not executed |
| 119241 | 2025-10-27 11:25 | 2025-10-27 11:29 | MySQL Server: DDL | Open (19 days) | S2 | 8.0.41 | Any | Any | Exception when creating index instance |
| 119305 | 2025-11-05 4:02 | 2025-11-05 4:03 | MySQL Server: Optimizer | Open | S3 | 8.0.41 | Linux | x86 | The query results of enabling and disabling materialization are inconsistent. |
| 119313 | 2025-11-06 3:03 | 2025-11-06 3:03 | MySQL Server: Optimizer | Open | S3 | 8.0.41 | Any | Any | BETWEEN clause returns incorrect results when comparing numeric literal with DATETIME columns |
| 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 |
| 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)` |
| 119385 | 2025-11-13 9:41 | 2025-11-13 9:41 | MySQL Server | Open | S3 | 8.0.41 | Any | Any | After replacing the expressions inside BETWEEN ... AND with constants, the results become inconsistent. |
| 119133 | 2025-10-11 6:55 | 2025-10-11 6:56 | MySQL Server: InnoDB storage engine | Open (35 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. |
| 119309 | 2025-11-05 13:37 | 2025-11-05 16:31 | MySQL Server | Open (10 days) | S3 | 8.0.42 + | Any | Any | An insert prepared statement fails to write across partitions |
| 119101 | 2025-10-02 4:44 | 2025-10-11 3:25 | MySQL Server: Logging | Open (35 days) | S3 | 8.0.43 | Any | Any | Incorrect query_time is logged in the slow log when adjusting system time backward |
| 119233 | 2025-10-24 19:37 | 2025-10-24 19:37 | MySQL Server: Connection Handling | Open | S3 | 8.0.43 | Windows (Microsoft Windows 10 Home) | Any | workbench crash when connecting to database |
| 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 |
| 119381 | 2025-11-13 8:14 | 2025-11-13 8:14 | MySQL Server | Open | S2 | 8.0.43, 9.4.0 | Any | Any | Contribution by Tencent: Duplicate auto-increment values happened with partitioned tables and uk conflict |
| 119276 | 2025-10-31 6:05 | 2025-10-31 6:05 | MySQL Server | Open | S3 | 8.0.44 | Any | Any | ALTER TABLE ANALYZE PARTITION statement causes incorrect results in the mysql.table_table_stats |
| 119285 | 2025-11-01 6:16 | 2025-11-01 6:25 | MySQL Server: InnoDB storage engine | Open (14 days) | S5 | 8.0.44 | Any | Any | resue read-view for read_only mode |
| 119300 | 2025-11-04 10:46 | 2025-11-04 10:56 | MySQL Server: InnoDB storage engine | Open (11 days) | S3 | 8.0.44 | Any | Any | Debug assertion failure: field.field_no < dict_index_get_n_fields(index) |
| 119004 | 2025-09-12 16:07 | 2025-10-11 3:23 | MySQL Server | Open (35 days) | S2 | 8.0+ | Any | Any | UNREACHABLE member is not expelled after the group_replication_member_expel_timeout delay |
| 119395 | 2025-11-14 9:20 | 2025-11-14 9:20 | MySQL Server: Storage Engines | Open | S3 | 8.4 | Any | Any | WL #12527 may cause performance jitter under heavy write workloads |
| 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. |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 119273 | 2025-10-30 14:14 | 2025-10-30 14:14 | MySQL Server | Open (16 days) | S2 | 8.4.6 | Red Hat (5.14.0-570.25.1.el9_6.x86_64) | x86 | disk-based Temptable gives "Table './tmp/#sql2730_2b2_4' doesn't exist" |
| 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 |
| 119312 | 2025-11-05 17:30 | 2025-11-05 17:30 | MySQL Server | Open | S3 | 8.4.x | Any | Any | `start replica` command adds an invalid record to mysql.slave_master_info |
| 119367 | 2025-11-12 6:18 | 2025-11-12 6:18 | MySQL Server: DML | Open | S3 | 9.1.0 | Any | Any | query function coalesce occur error 'Cannot convert string 'xxx from binary to utf8mb4' |
| 119088 | 2025-09-28 6:31 | 2025-10-11 3:24 | MySQL Server: Optimizer | Open (35 days) | S3 | 9.2,9.4 | Any | Any | sort with limit in hypergraph gets wrong result |
| 119290 | 2025-11-02 15:06 | 2025-11-07 7:43 | MySQL Server: InnoDB storage engine | Open (8 days) | S2 | 9.3.0, 9.5.0 | Any | Any | SELECT statement is affected by concurrent transaction under Read Uncommitted |
| 119110 | 2025-10-07 5:19 | 2025-10-11 3:25 | MySQL Server: Optimizer | Open (35 days) | S2 | 9.4.0 | Linux | x86 | Incorrect NULL filtering in CTE with UNION ALL over view containing LEFT JOIN on FALSE |
| 119111 | 2025-10-07 5:22 | 2025-10-11 3:21 | MySQL Server: Optimizer | Open (35 days) | S3 | 9.4.0 | Any | Any | Column Value change caused by MIN(column) --->-MAX(-column) |
| 119114 | 2025-10-08 7:54 | 2025-10-23 12:14 | MySQL Server | Open (23 days) | S3 | 9.4.0 | Any | Any | Column Value change caused by COUNT(column) --->COUNT(DISTINCT column) |
| 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'` |
| 119139 | 2025-10-13 7:30 | 2025-10-13 7:37 | MySQL Server | Open (33 days) | S1 | 9.4.0 | Any | Any | Unexpected error `Incorrect DECIMAL value: '0' for column '' at row -1` |
| 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 |
| 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 |
| 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 |
| 119174 | 2025-10-16 13:18 | 2025-10-23 12:22 | MySQL Server | Open (23 days) | S3 | 9.4.0 | Any | Any | unexpected value after changing Max to Min |
| 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 |
| 119248 | 2025-10-27 16:46 | 2025-10-27 16:54 | MySQL Server: Security: Privileges | Open (19 days) | S3 | 9.4.0 | Any | Any | CHECK TABLE command can be executed by users with the table-level GRANT OPTION privilege |
| 119327 | 2025-11-07 7:52 | 2025-11-07 7:52 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | after adding an index ,the result return different |
| 119348 | 2025-11-10 11:01 | 2025-11-10 11:01 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | Incorrect row number after changing having clause |
| 119349 | 2025-11-10 12:06 | 2025-11-12 4:46 | MySQL Server | Open (3 days) | S3 | 9.4.0 | Any | Any | Incorrect String Comparison with MyISAM BIT Column in IN Subquery |
| 119350 | 2025-11-10 12:14 | 2025-11-10 12:14 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | Column name change after changing having clause |
| 119351 | 2025-11-10 13:00 | 2025-11-10 13:00 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | Index caused different result |
| 119352 | 2025-11-10 13:11 | 2025-11-10 13:11 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | row number become less after changing where clause |
| 119353 | 2025-11-10 14:30 | 2025-11-10 14:30 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | Column Value change after removing DISTINCT in query |
| 119386 | 2025-11-13 11:44 | 2025-11-13 12:23 | MySQL Server | Open (2 days) | S1 | 9.4.0 | Any | Any | unexpected error "Can't write; duplicate key in table '/tmp/#sql1_372_1'" |
| 119087 | 2025-09-28 5:54 | 2025-10-11 3:24 | MySQL Server | Open (35 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for subquery with BIGINT UNSIGNED |
| 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 |
| 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 |
| 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 |
| 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 |
| 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) |
| 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 |
| 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) |
| 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 |
| 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 |
| 119340 | 2025-11-10 7:58 | 2025-11-10 7:58 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for RLIKE when INSERT() uses CURRENT_USER() as an argument. |
| 119343 | 2025-11-10 8:40 | 2025-11-10 8:40 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | NOT BETWEEN evaluates incorrectlywhen FROM_UNIXTIME operates on a FLOAT column |
| 119345 | 2025-11-10 9:21 | 2025-11-10 9:21 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Presence of UNIQUE index on INT column causes inconsistent results for IF with ANY subquery |
| 119346 | 2025-11-10 9:43 | 2025-11-10 9:43 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | CASE expression evaluates incorrectly |
| 119347 | 2025-11-10 10:43 | 2025-11-10 10:43 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | IN predicate incorrectly evaluates RADIANS() and TINYINT with key |
| 119354 | 2025-11-10 15:51 | 2025-11-10 15:51 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | IN subquery evaluates incorrectly when using IFNULL and CAST AS DATETIME |
| 119355 | 2025-11-10 16:15 | 2025-11-10 16:15 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | BETWEEN ... AND NULL evaluates incorrectly with bitwise shift |
| 119364 | 2025-11-12 3:01 | 2025-11-12 3:01 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect Evaluation of = ANY Subquery with NULL on Indexed DECIMAL Column |
| 119365 | 2025-11-12 3:14 | 2025-11-12 3:17 | MySQL Server | Open (3 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect NOT IN Evaluation for NULL on Indexed TEXT Column |
| 119370 | 2025-11-12 10:07 | 2025-11-12 10:07 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | FLOAT Value Returned by CASE Statement Evaluates Incorrectly in Bitwise Operation |
| 119235 | 2025-10-27 2:47 | 2025-11-10 14:16 | MySQL Server: InnoDB storage engine | Open (5 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 |
| 119253 | 2025-10-28 4:57 | 2025-10-28 4:58 | MySQL Server: InnoDB storage engine | Open (18 days) | S3 | 9.5.0 | MacOS (26.0.1) | ARM | innodb.tablespace_encrypt_9 crashing the server with assertion failure |
| 119280 | 2025-10-31 11:55 | 2025-11-12 11:08 | MySQL Server: InnoDB storage engine | Open (3 days) | S2 | 9.5.0 | Any | Any | INSTANT ADD succeeds even when the size of a row crosses row_size_limit |
| 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 |
| 119391 | 2025-11-14 7:19 | 2025-11-14 7:19 | MySQL Server | Open | S3 | 9.5.0 | Linux (mysqld --no-defaults --help failed) | x86 | /mysql-9.5.0/cmake/info_bin.cmake:37 (CREATE_INFO_BIN) |
| 119005 | 2025-09-15 7:56 | 2025-10-11 3:23 | MySQL Server | Open (35 days) | S3 | localhost3306 | Any | Any | wizard import bug |
| 119097 | 2025-09-30 9:04 | 2025-10-11 3:24 | MySQL Server: Optimizer | Open (35 days) | S2 | MySQL 8.4.6 | Windows | Other (x64) | STRAIGHT_JOIN returns different results compared to INNER JOIN with identical conditions |
| 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 |
| 119270 | 2025-10-30 9:12 | 2025-10-30 16:03 | MySQL Server: Replication | Open | S3 | MySQL8.0,5.7 | Any | Any | Single-statement transactions can cause latency spikes on the replica |
| Showing all 106 (Edit, Save, CSV, Feed) |
