| Showing all 109 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119799 | 2026-01-27 21:40 | 2026-01-27 21:40 | MySQL Server | Open | S3 | 8.3 | MacOS | ARM | OR condition incorrectly filters out NULL values in derived table with UNION |
| 119797 | 2026-01-27 20:09 | 2026-01-27 20:09 | MySQL Server: General | Open | S3 | Any | Any | Contribution: Feat: Native Vector Search with HNSW Indexing | |
| 119796 | 2026-01-27 19:12 | 2026-01-27 19:50 | MySQL Server: DDL | Open | S2 | 8.0.35 | Any | Any | Encrypted data changes when adding columns |
| 119784 | 2026-01-27 0:53 | 2026-01-27 1:26 | MySQL Server: Partitions | Open (1 day) | 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-01-26 18:21 | MySQL Server: InnoDB storage engine | Open | 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 |
| 119765 | 2026-01-23 17:52 | 2026-01-23 17:52 | MySQL Server: Connection Handling | Open | S3 | 8.0,8.4,9.6 | Any | Any | max allowed value for max_connections |
| 119759 | 2026-01-22 18:55 | 2026-01-27 8:06 | MySQL Server: InnoDB storage engine | Open (6 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 |
| 119708 | 2026-01-16 14:58 | 2026-01-17 5:22 | MySQL Server: Optimizer | Open (11 days) | S2 | 8.0.44 | Linux | Any | INNER JOIN and STRAIGHT_JOIN produce different results with FLOAT UNIQUE column on MEMORY table |
| 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 |
| 119706 | 2026-01-16 10:46 | 2026-01-16 10:49 | MySQL Server: Optimizer | Open | S2 | 8.0.44, 9.5.0 | Any | Any | Incorrect Results from ALL/ANY Subquery MIN/MAX Optimization with Type Mismatch |
| 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 |
| 119672 | 2026-01-13 14:54 | 2026-01-14 9:35 | MySQL Server: Stored Routines | Open (14 days) | S3 | all versions > 8.0 | Any | Any | [ERROR] [MY-013235] [Server] Error in parsing Event while upgrading MySQL version if Event was created in ANSI sql_mode |
| 119667 | 2026-01-13 11:42 | 2026-01-26 14:07 | MySQL Server: InnoDB storage engine | Open (2 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 |
| 119647 | 2026-01-08 8:23 | 2026-01-08 8:23 | MySQL Server | Open | S3 | 9.5.0 | Windows | Any | Inconsistent NOT IN query result between original table and SHOW CREATE TABLE reconstructed table |
| 119644 | 2026-01-07 20:26 | 2026-01-07 20:26 | MySQL Server: Security: Privileges | Open | S3 | 9.5.0 | Any | Any | Incorrect Column-level Privilege Checks of the CREATE TABLE ... LIKE Commands |
| 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-01-05 22:20 | MySQL Server: InnoDB storage engine | Open | 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 (22 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 (23 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 |
| 119601 | 2025-12-28 11:55 | 2025-12-28 11:59 | MySQL Server | Open (31 days) | S2 | 8.0.41 | CentOS | Any (x86) | Crash for show processlist when use cursor |
| 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 | 2025-12-23 5:43 | 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 (41 days) | S2 | 8.0.30/9.4.0/8.4.6 | Any | Any | signal 6 crashed when too many connections |
| 119565 | 2025-12-17 1:06 | 2025-12-17 1:06 | MySQL Server: Optimizer | Open | S3 | 8.0.41 | Any | Any | Temporary table causes incorrect conversion from TIME to JSON type |
| 119564 | 2025-12-16 12:51 | 2025-12-16 12:51 | MySQL Server: InnoDB storage engine | Open | 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 (43 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 (44 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 (55 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 (57 days) | S3 | 8.4.7 | Any | Any | GTID tags can violate restrictions |
| 119487 | 2025-12-01 14:45 | 2025-12-01 14:47 | MySQL Server | Open | S2 | 9.4.0, 9.5.0 | Ubuntu (22.04) | Any | JOIN, STRAIGHT_JOON Return Different Results |
| 119482 | 2025-12-01 12:00 | 2025-12-01 12:04 | MySQL Server: Security: Privileges | Open (58 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 (60 days) | S3 | 8.0.41 | Any | Any | InnoDB Mutex Deadlock Cause Mysql Crash |
| 119471 | 2025-11-27 17:03 | 2026-01-25 9:59 | MySQL Server: Connection Handling | Open | 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, |
| 119463 | 2025-11-26 6:23 | 2025-12-25 12:24 | MySQL Server: Charsets | Open | S2 | 9.5.0 | Any | Any | some charactor may be truncated use utf8mb4_general_ci collation_connection |
| 119460 | 2025-11-25 10:08 | 2026-01-21 3:17 | MySQL Server: InnoDB storage engine | Open (7 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 (62 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 (7 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 |
| 119444 | 2025-11-22 11:32 | 2025-11-27 7:01 | MySQL Server: Optimizer | Open (67 days) | S2 | any | Any | Any | Union with bound variable silently trims result |
| 119443 | 2025-11-22 2:36 | 2025-11-22 2:36 | MySQL Server: Charsets | Open | S3 | mysql-9.5.0 | Any | Any | LOWER() truncation with utf8mb4_0900_ai_ci due to byte expansion (In-place modification failure) |
| 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 | 2025-11-20 7:59 | MySQL Server | 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 (64 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 (70 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 (75 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 |
| 119394 | 2025-11-14 9:02 | 2025-12-14 12:06 | MySQL Server: Optimizer | Open (45 days) | S3 | Any | Any | Join order specified in the hint is different, the query results are incorrect. | |
| 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)` |
| 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 |
| 119353 | 2025-11-10 14:30 | 2025-12-06 21:38 | MySQL Server: Optimizer | Open | S3 | 9.4.0 | Any | Any | Column Value change after removing DISTINCT in query |
| 119352 | 2025-11-10 13:11 | 2025-12-06 21:37 | MySQL Server: Optimizer | Open | S3 | 9.4.0 | Any | Any | row number become less after changing where 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 |
| 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. |
| 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 |
| 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 (84 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 (85 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 (82 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 (88 days) | S5 | 8.0.44 | Any | Any | resue read-view for read_only mode |
| 119280 | 2025-10-31 11:55 | 2025-12-04 2:27 | MySQL Server: InnoDB storage engine | Open (55 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 (90 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 | 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 |
| 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 |
| 119253 | 2025-10-28 4:57 | 2026-01-22 12:00 | MySQL Server: InnoDB storage engine | Open (6 days) | S3 | 9.6.0 | MacOS (26.0.1) | ARM | innodb.tablespace_encrypt_9 crashing the server with assertion failure |
| 119248 | 2025-10-27 16:46 | 2025-10-27 16:54 | MySQL Server: Security: Privileges | Open (93 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 (93 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 (79 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 (97 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 (109 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 (109 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 (109 days) | S3 | Windows | Any | Issues with home page | |
| 118814 | 2025-08-12 3:47 | 2025-10-11 3:22 | MySQL Server: Windows | Open (109 days) | S2 | 8.0.39 | Windows | Any | I/O error while writing to file: .\#ib_16384_0.dblwr |
| Showing all 109 (Edit, Save, CSV, Feed) |
