| Showing 1-30 of 392 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 109668 | 2023-01-17 21:56 | 2024-11-05 2:50 | MySQL Server: Group Replication | Verified (976 days) | S2 | 8.0.27, 8.0.33 | CentOS | x86 | XCom connection stalled forever in read() syscall over network |
| 110430 | 2023-03-20 7:11 | 2023-03-30 2:49 | MySQL Server: Replication | Verified (1052 days) | S3 | 8.0 | Any | Any | XA COMMIT may not persist GTID into undo header |
| 110533 | 2023-03-28 15:49 | 2024-05-17 9:29 | MySQL Server: Replication | Verified (1051 days) | S3 | 8.0.32 | Any | Any | XA COMMIT may not be recovered after a crash |
| 83313 | 2016-10-09 9:08 | 2017-01-20 4:41 | MySQL Server: InnoDB storage engine | Verified (3310 days) | S3 | 5.7 | Any | Any | write to log file before crash recovery if need to fixup undo-trunc |
| 112191 | 2023-08-28 2:52 | 2023-08-29 9:45 | MySQL Server: Compiling | Verified (898 days) | S3 | 8.0.31 | Any | Any | When we compile MySQL 8.0 with DEBUG, we have some warning of memory leak |
| 116319 | 2024-10-09 6:50 | 2024-10-10 3:58 | MySQL Server: InnoDB storage engine | Verified (491 days) | S2 | 8.0, 8.4, 8.0.39 | Any | Any | When locks exhaust the BP, an incorret assert about semi_consistent causes crash |
| 116707 | 2024-11-19 11:49 | 2024-11-19 12:21 | MySQL Server: DDL | Verified (450 days) | S3 | 8.0 | Any | Any | when innodb_optimize_fulltext_only=ON, optimize table return OK always |
| 115019 | 2024-05-15 18:03 | 2024-10-23 8:49 | MySQL Server: Command-line Clients | Verified (477 days) | S3 | 8.4.0 | Any | Any | Warnings for time zone files that can't be loaded |
| 103684 | 2021-05-13 12:43 | 2025-05-07 16:46 | MySQL Server: Logging | Verified (1736 days) | S3 | 8.0.24 | Any | Any | Warning issued when querying ps. keyring_component_status |
| 83307 | 2016-10-08 9:17 | 2016-12-21 6:24 | MySQL Server: InnoDB storage engine | Verified (3340 days) | S3 | 5.7, 8.0 | Any | Any | Wakeup purge thread while enabling innodb_undo_log_truncate |
| 32911 | 2007-12-02 13:27 | 2020-02-20 15:40 | MySQL Server: XML functions | Verified (6647 days) | S3 | 5.1, 6.0 | Any | Any | Variable used as XPath expressions treated as empty string |
| 80646 | 2016-03-07 21:15 | 2016-03-17 22:49 | MySQL Server: InnoDB storage engine | Verified (3628 days) | S3 | Any | Any | ut_delay missing compile barrier (backport to 5.6) (contribution) | |
| 88399 | 2017-11-08 8:39 | 2018-02-18 18:29 | MySQL Server: InnoDB storage engine | Verified (2976 days) | S5 | 5.7,8.0 | Linux | ARM | Using CAS for trylock in place of TAS for EventMutex (arm64) |
| 116611 | 2024-11-11 11:20 | 2024-11-11 12:09 | MySQL Server: Optimizer | Verified (458 days) | S3 | 8.4.3, 8.0.40 | Any | Any | user defined histogram import error for bigint data |
| 107160 | 2022-04-29 8:19 | 2024-03-04 4:11 | MySQL Server: Stored Routines | Verified (1385 days) | S2 | 8.0.29 | Any | Any | Upgrade from 5.7 to 8.0 fails with syntax error while parsing an event |
| 66079 | 2012-07-30 2:59 | 2012-08-01 14:19 | MySQL Server: InnoDB storage engine | Verified (4945 days) | S5 | 5.5+ | Any | Any | unnecessary calling trx_sys_update_mysql_binlog_offset when sql_log_bin=0 |
| 88221 | 2017-10-25 9:53 | 2017-11-17 2:01 | MySQL Server: DDL | Verified (3030 days) | S3 | 5.7.17 | Any | Any | Unique index identification error at create/alter table |
| 115782 | 2024-08-06 11:24 | 2024-08-06 11:55 | MySQL Server: Optimizer | Verified (555 days) | S3 | 8.0.30,8.4.0 | Any | Any | unfair comparison between materialization and EXISTS |
| 117237 | 2025-01-19 4:13 | 2025-01-21 11:41 | MySQL Server: InnoDB storage engine | Verified (387 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Duplicate Error in DDL Row Log Apply |
| 115242 | 2024-06-06 8:43 | 2024-06-20 12:56 | MySQL Server: InnoDB storage engine | Verified (602 days) | S3 | 8.0.37, 8.4.0 | Any | Any | Unexpected dd_table_open_on_id_low() failure on concurrent RENAME TABLE |
| 118476 | 2025-06-18 8:45 | 2025-07-02 14:47 | MySQL Server: DDL | Verified (239 days) | S2 | 8.0, 8.4 | Red Hat | x86 | Unable to create partition with name '1e3fRQM2GhI' |
| 87293 | 2017-08-03 5:49 | 2018-02-18 18:29 | MySQL Server: InnoDB storage engine | Verified (3047 days) | S2 | 5.7, 8.0 | Linux | ARM | TTASFutex Lock release barrier (aarch64) |
| 60345 | 2011-03-04 17:11 | 2013-01-15 15:25 | MySQL Server | Verified (4776 days) | S5 | 5.1.55 6.0.11 | Any | Any | trim trailing spaces processes data only byte wise (the continue of bug14637) |
| 60351 | 2011-03-04 22:15 | 2013-01-15 15:27 | MySQL Server | Verified (4776 days) | S5 | 5.1.55 | Any | Any | trim same character processes data only byte wise (continue of bug14637 (4)) |
| 115988 | 2024-09-03 15:03 | 2025-10-06 12:45 | MySQL Server: InnoDB storage engine | Verified (129 days) | S5 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | Too Much Disk Read on Startup, penalizing deployments with many tables (1M+). |
| 113251 | 2023-11-28 11:54 | 2023-11-29 9:24 | MySQL Server: Row Based Replication ( RBR ) | Verified (806 days) | S3 | MySQL8.0 | Any | Any | the slow log in slave is logged ,when binlog_format is row |
| 117115 | 2025-01-07 7:12 | 2025-02-10 5:50 | MySQL Server: Replication | Verified (367 days) | S3 | 5.7.44, 8.0.40 | Any | Any | The server_id of the record written to the error log by semisync is incorrect |
| 85307 | 2017-03-04 13:53 | 2018-11-07 13:01 | MySQL Server: InnoDB storage engine | Verified (3257 days) | S3 | 5.7 | Any | Any | The server refuses to restart if turn off innodb_log_checksums |
| 111966 | 2023-08-04 4:04 | 2023-08-09 7:14 | MySQL Server: Logging | Verified (918 days) | S3 | 5.7.21 | Any (7.3) | Any | The information indicating abnormal operation of mysql data files is insufficien |
| 94139 | 2019-01-30 12:39 | 2019-01-31 7:46 | MySQL Server: Logging | Verified (2569 days) | S3 | 5.7.18, 5.7.25 | Any | Any | The first few lines of the error log with wrong timezone when start mysqld |
| Showing 1-30 of 392 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
