| Showing all 179 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 120943 | 2026-07-16 5:53 | 2026-07-16 5:53 | MySQL Server: Optimizer | Open | S2 | 8.0.42, 8.0.44, 8.0.46, 8.4.10 | Any (Official mysql Docker images (Linux/aarch64)) | Any | Semijoin duplicate-weedout discards valid rows when fed by a rowid filesort |
| 120941 | 2026-07-16 2:34 | 2026-07-16 3:21 | MySQL Server: InnoDB storage engine | Open | S3 | 8.4.7-7 | Any | Any | Contribution by ByteDance RDS MySQL team: InnoDB may permanently skip an undo record during shutdown |
| 120935 | 2026-07-15 10:45 | 2026-07-15 10:45 | MySQL Server: Optimizer | Open | S2 | 9.5.0 | Any | Any | Duplicate equivalent EXISTS predicate is not eliminated and causes a much slower execution plan |
| 120933 | 2026-07-15 9:54 | 2026-07-15 9:54 | MySQL Server: InnoDB storage engine | Open | S3 | 8.4.7-7 | Any | Any | mysqld crash during shutdown |
| 120929 | 2026-07-14 16:35 | 2026-07-14 16:35 | MySQL Server: InnoDB storage engine | Open | S3 | 9.7.1 | Any | Any | LATEST FOREIGN KEY ERROR is not printed in SHOW ENGINE INNODB STATUS |
| 120926 | 2026-07-14 14:07 | 2026-07-14 14:07 | MySQL Server: Optimizer | Open | S3 | 8.4.10 | Any | Any | Wrong result with CTE, AVG(DECIMAL), GROUP BY, comparison, and UNION |
| 120925 | 2026-07-14 14:04 | 2026-07-14 14:04 | MySQL Server: Optimizer | Open | S3 | 8.4.10 | Any | Any | Wrong result with VIEW, GROUP_CONCAT, JSON_QUOTE, UPPER, and UNION |
| 120924 | 2026-07-14 13:59 | 2026-07-14 13:59 | MySQL Server: Optimizer | Open | S3 | 8.4.10 | Any | Any | Wrong result with VIEW, GROUP_CONCAT, JSON_QUOTE, HEX, LOWER, and self JOIN |
| 120923 | 2026-07-14 13:53 | 2026-07-14 13:53 | MySQL Server: Optimizer | Open | S3 | 8.4.10 | Any | Any | Wrong result with CTE, UNION ALL, GROUP BY, and COUNT() |
| 120921 | 2026-07-14 13:51 | 2026-07-14 13:51 | MySQL Server: Optimizer | Open | S3 | 8.4.10 | Any | Any | Wrong result with VIEW, GROUP BY, STDDEV(DOUBLE), and IN subquery |
| 120912 | 2026-07-13 15:04 | 2026-07-14 6:52 | MySQL Server: Security: Privileges | Open | S3 | 8.4.10 | Any | Any | REQUIRE SUBJECT/ISSUER authentication fails on OpenSSL 3.x (RHEL 9) due to X509_NAME_oneline() escaping + as \+ |
| 120904 | 2026-07-13 9:59 | 2026-07-13 9:59 | MySQL Server: Optimizer | Open | S3 | 8.4.10 | Any | Any | Wrong/inconsistent result between VIEW and CTE with UNION ALL, EXISTS, and integer division |
| 120900 | 2026-07-13 8:03 | 2026-07-15 7:51 | MySQL Server: Optimizer | Open (1 day) | S2 | 9.5.0 | Any | Any | Redundant OR FALSE Predicate Causes a Much Slower Plan |
| 120899 | 2026-07-13 7:34 | 2026-07-13 7:34 | MySQL Server: Optimizer | Open | S2 | 9.5.0 | Any | Any | An equivalent query becomes much slower after a redundant duplicated IN-subquery predicate is added |
| 120896 | 2026-07-08 23:11 | 2026-07-08 23:11 | MySQL Server: Logging | Open | S3 | 8.4.10 | Any | Any | General query log inconsistency: SECURITY DEFINER function/trigger bodies logged as definer (host %); SP body not logged |
| 120859 | 2026-07-03 9:14 | 2026-07-03 9:20 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.30 | Any | Any | mysqld crashes with SIGSEGV in temptable::Block::can_accommodate() due to shared_block_pool use-after-free race conditio |
| 120835 | 2026-07-02 14:24 | 2026-07-02 14:24 | MySQL Server: InnoDB storage engine | Open | S3 | 9.7.0 | Any | Any | UBSan error on log0log.log_writer test |
| 120829 | 2026-07-01 22:32 | 2026-07-01 22:32 | MySQL Server: Optimizer | Open | S5 | 8.4.10, but not 9.7 | Any | Any | Functional index intermittently unusable under concurrent load: possible_keys=NULL, FORCE INDEX silently ignored |
| 120827 | 2026-07-01 12:25 | 2026-07-01 12:25 | MySQL Server: InnoDB storage engine | Open | S5 | 8.0.45 | Linux | Any | Clarification on deadlock during concurrent INSERT into secondary index without preceding locking reads |
| 120804 | 2026-06-28 13:41 | 2026-06-28 21:27 | MySQL Server: InnoDB storage engine | Open | S1 | mysql 8.4.9 | Ubuntu (20.04) | x86 | Unexpected deadlock under RR/SER when updating a row already locked by the same transaction |
| 120799 | 2026-06-28 8:09 | 2026-06-29 17:29 | MySQL Server: InnoDB storage engine | Open (17 days) | S2 | mysql 8.4.9 | Ubuntu (20.04) | x86 | SELECT ... LOCK IN SHARE MODE returns different row sets depending on index choice under RC/RU |
| 120774 | 2026-06-25 12:16 | 2026-06-25 12:16 | MySQL Server: Replication | Open | S2 | 8.4.8 | Linux | Any | replication worker thread dealock |
| 120758 | 2026-06-24 6:13 | 2026-07-14 14:43 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Add logging for redo log scan performance statistics | |
| 120739 | 2026-06-22 11:42 | 2026-06-22 11:56 | MySQL Server: Replication | Open | S1 | 5.7.25 | Linux | x86 | Corruption of the index file caused stale binary log entries to be re-applied after executing FLUSH LOGS |
| 120738 | 2026-06-22 10:55 | 2026-06-22 11:26 | MySQL Server: Replication | Open | S1 | 5.7.25 | Linux (6) | x86 | Corruption of the index file caused stale binary log entries to be re-applied after executing FLUSH LOGS |
| 120715 | 2026-06-17 8:28 | 2026-06-18 2:12 | MySQL Server: InnoDB storage engine | Open (28 days) | S2 | 9.7.0 | Any | Any | Unexpected deadlock when one of the two transactions does not acquire any locks |
| 120698 | 2026-06-16 3:17 | 2026-07-01 2:39 | MySQL Server: InnoDB storage engine | Open (15 days) | S1 | 8.0.44 | Any | Any | Contribution by Tencent: Compressed pages' records may out of order when using change buffer |
| 120685 | 2026-06-15 6:28 | 2026-06-15 6:40 | MySQL Server: XA transactions | Open | S3 | 8.0, 9.7.0 | Any | Any | XA recovery corrupts database name with special characters in MDL lock key (double filename_to_tablename()) |
| 120684 | 2026-06-15 3:22 | 2026-06-15 3:28 | MySQL Server: InnoDB storage engine | Open (31 days) | S2 | 9.4.0 | Any | Any | Inconsistent deadlock of UPDATE and SELECT FOR UPDATE with the same WHERE clause |
| 120681 | 2026-06-14 5:43 | 2026-06-14 5:43 | MySQL Server: FULLTEXT search | Open | S2 | 9.7 | Debian (Debian GNU/Linux 12 (bookworm)) | x86 ((86_64) | ngram FULLTEXT parser fails to match certain Latin tokens (e.g. "Sarah") in any query mode |
| 120665 | 2026-06-12 10:19 | 2026-06-15 8:49 | MySQL Server: Optimizer | Open (31 days) | S2 | 8.4.8 | Any | Any | Non optimal query plan chosen for DML |
| 120662 | 2026-06-11 22:16 | 2026-06-12 6:14 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: Use public variable name innodb_open_files in open-file timeo ... | |
| 120649 | 2026-06-09 17:53 | 2026-06-09 18:51 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: InnoDB: crash recovery of unfinished ALTER TABLESPACE ENCRYPT ... | |
| 120648 | 2026-06-09 17:53 | 2026-06-09 18:51 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: InnoDB: Crash resuming interrupted ALTER TABLESPACE ENCRYPTIO ... | |
| 120647 | 2026-06-09 17:40 | 2026-06-09 18:50 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: InnoDB: make_page_dirty debug command logs MLOG_2BYTES on com ... | |
| 120634 | 2026-06-09 4:07 | 2026-06-25 2:28 | MySQL Server: InnoDB storage engine | Open | S1 | 8.0.44 8.4.9 | Any | Any | buf_stat_per_index inc/dec is not paired: root page inc is never decremented, causing unbounded growth of ut_lock_free_h |
| 120610 | 2026-06-03 12:00 | 2026-06-03 12:21 | MySQL Server: InnoDB storage engine | Open (43 days) | S3 | 5.7 | Any | Any | REPEATABLE READ: no-change UPDATE causes MVCC Rule 1 violation — transaction cannot see own modification |
| 120598 | 2026-06-02 7:06 | 2026-06-02 7:07 | MySQL Server: InnoDB storage engine | Open (44 days) | S3 | 8.0.46, 8.4.9 | Linux | x86 | Autoincrement problem |
| 120597 | 2026-06-02 6:58 | 2026-06-02 6:58 | MySQL Server: Performance Schema | Open | S5 | 8.0.46, 8.4.9 | Linux | x86 | performance_schema atomic values maintaining CPU cache-friendliness |
| 120596 | 2026-06-02 6:37 | 2026-06-02 6:37 | MySQL Server: InnoDB storage engine | Open | S5 | 8.0.46, 8.4.9 | Linux | x86 | WAIT_FOR_READ, WAIT_FOR_WRITE is stuck in the 2012 |
| 120577 | 2026-05-30 7:58 | 2026-05-30 7:58 | MySQL Server: MyISAM storage engine | Open | S3 | 8.0.45 | Any | Any | drop index can lead to different results |
| 120576 | 2026-05-30 7:15 | 2026-05-30 7:15 | MySQL Server: MyISAM storage engine | Open | S3 | 8.0.45 | Any | Any | drop index can lead to different results |
| 120575 | 2026-05-30 6:57 | 2026-05-30 6:57 | MySQL Server: Optimizer | Open | S2 | 8.0.41+ | Any | Any | Range optimizer chooses bad range plan for large IN lists and execution is very slow and memory usage spikes. |
| 120574 | 2026-05-29 14:05 | 2026-05-29 14:12 | MySQL Server: Optimizer | Open | S2 | 8.0.41 | Any | Any | Range optimizer exceeds memory limit and chooses bad range plan for large IN lists |
| 120564 | 2026-05-29 6:43 | 2026-05-29 6:46 | MySQL Server: InnoDB storage engine | Open | S3 | 9.7.0 | Any | Any | InnoDB FTS: Off-by-one error in fts_init_index() causes unsynced document to be lost after crash recovery |
| 120561 | 2026-05-28 11:11 | 2026-05-29 4:41 | MySQL Server: DDL | Open (49 days) | S3 | 9.7/8.4/8.0 | Any | Any | tablespace marked missing after rollback of copy-style ALTER |
| 120558 | 2026-05-27 11:21 | 2026-05-27 11:41 | MySQL Server: InnoDB storage engine | Open (50 days) | S3 | 8.4.8 | Any | Any | Redo log archiving started by dead connection cannot be disabled later |
| 120539 | 2026-05-24 15:26 | 2026-05-24 15:26 | MySQL Server: FULLTEXT search | Open | S2 | 9.6.0 | Linux | Any | Duplicate FULLTEXT index on a column returns wrong MATCH...AGAINST results when combined with a STORED generated column |
| 120499 | 2026-05-20 5:02 | 2026-05-20 5:02 | MySQL Server: Stored Routines | Open | S2 | 9.6.0 | Linux | x86 (AMD EPYC 9K65) | Recursive stored procedure with max_sp_recursion_depth >= 250 crashes mysqld |
| 120480 | 2026-05-14 20:59 | 2026-06-12 21:18 | MySQL Server: Replication | Open (34 days) | S3 | 8.0.40 | Any | Any | Crash in set_and_validate_user_attributes during relay log recovery |
| 120471 | 2026-05-14 0:08 | 2026-05-18 9:15 | MySQL Server: Replication | Open (63 days) | S1 | 8.0.43, 8.0.46, 8.4.9, 9.7.0 | Any (reproduced on macOS and Linux) | Any | binary log violates read after write (commit) consistency |
| 120469 | 2026-05-13 17:00 | 2026-05-18 9:12 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: Fix ut_error() at ENABLE INNODB REDO_LOG when innodb_checkpo ... | |
| 120467 | 2026-05-13 15:57 | 2026-05-18 9:09 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.45 | Any | Any | dd_open_fk_tables function heap-use-after-free |
| 120435 | 2026-05-11 7:21 | 2026-05-19 14:18 | MySQL Server: DDL | Open | S3 | Any | Any | Add DDL Triggers Support in MySQL | |
| 120417 | 2026-05-08 6:22 | 2026-05-20 11:16 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.40 | Linux | x86 | MY-013028] [InnoDB] MySQL is freeing a thd though trx->n_mysql_tables_in_use is X and trx->mysql_n_tables_locked is Y |
| 120414 | 2026-05-07 15:19 | 2026-05-11 12:42 | MySQL Server: InnoDB storage engine | Open (66 days) | S5 | 8.0.32 - 9.7 | Any | Any | InnoDB performance regression because of validate_rec_offset |
| 120388 | 2026-04-30 19:36 | 2026-05-01 9:44 | MySQL Server: InnoDB storage engine | Open | S5 | 8.4.9 | Oracle Linux (9.5) | x86 | High contention on InnoDB per-page BUF_BLOCK_MUTEX during concurrent range-selects to same row/page |
| 120327 | 2026-04-23 7:46 | 2026-04-23 12:40 | MySQL Server: Replication | Open | S2 | MySQL 8.4 | Any | Any | Unsigned integer wraparound in Binlog_sender::run() when binlog_row_event_max_size is set to a large value |
| 120318 | 2026-04-22 6:31 | 2026-04-22 6:31 | MySQL Server: InnoDB storage engine | Open | S3 | 9.6.0 | Linux | Any | InnoDB partition statistics not auto-updated after ALTER TABLE REORGANIZE PARTITION |
| 120281 | 2026-04-17 9:21 | 2026-04-17 11:32 | MySQL Server: Replication | Open (90 days) | S2 | 8.0.42 | Linux (any) | Any | replica_preserve_commit_order causes infinite deadlock in group commit pipeline, blocking all application writes |
| 120278 | 2026-04-17 2:44 | 2026-05-12 2:31 | MySQL Server: Replication | Open (65 days) | S2 | 8.0.44 8.4.9 | Any | Any | mts_event_coord_cmp() uses strcmp() for binlog filename comparison, causing incorrect ordering when binlog index exceeds |
| 120274 | 2026-04-16 5:53 | 2026-05-12 6:59 | MySQL Server: Connection Handling | Open | S2 | 8.4.6 | Red Hat (Rocky Linux 8.8) | x86 (4.18.0-477.27.1.el8_8.x86_64) | Specific account authentication permanently fails with "Public Key Retrieval is not allowed" after FLUSH PRIVILEGES |
| 120266 | 2026-04-14 9:12 | 2026-04-14 9:12 | MySQL Server: Replication | Open | S3 | MySQL 8.4 | Any | Any | Replication delay when SQL thread skips large already-executed transactions |
| 120245 | 2026-04-10 13:14 | 2026-04-10 13:55 | MySQL Server: DDL | Open | S1 | 9.6.0 | Any | Any | Unexpected error `Got error -1 - 'Unknown error -1' from storage engine` |
| 120244 | 2026-04-10 12:40 | 2026-04-10 13:51 | MySQL Server: DDL | Open | S1 | 9.6.0 | Any | Any | Unexpected error `'0' for column '' at row -1` triggered by ALTER |
| 120241 | 2026-04-09 11:02 | 2026-04-09 11:02 | MySQL Server: InnoDB storage engine | Open | S3 | trunk | Any | Any | Fix ambiguity in the name and doxygen of method buf_flush_sync_all_buf_pools() |
| 120238 | 2026-04-09 9:16 | 2026-04-09 9:34 | MySQL Server: Replication | Open | S3 | 5.7 8.0 | Linux | Any | maybe cause "could not find next log" if rotate binary log without fsync @@log_bin_index's parent dir |
| 120235 | 2026-04-08 10:17 | 2026-04-08 10:17 | MySQL Server: XML functions | Open | S3 | 8.0 | Windows (Win11) | x86 (na) | Un/Comment Selection |
| 120204 | 2026-04-02 7:52 | 2026-04-02 7:52 | MySQL Server: InnoDB storage engine | Open | S2 | 9.4.0 | Any | Any | UPDATE statements fail to update rows or acquire locks after being released |
| 120199 | 2026-04-01 8:00 | 2026-06-19 12:42 | MySQL Server: InnoDB storage engine | Open (27 days) | S2 | 9.4.0 | Any | Any | Two transactions simultaneously acquire the same exclusive lock |
| 120196 | 2026-03-31 23:50 | 2026-04-03 6:23 | MySQL Server: InnoDB storage engine | Open | S3 | 9.6.0 | Any | Any | n_mysql_tables_in_use uint32 underflow via MRR dsmrr_init() error path in handler.cc |
| 120181 | 2026-03-30 21:14 | 2026-04-20 13:09 | MySQL Server: Replication | Open | S3 | Any | Any | Contribution: Fix stale sql_mode values in Query_event Doxygen documentatio ... | |
| 120177 | 2026-03-30 6:38 | 2026-04-01 12:10 | MySQL Server: Replication | Open | S3 | 5.7.44 | Any | Any | Lost gtids after crash recovery |
| 120170 | 2026-03-28 8:33 | 2026-03-28 8:33 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.39 | Any | Any | Missing Update in READ COMMITTED during concurrent UPDATE with row re-evaluation failure. |
| 120153 | 2026-03-25 16:15 | 2026-03-25 16:18 | MySQL Server: Options | Open | S3 | 9.5 | Any | Any | Wrong default value for default_collation_for_utf8mb4 |
| 120129 | 2026-03-23 9:29 | 2026-03-23 9:29 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | Non-deterministic semi-consistent read behavior: UPDATE randomly blocks on non-matching locked rows in READ UNCOMMITTED. |
| 120125 | 2026-03-23 2:43 | 2026-03-23 2:43 | MySQL Server: XA transactions | Open | S2 | 8.4 8.0.44 | Any | Any | xid_t::operator< breaks std::map ordering; binlog XA recovery may rollback prepared XA |
| 120124 | 2026-03-22 10:29 | 2026-03-22 10:29 | MySQL Server: DDL | Open | S3 | 9.6 | Any | Any | Remove unused partition states from enum partition_state { |
| 120115 | 2026-03-19 15:21 | 2026-03-19 15:32 | MySQL Server: Replication | Open | S3 | 8.4 | Any | Any | CHANGE REPLICATION FILTER REPLICATE_IGNORE_DB with ROW BASED REPLICATION NOT WORKING AS DESCRIBED |
| 120104 | 2026-03-19 7:36 | 2026-03-30 7:32 | MySQL Server: DDL | Open (108 days) | S3 | 8.4.7 | Any | Any | Modify VARCHAR column leads to unexpected rebuild of table |
| 120050 | 2026-03-13 9:00 | 2026-03-17 12:22 | MySQL Server: InnoDB storage engine | Open | S5 | 8.0.44 | Any | Any | remove dead code |
| 119997 | 2026-03-06 13:12 | 2026-03-20 15:06 | MySQL Server: InnoDB storage engine | Open (119 days) | S3 | 8.0.40 | Any | Any | Setting innodb_use_native_aio to OFF can lead to severe lock contention. |
| 119986 | 2026-03-05 11:29 | 2026-05-15 12:08 | MySQL Server: InnoDB storage engine | Open (132 days) | S3 | 8.4.7 | Any | Any | Value of sys var temptable_max_mmap not honored unless temptable_use_mmap is ON |
| 119980 | 2026-03-04 11:56 | 2026-03-04 11:56 | MySQL Server: FULLTEXT search | Open | S3 | 8.4.8 | Any | Any | Optimize full text only not working when trying to fix FTS index after tablespace import |
| 119978 | 2026-03-03 16:41 | 2026-04-08 9:16 | MySQL Server: InnoDB storage engine | Open (99 days) | S3 | 8.0 | SUSE (SLES 15 SP6) | x86 | In-place upgrade of Mysql 5.7.x/8.0.19 to revision after 8.0.23 fails due to undo_00x tablespace ID |
| 119974 | 2026-03-03 2:29 | 2026-04-16 2:50 | MySQL Server: InnoDB storage engine | Open (135 days) | S3 | 8.0, 8.4, 9.6 | Any | Any | inplace algorithm dropping multi full text indexes only drops FTS AUX tables of the last index, leading orphaned tables |
| 119957 | 2026-02-28 7:28 | 2026-02-28 7:28 | MySQL Server: Replication | Open | S2 | 8.0 | Any | Any | Contribution by Tencent: Replica Crash Due to Stale fts_doc_id in HASH_SCAN Replication Path |
| 119949 | 2026-02-26 14:21 | 2026-03-03 9:28 | MySQL Server: InnoDB storage engine | Open (135 days) | S2 | 9.5.0 | Any | Any | DELETE statement fails to delete the row after blocking is resumed |
| 119947 | 2026-02-26 9:19 | 2026-02-26 9:30 | MySQL Server: Replication | Open | S2 | 8.0.45 | Any | Any | ordered_commit some transactions had flush errors, but committed successfully.resulting in master-slave inconsistency |
| 119945 | 2026-02-26 2:44 | 2026-02-26 2:44 | MySQL Server: Partitions | Open | S3 | 8.0.35 | Any | Any | Inconsistent result set on repeated execution of NATURAL JOIN with expression index and KEY partitioning |
| 119877 | 2026-02-10 12:42 | 2026-02-11 9:52 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.42+ | Any | Any | InnoDB Buffer Pool Flush State Mutex Contention (8.0.42-debug) |
| 119855 | 2026-02-06 18:36 | 2026-02-06 18:38 | MySQL Server: Replication | Open (160 days) | S3 | 8.0 | Any | Any | Relay Log Recovery after mts_recovery_groups failure should be retried |
| 119797 | 2026-01-27 20:09 | 2026-02-10 6:48 | MySQL Server: General | Open | S3 | Any | Any | Contribution: Feat: Native Vector Search with HNSW Indexing | |
| 119784 | 2026-01-27 0:53 | 2026-06-01 23:27 | MySQL Server: Partitions | Open (170 days) | S3 | 8.0.42 and later | Any | Any | Fix partition pruning with non-constant defaults regression |
| 119782 | 2026-01-26 17:22 | 2026-01-27 8:36 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: Fix partition pruning with non-constant defaults regression | |
| 119775 | 2026-01-26 6:37 | 2026-01-26 6:37 | MySQL Server: MyISAM storage engine | Open | S2 | 9.6.0 | Any | Any | External locking should be removed |
| 119769 | 2026-01-24 14:46 | 2026-03-09 10:48 | MySQL Server: InnoDB storage engine | Open (130 days) | S2 | 9.4.0 | Any | Any | The transaction reads the value inserted by the blocked statement |
| 119766 | 2026-01-23 19:18 | 2026-01-23 19:18 | MySQL Server: Performance Schema | Open | S2 | 8.0.44 | Any | Any | Rows unexpectedly added in performance_schema for failed connections |
| 119759 | 2026-01-22 18:55 | 2026-05-12 20:31 | MySQL Server: InnoDB storage engine | Open (175 days) | S2 | 8.0.42 | Any | Any | InnoDB allow reads on non-durable data, which can be lost after crash(visibility before durability window) |
| 119744 | 2026-01-22 9:52 | 2026-01-22 9:52 | MySQL Server: InnoDB storage engine | Open | S2 | 9.6.0 | Any | Any | mysqlbackup_page_track_purge_up_to not working |
| 119731 | 2026-01-21 3:10 | 2026-01-21 3:13 | MySQL Server: InnoDB storage engine | Open | S3 | MySQL 8.4 | Any | Any | mysql 8.4 ut_a is invalid |
| 119707 | 2026-01-16 11:27 | 2026-01-16 11:27 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | SERIALIZABLE Isolation Level: Concurrent Transactions with AUTO_INCREMENT Produce Non-Serializable Result |
| 119676 | 2026-01-14 6:26 | 2026-01-14 13:11 | MySQL Server: Replication | Open | S2 | 8.0.44 | Any | Any | Column statistic (histograms) is not replicated in read_only replica mode |
| 119667 | 2026-01-13 11:42 | 2026-01-26 14:07 | MySQL Server: InnoDB storage engine | Open (171 days) | S2 | 9.4.0 | Ubuntu (22.04) | x86 (x86_64) | Assertion failure ddl0buffer.cc:197 with innodb-ddl-threads=4 + O_DIRECT |
| 119661 | 2026-01-12 13:19 | 2026-01-12 13:19 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.44 | Any | Any | Drop multiple FTS will cause permanent leakage of its AUX tables |
| 119656 | 2026-01-12 2:35 | 2026-01-12 2:35 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.41 | Any | Any | after crash recovery check table warning: Index xxx is marked as corrupted |
| 119654 | 2026-01-09 10:01 | 2026-01-09 10:01 | MySQL Server: InnoDB storage engine | Open | S2 | 8.x | Linux | Any | assert fail at mach_write_to_2 with a value larger than 0xFFFF. |
| 119653 | 2026-01-09 9:39 | 2026-01-09 9:39 | MySQL Server: InnoDB storage engine | Open | S5 | 8.0.44 | Any | Any | Reduce unnecessary if checks in core logic |
| 119649 | 2026-01-08 12:18 | 2026-01-08 12:18 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | SERIALIZABLE Isolation Violation with Consistent Snapshot in MySQL |
| 119648 | 2026-01-08 11:37 | 2026-01-09 6:09 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.39 | Any | Any | Non-repeatable Reads in REPEATABLE READ Isolation Level |
| 119643 | 2026-01-07 18:53 | 2026-01-08 5:48 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.44 | Linux | x86 | Undo log purging goes through purge boundary overwrites undo log |
| 119632 | 2026-01-06 12:48 | 2026-01-06 12:48 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.39 | Any | Any | Inconsistent Auto-increment Primary Key Allocation Under Concurrent Operations Violates Transaction Consistency |
| 119628 | 2026-01-05 22:20 | 2026-05-06 15:44 | MySQL Server: InnoDB storage engine | Open (71 days) | S1 | 8.0 | Any | Any | Undo Truncation Bug, not fixed in 8.0, leads to Data Corruption. |
| 119626 | 2026-01-05 13:33 | 2026-01-06 1:30 | MySQL Server: InnoDB storage engine | Open (191 days) | S3 | 8.0.41 | Any | Any | Adding an index using the inplace algorithm will result in a "Duplicate entry" error in the replace into syntax. |
| 119623 | 2026-01-05 12:06 | 2026-01-05 12:35 | MySQL Server: DDL | Open (192 days) | S3 | 8.0.43 | CentOS | x86 | Cannot add or update a child row: a foreign key constraint fails |
| 119618 | 2026-01-04 8:39 | 2026-01-04 8:39 | MySQL Server: Information schema | Open | S3 | 9.4 | Any | Any | misleading name of external temp table in I_S.INNODB_TEMP_TABLE_INFO |
| 119612 | 2025-12-31 2:10 | 2025-12-31 5:02 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.25 8.0.40 | Any | Any | dict_stats_analyze_index() may always discard optimal index-based access paths |
| 119608 | 2025-12-30 3:39 | 2025-12-30 3:39 | MySQL Server: InnoDB storage engine | Open | S3 | 9.3.0 | Any | Any | UPDATE is not blocked by SELECT ... FOR SHARE under READ COMMITTED isolation level |
| 119607 | 2025-12-30 2:53 | 2025-12-30 2:53 | MySQL Server: Errors | Open | S3 | Any | Any | can't imorte csv. | |
| 119602 | 2025-12-28 21:11 | 2025-12-29 10:39 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0 | Any | Any | Inconsistent data |
| 119598 | 2025-12-26 6:46 | 2025-12-29 4:52 | MySQL Server: DDL | Open | S3 | Any | Any | ALTER TABLE will report Deadlock found ... when do a RENAME to itself and ENABLE KEYS. | |
| 119593 | 2025-12-24 8:36 | 2025-12-24 8:36 | MySQL Server: Row Based Replication ( RBR ) | Open | S3 | 8.0.* | Any | Any | Generated Column Calculation on the replica ERROR |
| 119585 | 2025-12-23 3:17 | 2026-07-13 23:49 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.30/9.4.0/8.4.6 | Any | Any | In extreme cases, sync_array_get_and_reserve_cell fails to obtain a cell even have space |
| 119578 | 2025-12-19 14:06 | 2025-12-19 14:11 | MySQL Server: InnoDB storage engine | Open | S1 | 8.0.40 | Any | x86 | Repeated MySQL Crashes During Online ALTER on Multi -TB Tables |
| 119577 | 2025-12-19 8:15 | 2025-12-19 8:15 | MySQL Server: XA transactions | Open | S3 | 8.0.43 | Linux | x86 | Read uncommitted isolation was not work in different transactions |
| 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 |
| 119567 | 2025-12-17 2:53 | 2025-12-18 2:10 | MySQL Server: InnoDB storage engine | Open (210 days) | S2 | 8.0.30/9.4.0/8.4.6 | Any | Any | signal 6 crashed when too many connections |
| 119564 | 2025-12-16 12:51 | 2026-01-30 1:11 | MySQL Server: InnoDB storage engine | Open (167 days) | 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 (212 days) | S3 | 8.4.7 | Any | Any | SHOW BINLOG EVENTS fails with Event too big |
| 119553 | 2025-12-15 14:00 | 2025-12-15 14:00 | MySQL Server: Federated storage engine | Open | S2 | 8.4.6 | Linux | x86 | Mutex deadlock between THR_LOCK_servers and federated_mutex |
| 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 |
| 119517 | 2025-12-05 15:25 | 2025-12-15 5:26 | MySQL Server: InnoDB storage engine | Open (213 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 (224 days) | S3 | 8.4.6 | Linux | x86 | [InnoDB] Partitioned tables in reserved db name 'aux' act as missing tablespaces after restart |
| 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 |
| 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 (226 days) | S3 | 8.4.7 | Any | Any | GTID tags can violate restrictions |
| 119482 | 2025-12-01 12:00 | 2025-12-01 12:04 | MySQL Server: Security: Privileges | Open (227 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 |
| 119473 | 2025-11-29 8:17 | 2025-11-30 15:03 | MySQL Server: InnoDB storage engine | Open (229 days) | S3 | 8.0.41 | Any | Any | InnoDB Mutex Deadlock Cause Mysql Crash |
| 119471 | 2025-11-27 17:03 | 2026-05-06 17:03 | MySQL Server: Connection Handling | Open (71 days) | S2 | 8.4.7 | Ubuntu (25.10 questing) | x86 (64 bits) | "Bad handshake" during each connection to a replication source server |
| 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, |
| 119460 | 2025-11-25 10:08 | 2026-01-21 3:17 | MySQL Server: InnoDB storage engine | Open (176 days) | 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 (231 days) | S2 | 5.7 | Any | Any | import tablespace cost too long |
| 119451 | 2025-11-24 9:50 | 2026-01-21 3:17 | MySQL Server: Locking | Open (176 days) | S2 | 8.0.44 | Any | Any | The schema's MDL lock is held for too long after opening the table |
| 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 |
| 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 |
| 119431 | 2025-11-20 7:59 | 2026-07-09 5:01 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.30, 8.0.39 | Any | Any | Concurrent inserts generate duplicate AUTO_INCREMENT values after changing auto_increment settings |
| 119418 | 2025-11-18 8:23 | 2025-11-25 11:21 | MySQL Server: MyISAM storage engine | Open (233 days) | S3 | 8.4.7 | Any | Any | MyISAM ALTER TABLE random 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 |
| 119407 | 2025-11-17 6:17 | 2025-12-07 21:04 | MySQL Server: Locking | Open (239 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. |
| 119396 | 2025-11-14 10:58 | 2025-11-14 15:12 | MySQL Server: InnoDB storage engine | Open (244 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() |
| 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)` |
| 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 |
| 119312 | 2025-11-05 17:30 | 2026-01-13 11:33 | MySQL Server: Replication | Open | S3 | 8.4.x | Any | Any | `start replica` command adds an invalid record to mysql.slave_master_info |
| 119304 | 2025-11-05 2:08 | 2026-01-15 10:31 | MySQL Server: Replication | Open (253 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 |
| 119300 | 2025-11-04 10:46 | 2025-11-04 10:56 | MySQL Server: InnoDB storage engine | Open (254 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 (251 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 | 2026-01-29 6:39 | MySQL Server: InnoDB storage engine | Open (168 days) | S5 | 8.0.44 | Any | Any | resue read-view for read_only mode |
| 119280 | 2025-10-31 11:55 | 2026-06-20 21:50 | MySQL Server: InnoDB storage engine | Open (48 days) | S2 | 9.5.0 | Any | Any | INSTANT ADD succeeds even when the size of a row crosses row_size_limit |
| 119276 | 2025-10-31 6:05 | 2026-01-13 11:34 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.44 | Any | Any | ALTER TABLE ANALYZE PARTITION statement causes incorrect results in the mysql.table_table_stats |
| 119273 | 2025-10-30 14:14 | 2026-01-15 10:29 | MySQL Server: InnoDB storage engine | Open (259 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" |
| 119270 | 2025-10-30 9:12 | 2026-04-14 8:43 | MySQL Server: Replication | Open | S3 | MySQL8.0,5.7 | Any | Any | Single-statement transactions can cause latency spikes on the replica |
| 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 |
| 119248 | 2025-10-27 16:46 | 2025-10-27 16:54 | MySQL Server: Security: Privileges | Open (262 days) | S3 | 9.4.0 | Any | Any | CHECK TABLE command can be executed by users with the table-level GRANT OPTION privilege |
| 119241 | 2025-10-27 11:25 | 2025-10-27 11:29 | MySQL Server: DDL | Open (262 days) | S2 | 8.0.41 | Any | Any | Exception when creating index instance |
| 119235 | 2025-10-27 2:47 | 2025-11-10 14:16 | MySQL Server: InnoDB storage engine | Open (248 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 |
| 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 |
| 119223 | 2025-10-24 3:16 | 2026-01-13 20:35 | MySQL Server: Performance Schema | Open | S3 | 8.0.30 | Any | Any | The pfs_thread.processlist_id is set to NULL after using Srv_session |
| 119215 | 2025-10-23 9:16 | 2026-01-13 20:35 | MySQL Server: Performance Schema | Open (266 days) | S3 | 8.0.30 | Any | Any | pfs_thread.processlist_id will be null after select group_replication_reset_member_actions() |
| 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 (278 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. |
| 119101 | 2025-10-02 4:44 | 2025-10-11 3:25 | MySQL Server: Logging | Open (278 days) | S3 | 8.0.43 | Any | Any | Incorrect query_time is logged in the slow log when adjusting system time backward |
| 119075 | 2025-09-26 6:42 | 2025-10-11 3:23 | MySQL Server: Connection Handling | Open (278 days) | S3 | Windows | Any | Issues with home page | |
| 118814 | 2025-08-12 3:47 | 2025-10-11 3:22 | MySQL Server: Windows | Open (278 days) | S2 | 8.0.39 | Windows | Any | I/O error while writing to file: .\#ib_16384_0.dblwr |
| Showing all 179 (Edit, Save, CSV, Feed) |
