| « Show Previous 30 Entries | Showing 31-38 of 38 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 86683 | 2017-06-13 17:37 | 2022-08-17 22:04 | MySQL for Windows: Installer | Closed (1063 days) | S3 | Any | Any | MySQLInstallerConsole.exe -silent doesn't work on upgrade | |
| 108436 | 2022-09-08 16:16 | 2022-09-09 4:39 | MySQL Server: Errors | Verified (1040 days) | S3 | 8.0.30, 5.7.39 | Any | Any | typo in ER_IB_MSG_RECOVERY_CHECKPOINT_OUTSIDE_LOG_FILE |
| 108471 | 2022-09-13 12:16 | 2022-09-13 13:19 | MySQL Server: InnoDB storage engine | Verified (1036 days) | S3 | 8.0.30 | Any | Any | Allow redo log register UDF to specify a register name |
| 107224 | 2022-05-05 17:01 | 2022-09-19 9:19 | MySQL Server: Logging | Verified (1166 days) | S3 | 8.0.29 | Any | Any | missleading Redo log format is error |
| 107894 | 2022-07-15 10:58 | 2023-04-19 13:18 | MySQL Server: Command-line Clients | Can't repeat (818 days) | S3 | 8.0 | Any | Any | mysql client crash when FIDO device is not present |
| 112189 | 2023-08-26 23:41 | 2023-08-28 9:58 | MySQL Server: Replication | Verified (687 days) | S3 | 8.0 | Any | Any | Binlog::EventHeader position overflow |
| 112608 | 2023-10-03 16:37 | 2024-03-14 10:56 | MySQL Server: InnoDB storage engine | Closed (489 days) | S3 | 8.0 | Any | Any | redo log consumer cannot advance |
| 103684 | 2021-05-13 12:43 | 2025-05-07 16:46 | MySQL Server: Logging | Verified (1524 days) | S3 | 8.0.24 | Any | Any | Warning issued when querying ps. keyring_component_status |
| « Show Previous 30 Entries | Showing 31-38 of 38 (Edit, Save, CSV, Feed) |
