Showing all 9 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
99444 | 2020-05-05 9:28 | 2020-05-13 20:52 | MySQL Server: Optimizer | Not a Bug (1443 days) | S1 | 8.0.20 | CentOS (64G RAM) | x86 (Intel(R) Xeon(R) CPU E5-2665 0 @ 2.40GHz) | New HASH JOIN order problem |
99244 | 2020-04-14 3:22 | 2020-04-22 12:45 | MySQL Server: Optimizer | Verified (1465 days) | S1 | 8.0.19 | Any | Any | bad performance in hash join because join with no join condition between tables |
100783 | 2020-09-09 12:29 | 2020-09-10 4:50 | MySQL Server: Optimizer | Can't repeat (1323 days) | S2 | 8.0.19 | Any | Any | wrong result with hash join |
99943 | 2020-06-20 20:34 | 2021-02-17 14:23 | MySQL Server: Optimizer | Not a Bug (1163 days) | S3 | 8.0.20 | Linux | Any | Hash join does not work for Semijoin and Antijoin |
97979 | 2019-12-13 5:15 | 2020-02-12 13:06 | MySQL Server | Not a Bug (1534 days) | S3 | 8.0.18 | Any | Any | MySQL Feature Request: hash joins should be able to use an index |
108621 | 2022-09-27 8:38 | 2022-10-06 16:25 | MySQL Server: Documentation | Closed (567 days) | S3 | current | Any | Any | mysql 8.0 Chapter (8.2.1.4 Hash Join Optimization) Document content error |
111564 | 2023-06-26 12:33 | 2023-08-10 12:21 | MySQL Server: Optimizer | Closed (259 days) | S3 | 8.0 | Any | Any | Contribution by Tencent: explain format=tree lost the subquery in the hash join |
114027 | 2024-02-17 19:34 | 2024-02-19 6:29 | MySQL Server: Optimizer | Verified (66 days) | S3 | 8.0.36 & 8.3.0 | Windows (10 & 11) | ARM (x64) | Plans for inner hash join show that wrong table is hashed |
112198 | 2023-08-28 8:21 | 2024-03-05 6:06 | MySQL Server: Optimizer | Verified (241 days) | S1 | 8.0, 8.0.34 | Any | Any | Incorrect multiple equality optimization causes performance degradation |
Showing all 9 (Edit, Save, CSV, Feed) |