| Showing 1-90 of 768 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119490 | 2025-12-02 7:48 | 2025-12-02 7:57 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.41 | Any | Any | savepoint |
| 119480 | 2025-12-01 9:38 | 2025-12-03 9:43 | MySQL Server: InnoDB storage engine | Verified | S3 | Any | Any | Full table scans on primary keys, MySQL 8.0 performance degradation than MySQL 5.7. | |
| 119473 | 2025-11-29 8:17 | 2025-11-30 15:03 | MySQL Server: InnoDB storage engine | Open (4 days) | S3 | 8.0.41 | Any | Any | InnoDB Mutex Deadlock Cause Mysql Crash |
| 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 (6 days) | S2 | 5.7 | Any | Any | import tablespace cost too long |
| 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 |
| 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 |
| 119396 | 2025-11-14 10:58 | 2025-11-14 15:12 | MySQL Server: InnoDB storage engine | Open (19 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 |
| 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() |
| 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 |
| 119300 | 2025-11-04 10:46 | 2025-11-04 10:56 | MySQL Server: InnoDB storage engine | Open (29 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 (26 days) | S2 | 9.3.0, 9.5.0 | Any | Any | SELECT statement is affected by concurrent transaction under Read Uncommitted |
| 119285 | 2025-11-01 6:16 | 2025-11-01 6:25 | MySQL Server: InnoDB storage engine | Open (32 days) | S5 | 8.0.44 | Any | Any | resue read-view for read_only mode |
| 119280 | 2025-10-31 11:55 | 2025-11-12 11:08 | MySQL Server: InnoDB storage engine | Open (21 days) | S2 | 9.5.0 | Any | Any | INSTANT ADD succeeds even when the size of a row crosses row_size_limit |
| 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 (36 days) | S3 | 9.5.0 | MacOS (26.0.1) | ARM | innodb.tablespace_encrypt_9 crashing the server with assertion failure |
| 119235 | 2025-10-27 2:47 | 2025-11-10 14:16 | MySQL Server: InnoDB storage engine | Open (23 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 |
| 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 |
| 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. |
| 119133 | 2025-10-11 6:55 | 2025-10-11 6:56 | MySQL Server: InnoDB storage engine | Open (53 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. |
| 119073 | 2025-09-26 3:29 | 2025-10-01 13:59 | MySQL Server: InnoDB storage engine | Verified (65 days) | S3 | 9.4.0 8.4.6 | Any | x86 | Inconsistent Type Conversion Behavior for TIMESTAMP Column Based on UNIQUE Constraint |
| 119063 | 2025-09-24 3:45 | 2025-10-01 14:04 | MySQL Server: InnoDB storage engine | Verified (65 days) | S3 | 8.0.43 | Any | Any | Unused variable 'fk_max_recusive_level' |
| 119043 | 2025-09-19 9:14 | 2025-09-23 2:39 | MySQL Server: InnoDB storage engine | Verified (71 days) | S3 | 8.0.41 | Any | Any | in certain situations the table space will be greatly wasted |
| 118984 | 2025-09-10 7:05 | 2025-09-15 16:01 | MySQL Server: InnoDB storage engine | Verified (82 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 (83 days) | S3 | 8.0.43 | Any | Any | PCursor::move_to_next_block is not functioning as expected |
| 118923 | 2025-09-02 7:49 | 2025-09-04 11:46 | MySQL Server: InnoDB storage engine | Verified (91 days) | S2 | 8.4, 8.0.22, 9.4.0 | Any | Any | Abnormal read phenomena are observed under MySQL's Read Committed isolation level |
| 118872 | 2025-08-21 5:01 | 2025-08-21 6:31 | MySQL Server: InnoDB storage engine | Verified (104 days) | S3 | 8.0.40 | Any | Any | Innodb_data_written lacks statistics for double-write files |
| 118867 | 2025-08-20 18:35 | 2025-09-01 11:12 | MySQL Server: InnoDB storage engine | Verified (104 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 (104 days) | S3 | 9.4 | Any | Any | Contribution: Optimize hash_table_locks |
| 118864 | 2025-08-20 18:17 | 2025-09-16 1:31 | MySQL Server: InnoDB storage engine | Verified (104 days) | S3 | 9.4 | Any | Any | Contribution: Optimize undo spaces lock |
| 118842 | 2025-08-14 8:50 | 2025-09-22 3:27 | MySQL Server: InnoDB storage engine | Verified (72 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 |
| 118820 | 2025-08-13 7:39 | 2025-08-20 6:01 | MySQL Server: InnoDB storage engine | Verified (106 days) | S2 | 8.0.41 | Any | Any | AHI results the mysqld hung and assertion failure: btr0sea.cc:295:sleep_counter < 60000 |
| 118723 | 2025-07-26 11:54 | 2025-07-28 4:29 | MySQL Server: InnoDB storage engine | Verified (128 days) | S5 | 8.0.42 | Any | Any | optimize for innodb insert |
| 118705 | 2025-07-23 8:06 | 2025-08-13 11:06 | MySQL Server: InnoDB storage engine | Verified (131 days) | S2 | 8.0 | Any | Any | when call que_eval_sql, may crash. |
| 118695 | 2025-07-22 7:11 | 2025-07-23 7:33 | MySQL Server: InnoDB storage engine | Verified (133 days) | S3 | 8.0 | Any | Any | This if condition seems to be useless in btr0cur.cc:1398 |
| 118693 | 2025-07-22 5:52 | 2025-07-22 6:34 | MySQL Server: InnoDB storage engine | Verified (134 days) | S3 | 8.0.42 | Any | Any | Increasing length of varchar field should be inplace. |
| 118681 | 2025-07-18 2:54 | 2025-07-18 5:22 | MySQL Server: InnoDB storage engine | Verified (138 days) | S5 | 8.0.42 | Any | Any | Reduce the locking scope of dict_sys_mutex in dict_stats_drop_table |
| 118624 | 2025-07-10 2:47 | 2025-07-10 8:15 | MySQL Server: InnoDB storage engine | Verified (146 days) | S1 | 8.3.0, 8.0.42, 8.3.0, 8.4.5, 9.3.0 | Any | Any | Wrong result when icp(push a 'like condition' into engine) |
| 118594 | 2025-07-07 14:16 | 2025-07-07 14:58 | MySQL Server: InnoDB storage engine | Verified (149 days) | S2 | 8.0.42 | Any | Any | In-place ALTER TABLE ... ADD FOREIGN KEY can sometimes fails with unwarranted error or even crashes |
| 118516 | 2025-06-24 10:42 | 2025-07-03 18:36 | MySQL Server: InnoDB storage engine | Verified (153 days) | S3 | 8.0.39 | Any | Any | Unexpected blocked statement when different select statements are executed |
| 118515 | 2025-06-24 9:08 | 2025-07-01 4:35 | MySQL Server: InnoDB storage engine | Verified (156 days) | S2 | 8.4, 8.4.5 | Any | Any | Contribution by Tencent: trx_cleanup_at_db_startup did not clean up trx_sys->shards |
| 118411 | 2025-06-10 15:52 | 2025-07-21 11:44 | MySQL Server: InnoDB storage engine | Verified (135 days) | S2 | 8.0.37, 8.0.42 | CentOS | x86 | Performance degradation in write workload after rebuilding table with row_format=compressed |
| 118403 | 2025-06-09 17:10 | 2025-06-20 10:13 | MySQL Server: InnoDB storage engine | Verified (166 days) | S3 | 8.0.37, 8.0.42 | Any | Any | innodb_fill_factor is not honored for InnoDB Compressed Tables |
| 118363 | 2025-06-04 18:00 | 2025-06-16 12:33 | MySQL Server: InnoDB storage engine | Verified (175 days) | S3 | mysql-8.0.41 | Any | Any | Another Potential Optimization in row_ins_sec_index_entry_low() |
| 118359 | 2025-06-04 13:43 | 2025-06-16 12:33 | MySQL Server: InnoDB storage engine | Verified (175 days) | S2 | mysql-8.0.41 | Any | Any | False-negative result in row_vers_impl_x_locked_low() — may miss identifying the active transaction on a secondary rec |
| 118358 | 2025-06-04 12:04 | 2025-07-13 10:14 | MySQL Server: InnoDB storage engine | Verified (152 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | Startup without Signs of Progress when Rolling-Back Big Transaction. |
| 118355 | 2025-06-04 7:41 | 2025-06-10 13:59 | MySQL Server: InnoDB Plugin storage engine | Verified (176 days) | S3 | 8.0.42 | Any | Any | Temporary file write failure when creating an index |
| 118335 | 2025-06-03 7:50 | 2025-07-07 14:05 | MySQL Server: InnoDB storage engine | Verified (149 days) | S5 | 9.3.0 | Any | Any | drop big table affect performance when general space used |
| 118302 | 2025-05-29 16:46 | 2025-11-03 20:17 | MySQL Server: InnoDB storage engine | Verified (187 days) | S3 | 9.0.0, 9.3.0 | Any | Any | Contribution: Adding \'sb\' instruction to spin_delay() for ARM v8.5 onward |
| 118299 | 2025-05-29 6:57 | 2025-08-21 2:18 | MySQL Server: InnoDB storage engine | Verified (104 days) | S2 | 8.0.42, 8.4.5 | Any | Any | Multi-valued Index on Composite Key Returns Incomplete Results for Rows with Empty JSON Array('[]') |
| 118265 | 2025-05-25 23:12 | 2025-07-09 15:42 | MySQL Server: InnoDB storage engine | Verified (169 days) | S1 | 9.3.0 | MacOS (15.4.1 (24E263)) | x86 (Quad-Core Intel Core i7) | mysqld hangs durning startup |
| 118172 | 2025-05-13 3:54 | 2025-09-21 20:45 | MySQL Server: InnoDB storage engine | Analyzing (133 days) | S3 | 8.0.31 | Windows | x86 ( x86_64) | 猜测间隙锁可以加到普通索引上，导致只能防止插入操作而不能防止select ...for update操作 |
| 118121 | 2025-05-06 14:40 | 2025-05-13 8:47 | MySQL Server: InnoDB storage engine | Verified (204 days) | S3 | 8.0.37, 8.0.42 | Any | Any | lob pages leak when mysqld crashed |
| 118054 | 2025-04-24 16:23 | 2025-05-07 15:55 | MySQL Server: InnoDB storage engine | Verified (211 days) | S5 | Any | Any | Potential optimization in row_ins_sec_index_entry_low(): avoid second btr_cur_search_to_nth_level() under certain condit | |
| 117962 | 2025-04-13 15:19 | 2025-04-13 17:26 | MySQL Server: InnoDB storage engine | Verified (234 days) | S3 | 8.0.37, 8.0.41, 9.2.0 | Any | Any | ibd2sdi failed when table COMPRESSION='lz4' |
| 117943 | 2025-04-11 8:07 | 2025-05-13 12:31 | MySQL Server: InnoDB storage engine | Verified (211 days) | S3 | 8.4.4, 9.2.0 | Any | Any | Startup ibd-file validation uses too much CPU threads |
| 117898 | 2025-04-07 8:26 | 2025-09-10 9:54 | MySQL Server: InnoDB storage engine | Verified (216 days) | S3 | 8.0.41 | Any | Any | User Records may be skipped when Persistent Cursor restores Infimum and Supremum Record |
| 117835 | 2025-03-31 10:44 | 2025-05-12 12:18 | MySQL Server: InnoDB storage engine | Verified (205 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Non Repeatable Read WITH CONSISTENT SNAPSHOT |
| 117778 | 2025-03-24 10:23 | 2025-05-12 9:23 | MySQL Server: InnoDB storage engine | Verified (254 days) | S3 | 8.0, 8.4, 9.2 | Any | Any | AHI hash table memory is invisible to Performance Schema |
| 117733 | 2025-03-18 2:59 | 2025-03-21 1:13 | MySQL Server: InnoDB storage engine | Verified (260 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Dirty reads due to isolation level settings |
| 117717 | 2025-03-16 5:05 | 2025-03-16 11:41 | MySQL Server: InnoDB storage engine | Verified (262 days) | S2 | 8.0.41, 8.4.4, 9.2.0 | Any | Any | Import Tablespace Fails Due to Inconsistent max_prefix in dict_col_t After Dropping Index |
| 117533 | 2025-02-20 13:37 | 2025-03-27 9:50 | MySQL Server: InnoDB storage engine | Verified (251 days) | S5 | 8.0.41 | Any | Any | The performance is poor when concurrently reading undo records |
| 117498 | 2025-02-18 9:37 | 2025-03-27 13:44 | MySQL Server: InnoDB storage engine | Verified (251 days) | S5 | 8.0.41 | Any | Any | Traversing a relatively long undo-chain will seriously affect write performance |
| 117448 | 2025-02-12 9:22 | 2025-11-14 9:54 | MySQL Server: InnoDB storage engine | Verified (294 days) | S5 | 8.0 | Any | Any | When a large number of undo logs accumulate, reading the undo logs during the undo purge process may become a bottleneck |
| 117436 | 2025-02-11 7:22 | 2025-04-29 10:27 | MySQL Server: InnoDB storage engine | Verified (231 days) | S2 | 8.0 | Any | Any | PCursor::move_to_next_block may skip records incorrectly |
| 117256 | 2025-01-21 13:19 | 2025-01-28 18:24 | MySQL Server: InnoDB storage engine | Verified (309 days) | S2 | 8.4.4 | Any | Any | Repeating uncaused error "Column cannot be null" after single error on table with trigger |
| 117237 | 2025-01-19 4:13 | 2025-01-21 11:41 | MySQL Server: InnoDB storage engine | Verified (316 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Duplicate Error in DDL Row Log Apply |
| 117231 | 2025-01-17 20:50 | 2025-01-27 6:57 | MySQL Server: InnoDB storage engine | Verified (310 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Wrong SDI after upgrade from 8.0.23 because Bug#98501 (Exchanging partition does not update SDI). |
| 117189 | 2025-01-13 8:26 | 2025-01-13 8:40 | MySQL Server: InnoDB storage engine | Verified (324 days) | S3 | 8.0.39, 8.0.40 | Any | Any | InnoDB index stats many orders of magnitude wrong |
| 117099 | 2025-01-02 18:20 | 2025-01-08 15:18 | MySQL Server: InnoDB storage engine | Verified (329 days) | S2 | 8.0.40 | Any | Any | Variable innodb_ddl_buffer_size does not limit memory usage in the first phase of an ALTER TABLE |
| 116934 | 2024-12-11 2:04 | 2024-12-11 5:33 | MySQL Server: InnoDB storage engine | Verified (357 days) | S3 | 8.0,8.4 | Any | Any | Recovery should abort immediatly if meet corrupt log |
| 116933 | 2024-12-11 1:47 | 2024-12-11 5:33 | MySQL Server: InnoDB storage engine | Verified (357 days) | S3 | 8.0,8.4 | Any | Any | Function recv_single_rec doesn't handle corrupt_log correctly |
| 116878 | 2024-12-04 17:10 | 2025-02-21 12:40 | MySQL Server: InnoDB storage engine | Verified (299 days) | S5 | 8.0.21 and above | Any | Any | False sharing with hardcoded cache line size |
| 116813 | 2024-11-28 2:57 | 2025-07-11 2:28 | MySQL Server: InnoDB storage engine | Verified (145 days) | S5 | 8.0.40, 8.0.42 | Any | Any | The transaction commit takes a long time even if it doesn't affect any rows |
| 116794 | 2024-11-27 4:10 | 2024-11-28 14:27 | MySQL Server: InnoDB storage engine | Verified (370 days) | S3 | 8.0 | Any | Any | Blobs in dropped columns will be residual after a update. |
| 116793 | 2024-11-27 3:51 | 2024-11-27 7:14 | MySQL Server: InnoDB storage engine | Verified (371 days) | S2 | 8.0.40 | Any | Any | AHI crash : ut_a(old_index != nullptr) |
| 116761 | 2024-11-24 4:46 | 2024-11-26 7:51 | MySQL Server: InnoDB storage engine | Verified (372 days) | S3 | 8.0.40 | Any | Any | Page tracking stops working when disk is full |
| 116760 | 2024-11-23 13:44 | 2025-07-28 5:11 | MySQL Server: InnoDB storage engine | Verified (373 days) | S2 | 8.0.40,8.4.3,9.1.0 | Any | Any | Page deadlock occured when searching BTREE after nullable cols dropped by INSTAN |
| 116715 | 2024-11-19 17:03 | 2024-11-20 17:23 | MySQL Server: InnoDB storage engine | Verified (378 days) | S2 | 9, 8.4, 8.0 | Any | Any | Optimize Normal Startup with Many Tables. |
| 116714 | 2024-11-19 16:04 | 2024-11-21 14:17 | MySQL Server: InnoDB storage engine | Verified (378 days) | S3 | 8.0 | Any | Any | With 8000 to 15,999 Tablespaces, MySQL Startup Spawns one Useless Sub-Thread. |
| 116713 | 2024-11-19 15:57 | 2024-11-21 14:15 | MySQL Server: InnoDB storage engine | Verified (378 days) | S2 | 9.0 | Any | Any | Function rename_partition_files should not be in MySQL 9, and more. |
| 116709 | 2024-11-19 11:59 | 2024-11-19 12:22 | MySQL Server: InnoDB storage engine | Verified (379 days) | S3 | 9.1.0 | Any | Any | scripts/mysql_system_tables.sql still treating InnoDB as an optional SE |
| 116647 | 2024-11-13 19:28 | 2025-04-25 16:55 | MySQL Server: InnoDB storage engine | Verified (384 days) | S3 | 8.4.2,9.0 | Any | Any | Bufferpool Index Stats are not decremented on btr_page_free |
| 116627 | 2024-11-12 10:30 | 2024-11-12 18:57 | MySQL Server: InnoDB storage engine | Verified (386 days) | S3 | 8.0 | Any | Any | innodb print tons of partial read in error log |
| 116626 | 2024-11-12 9:55 | 2024-11-12 10:02 | MySQL Server: InnoDB storage engine | Verified (386 days) | S3 | 8.0.40 | Any | Any | Lack of error handling when temp tablespace truncate fails |
| 116574 | 2024-11-07 3:20 | 2024-11-07 15:18 | MySQL Server: InnoDB storage engine | Verified (391 days) | S3 | 8.0 | Any | Any | btr_page_reorganize_low may cause crash recovery failure |
| 116504 | 2024-10-30 12:52 | 2024-11-07 15:25 | MySQL Server: InnoDB storage engine | Verified (391 days) | S3 | 8.0 | Linux | Any | Insert into punch hole compression table drop of zero randomly |
| 116502 | 2024-10-30 4:31 | 2025-01-20 6:58 | MySQL Server: InnoDB storage engine | Verified (398 days) | S2 | 8.0.40 | Any | Any | Duplicate Detection Flaw for NULL Values in UK During DDL Rollback Operations |
| 116501 | 2024-10-29 13:27 | 2024-11-07 15:22 | MySQL Server: InnoDB storage engine | Verified (391 days) | S3 | 8.0 | Linux | Any | Compression not work with file system which sector size is not 512 |
| Showing 1-90 of 768 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
