| Showing 1-20 of 2533 (Edit, Save, CSV, Feed) | Show Next 20 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 118999 | 2025-09-12 10:03 | 2025-09-12 10:04 | MySQL Server | Open (2 days) | S3 | 8.4.6 | Linux | Any | Unexpected background histogram update warnings(MY-015116) |
| 118798 | 2025-08-07 9:22 | 2025-08-08 7:36 | MySQL Server: Replication | Verified (37 days) | S1 | 8.0.40 | Ubuntu | Any | Replication Break in 8.0.40 salve when from 8.0.33 Master |
| 118705 | 2025-07-23 8:06 | 2025-08-13 11:06 | MySQL Server: InnoDB storage engine | Verified (51 days) | S2 | 8.0 | Any | Any | when call que_eval_sql, may crash. |
| 118700 | 2025-07-22 12:55 | 2025-08-25 1:00 | MySQL Server: Replication | No Feedback (21 days) | S2 | 8.0.40 | Any | Any | Due to the master enabling the NO_BACKSLASH_ESCAPES sql_mode, an error occurs during replay on the slave. |
| 118653 | 2025-07-14 3:35 | 2025-07-14 5:09 | MySQL Server: XA transactions | Verified (62 days) | S3 | 8.0.35, 9.3.0 | Any | Any | The threads waiting for the MDL lock and the threads holding the lock are the same |
| 118602 | 2025-07-08 10:26 | 2025-08-19 0:07 | MySQL Server: Replication | Can't repeat (26 days) | S2 | 8.0.42 | Ubuntu (8.0.42-0ubuntu0.24.04.1) | x86 | SQL Thread cannot be stopped when last error was 1755 |
| 118538 | 2025-06-27 4:56 | 2025-08-02 1:00 | MySQL Server | No Feedback (44 days) | S3 | 8.0.30 | Linux (Amazon Linux 2) | x86 | Undo Logs Not Shrinking Despite No Active Long Transactions or Open Snapshots |
| 118516 | 2025-06-24 10:42 | 2025-07-03 18:36 | MySQL Server: InnoDB storage engine | Verified (73 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 (76 days) | S2 | 8.4, 8.4.5 | Any | Any | Contribution by Tencent: trx_cleanup_at_db_startup did not clean up trx_sys->shards |
| 118462 | 2025-06-17 2:56 | 2025-07-01 14:09 | MySQL Server: Replication | Can't repeat (75 days) | S3 | 8.0.39 | Red Hat (Rocky Linux 8.10) | x86 (AMD EPYC 7R32) | Executed SQL on replica is different from source |
| 118359 | 2025-06-04 13:43 | 2025-06-16 12:33 | MySQL Server: InnoDB storage engine | Verified (95 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 (72 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | Startup without Signs of Progress when Rolling-Back Big Transaction. |
| 118356 | 2025-06-04 11:58 | 2025-07-13 10:29 | MySQL Server: Replication | Verified (95 days) | S2 | 8.0.42, 8.4.5 9.3.0 | Any | Any | MySQL attempts committing transaction not fitting on disk, then crashes. |
| 118332 | 2025-06-02 18:58 | 2025-06-03 4:37 | MySQL Server: Replication | Verified (103 days) | S4 | 9.x | Any | Any | Please consider optimizing the binary log committing of big transactions (latency and disk usage). |
| 118322 | 2025-06-01 4:47 | 2025-07-20 1:00 | MySQL Server: Replication | No Feedback (57 days) | S2 | 8.0.20 | Any | x86 | Result of `show master status` is not correct !!! |
| 118229 | 2025-05-19 23:05 | 2025-06-10 15:59 | MySQL Server: Group Replication | Not a Bug (103 days) | S3 | 8.4.5, 8.0.41 | Any | Any | Async replica fails in DELETE event with HA_ERR_KEY_NOT_FOUND when using InnoDB cluster (group replication) |
| 118168 | 2025-05-12 12:27 | 2025-09-02 7:14 | MySQL Server: Replication | Verified (124 days) | S1 | 8.0.41 | Any | Any | MySQL data dictionary fails to upgrade at startup with lock timeout on ALTER TABLE |
| 118116 | 2025-05-05 17:41 | 2025-06-20 1:00 | MySQL Server: Replication | No Feedback (87 days) | S1 | 8.0.41 | Any | Any | HA_ERR_CORRUPT_EVENT on replication from datetime -> datetime(6) |
| 118093 | 2025-04-30 7:13 | 2025-04-30 18:06 | MySQL Server: FULLTEXT search | Verified (137 days) | S2 | 8.0.42 | Any | Any | Huge memory usage when inserting into a FTS table with a single transaction. |
| 118054 | 2025-04-24 16:23 | 2025-05-07 15:55 | MySQL Server: InnoDB storage engine | Verified (131 days) | S5 | Any | Any | Potential optimization in row_ins_sec_index_entry_low(): avoid second btr_cur_search_to_nth_level() under certain condit |
| Showing 1-20 of 2533 (Edit, Save, CSV, Feed) | Show Next 20 Entries » |
