| Showing all 6 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 121314 | 2026-09-18 10:03 | 2026-09-30 14:48 | MySQL Server: Replication | Documenting (31 days) | S2 | 8.0.40/5.7.44 | Any | Any | MTS recovery silently skips transactions, leaving holes in gtid_executed |
| 121065 | 2026-08-07 9:16 | 2026-08-11 12:42 | MySQL Server: InnoDB storage engine | Open | S1 | 8.4.10, 8.0.45, 5.7.39 | Linux | x86 | mysqld crashes with signal 11 while OPTIMIZE and concurrent DML on the same table |
| 121055 | 2026-08-04 22:14 | 2026-08-04 22:26 | MySQL Server: Documentation | Open (79 days) | S2 | 8.0, 8.4, 9.7 and 26.7.0 (and 5.7) | Any | Any | The documentation of gtid_purged (and more) is incomplete since 8.0.17. |
| 121021 | 2026-07-28 11:40 | 2026-07-28 11:40 | MySQL Server: Connection Handling | Open | S3 | 5.7 (all), 8.0 (all, verified on 8.0.x s | Linux | Any | Shutdown can hang: lost SIGUSR1/SIGALRM between abort-flag check and poll() in connection accept loop |
| 120739 | 2026-06-22 11:42 | 2026-10-07 14:17 | MySQL Server: Replication | Need Feedback (15 days) | S1 | 5.7.25 | Linux | x86 | Corruption of the index file caused stale binary log entries to be re-applied after executing FLUSH LOGS |
| 120610 | 2026-06-03 12:00 | 2026-06-03 12:21 | MySQL Server: InnoDB storage engine | Open (141 days) | S3 | 5.7 | Any | Any | REPEATABLE READ: no-change UPDATE causes MVCC Rule 1 violation — transaction cannot see own modification |
| Showing all 6 (Edit, Save, CSV, Feed) |
