Showing 1–30 of 220
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 107852 | 2022-07-12 19:18 | 2026-04-05 20:45 | MySQL Server: Command-line Clients | Open (988 days) | S3 | 8.0.26 | Any (Linux and OSX) | x86 | MySQL client does not detect closed connection properly |
| 118814 | 2025-08-12 3:47 | 2025-10-11 3:22 | MySQL Server: Windows | Open (386 days) | S2 | 8.0.39 | Windows | Any | I/O error while writing to file: .\#ib_16384_0.dblwr |
| 119075 | 2025-09-26 6:42 | 2025-10-11 3:23 | MySQL Server: Connection Handling | Open (386 days) | S3 | Windows | Any | Issues with home page | |
| 119101 | 2025-10-02 4:44 | 2025-10-11 3:25 | MySQL Server: Logging | Open (386 days) | S3 | 8.0.43 | Any | Any | Incorrect query_time is logged in the slow log when adjusting system time backward |
| 119133 | 2025-10-11 6:55 | 2025-10-11 6:56 | MySQL Server: InnoDB storage engine | Open (386 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. |
| 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. |
| 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 |
| 119200 | 2025-10-21 8:19 | 2026-01-15 10:19 | MySQL Server: Security: Roles | Open | S3 | 8.4.x | Any | Any | make connection access sorting rule sane and predictable |
| 119215 | 2025-10-23 9:16 | 2026-01-13 20:35 | MySQL Server: Performance Schema | Open (374 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 | 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 |
| 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 |
| 119235 | 2025-10-27 2:47 | 2025-11-10 14:16 | MySQL Server: InnoDB storage engine | Open (356 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 |
| 119241 | 2025-10-27 11:25 | 2025-10-27 11:29 | MySQL Server: DDL | Open (370 days) | S2 | 8.0.41 | Any | Any | Exception when creating index instance |
| 119248 | 2025-10-27 16:46 | 2025-10-27 16:54 | MySQL Server: Security: Privileges | Open (370 days) | S3 | 9.4.0 | Any | Any | CHECK TABLE command can be executed by users with the table-level GRANT OPTION privilege |
| 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 |
| 119265 | 2025-10-29 11:15 | 2025-10-29 11:15 | MySQL Server: mysqldump Command-line Client | Open | S2 | mysqldump: 8.0.40 | Any | Any | mysqldump 8.0.40 issues FLUSH TABLES before dumping, generating a new GTID and causing replication divergence |
| 119273 | 2025-10-30 14:14 | 2026-01-15 10:29 | MySQL Server: InnoDB storage engine | Open (367 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" |
| 119280 | 2025-10-31 11:55 | 2026-06-20 21:50 | MySQL Server: InnoDB storage engine | Open (156 days) | S2 | 9.5.0 | Any | Any | INSTANT ADD succeeds even when the size of a row crosses row_size_limit |
| 119285 | 2025-11-01 6:16 | 2026-01-29 6:39 | MySQL Server: InnoDB storage engine | Open (276 days) | S5 | 8.0.44 | Any | Any | resue read-view for read_only mode |
| 119290 | 2025-11-02 15:06 | 2025-11-07 7:43 | MySQL Server: InnoDB storage engine | Open (359 days) | S2 | 9.3.0, 9.5.0 | Any | Any | SELECT statement is affected by concurrent transaction under Read Uncommitted |
| 119300 | 2025-11-04 10:46 | 2025-11-04 10:56 | MySQL Server: InnoDB storage engine | Open (362 days) | S3 | 8.0.44 | Any | Any | Debug assertion failure: field.field_no < dict_index_get_n_fields(index) |
| 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 |
| 119336 | 2025-11-07 18:21 | 2025-11-07 18:49 | MySQL Server: Command-line Clients | Open (359 days) | S3 | 5.7 8.0 8.4 | Any | Any | extra whitespace in grant statement results in syntax error |
| 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)` |
| 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() |
| 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 |
| 119396 | 2025-11-14 10:58 | 2025-11-14 15:12 | MySQL Server: InnoDB storage engine | Open (352 days) | S1 | 8.0.40 | Any | Any | Increase in undo log size , slower purging and no truncation even after restart |
| 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. |
| 119407 | 2025-11-17 6:17 | 2025-12-07 21:04 | MySQL Server: Locking | Open (347 days) | S3 | 8.0.41 | Any | Any | Isolation Level Settings |
| 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 |
Showing 1–30 of 220
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.022 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.