Showing 1–30 of 104
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119133 | 2025-10-11 6:55 | 2025-10-11 6:56 | MySQL Server: InnoDB storage engine | Open (393 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 |
| 119235 | 2025-10-27 2:47 | 2025-11-10 14:16 | MySQL Server: InnoDB storage engine | Open (363 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 |
| 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 |
| 119273 | 2025-10-30 14:14 | 2026-01-15 10:29 | MySQL Server: InnoDB storage engine | Open (374 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 (163 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 (283 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 (366 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 (369 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 |
| 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 (359 days) | S1 | 8.0.40 | Any | Any | Increase in undo log size , slower purging and no truncation even after restart |
| 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 |
| 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 |
| 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 |
| 119457 | 2025-11-25 9:00 | 2025-11-27 12:42 | MySQL Server: InnoDB storage engine | Open (346 days) | S2 | 5.7 | Any | Any | import tablespace cost too long |
| 119460 | 2025-11-25 10:08 | 2026-01-21 3:17 | MySQL Server: InnoDB storage engine | Open (291 days) | S2 | 8.0.44 | Any | Any | InnoDB transaction may get stuck in an infinite loop when releasing Read Locks |
| 119473 | 2025-11-29 8:17 | 2025-11-30 15:03 | MySQL Server: InnoDB storage engine | Open (344 days) | S3 | 8.0.41 | Any | Any | InnoDB Mutex Deadlock Cause Mysql Crash |
| 119490 | 2025-12-02 7:48 | 2025-12-02 7:57 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.41 | Any | Any | savepoint |
| 119503 | 2025-12-03 16:45 | 2025-12-04 20:12 | MySQL Server: InnoDB storage engine | Open (339 days) | S3 | 8.4.6 | Linux | x86 | [InnoDB] Partitioned tables in reserved db name 'aux' act as missing tablespaces after restart |
| 119517 | 2025-12-05 15:25 | 2025-12-15 5:26 | MySQL Server: InnoDB storage engine | Open (328 days) | S3 | 8.0.44 | Any | Any | Importing Table with Instant Drop Column not fix index col name pointer |
| 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 |
| 119564 | 2025-12-16 12:51 | 2026-01-30 1:11 | MySQL Server: InnoDB storage engine | Open (282 days) | S3 | 9.5.0 | Any | Any | for REPEATABLE READ TRANSACTION ISOLATION, data should not be read if deleted |
| 119567 | 2025-12-17 2:53 | 2025-12-18 2:10 | MySQL Server: InnoDB storage engine | Open (325 days) | S2 | 8.0.30/9.4.0/8.4.6 | Any | Any | signal 6 crashed when too many connections |
| 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 |
| 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 |
| 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 |
| 119602 | 2025-12-28 21:11 | 2025-12-29 10:39 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0 | Any | Any | Inconsistent data |
Showing 1–30 of 104
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.011 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.