| Showing all 6 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 120739 | 2026-06-22 11:42 | 2026-06-22 11:56 | MySQL Server: Replication | Open | S1 | 5.7.25 | Linux | x86 | Corruption of the index file caused stale binary log entries to be re-applied after executing FLUSH LOGS |
| 120738 | 2026-06-22 10:55 | 2026-06-22 11:26 | MySQL Server: Replication | Open | S1 | 5.7.25 | Linux (6) | 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 (43 days) | S3 | 5.7 | Any | Any | REPEATABLE READ: no-change UPDATE causes MVCC Rule 1 violation — transaction cannot see own modification |
| 120268 | 2026-04-14 19:38 | 2026-05-05 13:11 | MySQL Server: Documentation | Verified (72 days) | S1 | 5.7, 8.0, 8.4, 9.x | Any | Any | Clarify Symbolic Link Usage and Alternative for InnoDB |
| 120238 | 2026-04-09 9:16 | 2026-04-09 9:34 | MySQL Server: Replication | Open | S3 | 5.7 8.0 | Linux | Any | maybe cause "could not find next log" if rotate binary log without fsync @@log_bin_index's parent dir |
| 120177 | 2026-03-30 6:38 | 2026-04-01 12:10 | MySQL Server: Replication | Open | S3 | 5.7.44 | Any | Any | Lost gtids after crash recovery |
| Showing all 6 (Edit, Save, CSV, Feed) |
