| « Show Previous 30 Entries | Showing 31-60 of 118 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 111429 | 2023-06-15 6:44 | 2023-06-21 14:02 | MySQL Server: Optimizer | Verified (1131 days) | S3 | 8.0.22, 8.0.33 | Any | Any | Incorrect result when timestamp col apply <=> to the result of subquery |
| 111431 | 2023-06-15 8:47 | 2023-06-26 14:48 | MySQL Server: Optimizer | Verified (1131 days) | S3 | 8.0.33 | Ubuntu (22.04) | Other (x86_64) | condition_fanout_filter optimizer wrong result? |
| 111453 | 2023-06-16 0:54 | 2023-06-19 10:09 | MySQL Server: Optimizer | Verified (1127 days) | S2 | 8.0.33 | Any | Any | sql query with "where time_col not between val1 and null' has diffrent results |
| 111454 | 2023-06-16 2:24 | 2023-06-19 8:37 | MySQL Server: Optimizer | Verified (1127 days) | S3 | 8.0.33 | Any | Any | select query with json and time column has different results |
| 111471 | 2023-06-17 14:28 | 2023-06-18 13:26 | MySQL Server: Optimizer | Verified (1128 days) | S2 | 8.0.33 | Ubuntu | x86 | Unexpected Error: Memory capacity exceeded |
| 111484 | 2023-06-19 8:49 | 2023-06-19 9:10 | MySQL Server: Optimizer | Verified (1127 days) | S3 | mysql-8.0.33 | Linux | x86 | wrong result when rewriting scalar subquery in json function parameters |
| 111485 | 2023-06-19 11:16 | 2023-06-19 11:40 | MySQL Server: Optimizer | Verified (1127 days) | S3 | mysql-8.0.33 | Linux | x86 | When subquery_to_derived is on, IN-subq to derived table transformed wrongly |
| 111508 | 2023-06-21 7:06 | 2023-06-21 8:24 | MySQL Server: Optimizer | Verified (1125 days) | S3 | 8.0.33 | Any | Any | The query results are inconsistent when different optimizer options are used. |
| 111511 | 2023-06-21 8:38 | 2024-04-12 15:00 | MySQL Server: Optimizer | Verified (1125 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | CTE missing scope in set queries |
| 111559 | 2023-06-26 9:10 | 2026-06-17 14:48 | MySQL Server: Optimizer | Documenting (1120 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | View with CTE syntax error |
| 111669 | 2023-07-06 0:47 | 2023-07-12 13:04 | MySQL Server: Optimizer | Verified (1104 days) | S5 | 8.0.33 | Any | Any | Simple Query Times Out |
| 111699 | 2023-07-09 3:46 | 2023-07-10 5:51 | MySQL Server: Optimizer | Verified (1106 days) | S3 | 8.0.28, 8.0.33 | Any | Any | Incorrect results |
| 111700 | 2023-07-09 7:31 | 2023-07-12 5:55 | MySQL Server: Optimizer | Verified (1104 days) | S3 | 8.0.32, 8.0.33 | Any | Any | LIMIT values are not adequately handled in EXPLAIN. |
| 111706 | 2023-07-10 8:24 | 2025-03-17 9:33 | MySQL Server: Optimizer | Verified (1106 days) | S3 | 8.0.28, 8.0.33 | Any | Any | Incorrect result |
| 111728 | 2023-07-12 8:08 | 2023-07-12 8:42 | MySQL Server: Optimizer | Verified (1104 days) | S2 | 8.0.28, 8.0.33 | Any | Any | Incorrect result |
| 113288 | 2023-11-30 6:58 | 2026-06-07 8:48 | MySQL Server: Optimizer | Documenting (963 days) | S5 | 8.0.33 | Any | Any | Explain plan shows dynamic range, but bug causes no chance to use for LEFT JOIN |
| 113298 | 2023-12-01 4:41 | 2023-12-01 4:55 | MySQL Server: Optimizer | Verified (962 days) | S3 | 8.0.33, 8.1.0, 8.0.35 | Any | Any | Unexpected Results when Using IN for Floating-Point |
| 113513 | 2023-12-26 12:12 | 2023-12-27 5:20 | MySQL Server: Optimizer | Verified (936 days) | S3 | 8.0.33 | Any | Any | Join reordering regression and inconsistent behavior for SQL involving LEFT JOIN |
| 114714 | 2024-04-20 3:54 | 2025-05-09 12:41 | MySQL Server: Optimizer | Verified (819 days) | S3 | 8.0.33 | Any | Any | Duplicate subquery explain plan output when explain format is tree |
| 114970 | 2024-05-13 3:42 | 2024-05-13 6:04 | MySQL Server: Optimizer | Verified (798 days) | S1 | 8.0.33 | Any | Any | prev_record_reads() use stale cardinality to calculate after plan enumeration |
| 115208 | 2024-06-04 8:51 | 2026-07-03 8:48 | MySQL Server: Optimizer | Patch pending (776 days) | S3 | 8.0.33 | Any | Any | Last_query_cost could be negative number due to unmatched cost values in JOIN |
| 119581 | 2025-12-20 14:54 | 2025-12-22 19:17 | MySQL Server: Optimizer | Verified (210 days) | S3 | 8.0.33 | Ubuntu (22.04) | Any | FLOOR function shows inconsistent overflow handling |
| 110795 | 2023-04-25 5:45 | 2023-04-25 8:41 | MySQL Server: Locking | Verified (1182 days) | S3 | 8.0.27, 8.0.33, 5.7.42 | Any | Any | mysql insert is deadlocked |
| 111068 | 2023-05-18 8:38 | 2025-05-14 8:21 | MySQL Server: Locking | Verified (1159 days) | S2 | 8.0.25, 8.0.33 | Any | Any | Lock failure |
| 111072 | 2023-05-18 10:12 | 2024-04-10 10:04 | MySQL Server: JSON | Verified (1158 days) | S3 | 8.0.33, 5.7.42, 8.0.36 | Any | Any | The subquery involves JSON, and the execution result is incorrect. |
| 116703 | 2024-11-19 6:06 | 2024-11-19 6:28 | MySQL Server: JSON | Verified (608 days) | S3 | 8.0.33, 8.0.40, 8.4.3, 9.1.0 | Any | Any | `JSON_VALID` has inconsistent behavior for `NULL` |
| 110771 | 2023-04-23 7:46 | 2024-08-20 15:27 | MySQL Server: InnoDB storage engine | Verified (1183 days) | S2 | 8.0.33 | Any | Any | Failed to update NULL to empty value on instant col for REDUNDANT table |
| 111182 | 2023-05-29 9:15 | 2024-04-10 7:04 | MySQL Server: InnoDB storage engine | Verified (1141 days) | S3 | 8.0.33, 8.0.36 | Any | Any | buffer pool online resize warning message incorrect |
| 111261 | 2023-06-02 17:38 | 2023-06-05 6:09 | MySQL Server: InnoDB storage engine | Verified (1141 days) | S3 | 8.0.32, 8.0.33 | Any | Any | Skip scan results in wrong query results |
| 111570 | 2023-06-26 20:03 | 2023-06-28 0:31 | MySQL Server: InnoDB storage engine | Verified (1118 days) | S3 | 8.0.33, 5.7.42 | Any | Any | Looking for inexistent data reports 0 rows examined |
| « Show Previous 30 Entries | Showing 31-60 of 118 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
