Showing 1-30 of 192 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
115988 | 2024-09-03 15:03 | 2024-09-12 2:11 | MySQL Server: InnoDB storage engine | Verified (17 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+). |
115931 | 2024-08-26 12:32 | 2024-08-26 14:32 | MySQL Server: InnoDB storage engine | Verified (26 days) | S3 | 8.0.39, 8.4.0 | Any | Any | MySQL hangs on installing plugin with innodb_thread_concurrency=1 |
115842 | 2024-08-15 8:21 | 2024-08-20 7:37 | MySQL Server: DML | Verified (37 days) | S2 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | The count distinct aggregation funciton of UUID returned an error value |
115519 | 2024-07-05 4:24 | 2024-07-16 13:34 | MySQL Server: Optimizer | Verified (67 days) | S2 | 8.2, 8.4.1 | Any | Any | INTERSECT within correlated subquery results in incorrect result |
114924 | 2024-05-08 14:01 | 2024-07-02 9:48 | MySQL Server: InnoDB storage engine | Verified (121 days) | S5 | 8.0.37 | Any | Any | Significant regression between 8.0.25 and 8.0.37 in a simple OLTP workload |
115017 | 2024-05-15 14:44 | 2024-07-01 11:21 | MySQL Server: Optimizer | Verified (129 days) | S2 | 8.0 | Any | Any | Wrong row estimate for range scan |
101828 | 2020-12-02 2:37 | 2024-06-25 7:48 | MySQL Server: Replication | Verified (88 days) | S2 | 8.0.37 | CentOS | x86 | Hash scan incorrectly applied the log resulting in HA_ERR_END_OF_FILE |
115353 | 2024-06-17 7:22 | 2024-06-21 6:40 | MySQL Server: Optimizer | Verified (96 days) | S2 | 8.0.37, 8.4.0 LTS | Any | Any | Setting index_merge_union leads to incorrect results. |
115122 | 2024-05-25 11:17 | 2024-06-16 9:10 | MySQL Server: Optimizer | Verified (97 days) | S5 | 8.4 (Latest), 8.0.37 | Ubuntu (22.04 LTS) | ARM | Unneeded full table scan, although there is an index and condition |
112362 | 2023-09-15 20:19 | 2024-06-10 7:46 | MySQL Server: Optimizer | Verified (362 days) | S5 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 | WHERE NOT IN with subquery is much slower on 8.1 than 5.7 |
114581 | 2024-04-08 11:24 | 2024-04-08 12:37 | MySQL Server: Optimizer | Verified (166 days) | S2 | 8.0.36 | Any | Any | Constant-Folding optimization negative constant truncate gives wrong operator |
114568 | 2024-04-07 13:43 | 2024-04-08 7:28 | MySQL Server: Optimizer | Verified (166 days) | S1 | 8.0.36 | Any | Any | Different join orders cause inconsistent results |
113464 | 2023-12-19 17:40 | 2024-03-12 11:05 | MySQL Server: Optimizer | Verified (276 days) | S2 | 8.0.27 | Any | Any | >= 8.0.27 Error 1048 when updating row with empty_sql mode |
105004 | 2021-09-22 10:20 | 2024-02-22 19:27 | MySQL Server: Parser | Verified (1094 days) | S2 | 8.0.26 | Any | Any | mysql 8.0 parser consuming more memory than 5.7 for similar query |
114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (212 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
113892 | 2024-02-05 10:39 | 2024-02-05 14:13 | MySQL Server: Optimizer | Verified (229 days) | S3 | 8.0 | Any | Any | FORCE INDEX reports wrong number of rows |
113800 | 2024-01-30 5:30 | 2024-01-31 8:28 | MySQL Server: DML | Verified (234 days) | S5 | 8.0.22, 8.0.36, 8.0.11 | Linux | x86 | Performance degradation of Blob operations comparing with MySQL 5.7 |
113768 | 2024-01-26 2:40 | 2024-01-26 8:53 | MySQL Server: DML | Verified (239 days) | S3 | 8.0.35 | Linux | Any | return error with cast |
68925 | 2013-04-11 5:57 | 2024-01-02 6:19 | MySQL Server: Command-line Clients | Verified (3688 days) | S3 | 5.6.10, 5.5.29, 8.0.35 | Any | Any | Compatibility issue with mysql history ("\040" instead of space) |
113303 | 2023-12-01 7:29 | 2023-12-05 4:54 | MySQL Server: Optimizer | Verified (295 days) | S5 | 8.0.35 | Any | Any | Explain plan takes forever when there are more joins |
113301 | 2023-12-01 7:22 | 2023-12-01 8:53 | MySQL Server: Prepared statements | Verified (295 days) | S2 | 8.0.35, 8.0.31 | Any | Any | using preparation statement to query the time type data, some data is not found |
110998 | 2023-05-11 15:33 | 2023-12-01 6:49 | MySQL Server: Optimizer | Verified (493 days) | S5 | 8.0.20+, 8.0.33 | Linux | Any | Performance regression with SELECT query when sorting on limited fields |
105975 | 2021-12-25 3:13 | 2023-11-28 9:44 | MySQL Server: Optimizer | Verified (1001 days) | S2 | 8.0.22,8.0.27 | Linux | Any | When I set duplicateweedout=ON,I got an incorrect query result. |
111484 | 2023-06-19 8:49 | 2023-06-19 9:10 | MySQL Server: Optimizer | Verified (460 days) | S3 | mysql-8.0.33 | Linux | x86 | wrong result when rewriting scalar subquery in json function parameters |
109726 | 2023-01-20 21:35 | 2023-05-29 12:01 | MySQL Server: Optimizer | Verified (607 days) | S2 | 8.0.31 | Ubuntu | x86 | Incorrect results with aggregated functions on correlated lateral joins |
110706 | 2023-04-17 2:56 | 2023-05-17 2:31 | MySQL Server: InnoDB storage engine | Verified (493 days) | S2 | 8.0.32 | Any | Any | Data will be lost when the table structure is rebuilt. |
107059 | 2022-04-19 20:45 | 2023-05-09 15:07 | MySQL Server: InnoDB storage engine | Verified (501 days) | S3 | 5.7.37 ,5.7.27, 5.7.42 | Any | Any | Bad compression stats in I_S.INNODB_CMP starting in 5.7.27 (8.0 not affected). |
110819 | 2023-04-26 15:11 | 2023-05-08 22:48 | MySQL Server: Optimizer | Verified (513 days) | S2 | 8.0.16+, 8.0.33 | Any | Any | EXISTS with dependent subquery can return incorrect results |
109390 | 2022-12-15 8:02 | 2023-05-01 15:02 | Connector / NET | Verified (646 days) | S2 | 8.0.31 | Any | Any | Transaction lock held after connection timeout exception |
109339 | 2022-12-12 12:44 | 2023-04-10 22:02 | Connector / J | Verified (646 days) | S3 | 8.0.22, 8.0.31 | Any | Any | Failed to insert bignums due to overflow |
Showing 1-30 of 192 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |