| Showing 1-30 of 148 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 114538 | 2024-04-03 7:13 | 2024-04-03 10:34 | MySQL Server: Optimizer | Can't repeat (22 days) | S3 | 8.0 | Any | Any | Item_ref replaced by new item in Item_ref::transform lead to wrong result |
| 113529 | 2023-12-30 16:04 | 2024-01-02 9:32 | MySQL Server: Optimizer | Can't repeat (114 days) | S1 | 8.2.0 | Ubuntu | Any | Unexpectedly exceeding memory capacity after adding a unique index |
| 113054 | 2023-11-12 10:36 | 2023-11-13 10:40 | MySQL Server: Optimizer | Can't repeat (164 days) | S3 | 8.0.32 | CentOS | Any | mysql explain filtered inaccurate when find_in_set function used |
| 113035 | 2023-11-10 6:05 | 2023-11-10 12:43 | MySQL Server: Optimizer | Can't repeat (167 days) | S3 | CentOS | Any | why MySQL 8.0.32 chooses wrong drive tables in this situation | |
| 112453 | 2023-09-25 7:42 | 2023-09-25 11:28 | MySQL Server: Optimizer | Can't repeat (213 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
| 112454 | 2023-09-25 7:50 | 2023-09-25 11:26 | MySQL Server: Optimizer | Can't repeat (213 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
| 112378 | 2023-09-19 2:03 | 2023-09-25 11:01 | MySQL Server: Optimizer | Can't repeat (214 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
| 112251 | 2023-09-04 13:19 | 2023-09-05 12:11 | MySQL Server: Optimizer | Can't repeat (233 days) | S3 | 8.1.0 | Any | Any | Uncertain Result |
| 111414 | 2023-06-14 9:26 | 2023-06-16 9:32 | MySQL Server: Optimizer | Can't repeat (314 days) | S3 | 8.0.33 | Any | Any | HASH JOIN results in wrong query results |
| 111198 | 2023-05-30 10:42 | 2023-05-30 12:11 | MySQL Server: Optimizer | Can't repeat (331 days) | S3 | 8.0.31 | Any | Any | Using index for skip scan optimization produces wrong result |
| 108808 | 2022-10-18 7:25 | 2022-10-18 12:41 | MySQL Server: Optimizer | Can't repeat (555 days) | S5 | 8.0.27 | Red Hat (CentOS Linux release 7.9.2009 (Core)) | x86 | MySQL optimizer: the execution order of explain execution plan and explain analy |
| 108686 | 2022-10-05 11:08 | 2022-10-05 14:02 | MySQL Server: Optimizer | Can't repeat (568 days) | S3 | 8.0.28 | Any | x86 | Bug usibg limit 1 sub select |
| 108640 | 2022-09-29 7:05 | 2022-09-29 8:37 | MySQL Server: Optimizer | Can't repeat (574 days) | S3 | 8.0.28 | Any | Any | multi-valued index with composite index get wrong result |
| 108620 | 2022-09-27 2:39 | 2022-09-27 6:06 | MySQL Server: Optimizer | Can't repeat (576 days) | S3 | 8.0.28 | Any | Any | Wrong count when choosing json index |
| 42240 | 2009-01-21 14:36 | 2022-09-01 7:08 | MySQL Server: Optimizer | Can't repeat (602 days) | S2 | 5.1-bzr, 6.0-bzr | Any | Any | Query returns non-matching rows with Innodb + IN + ORDER BY pk |
| 42677 | 2009-02-08 3:26 | 2022-09-01 6:54 | MySQL Server: Optimizer | Can't repeat (602 days) | S3 | 5.0 and 5.1 | Any | Any | MySQL Optimizer does not work right with truncation |
| 107363 | 2022-05-22 14:01 | 2022-05-23 7:18 | MySQL Server: Optimizer | Can't repeat (703 days) | S2 | 8.0.25 | Any | Any | Unexpected results if the query with subquery, FLOOR and GROUP BY. |
| 106944 | 2022-04-07 12:28 | 2022-05-09 11:53 | MySQL Server: Optimizer | Can't repeat (717 days) | S5 | 8.0 | Any | Any | can_switch_from_ref_to_range() doesn't work for prepare statement |
| 106154 | 2022-01-13 3:34 | 2022-01-13 7:47 | MySQL Server: Optimizer | Can't repeat (833 days) | S3 | 8.0.25 | Any | Any | Got different query result between 5.7.33 and 8.0.25 |
| 105437 | 2021-11-03 7:53 | 2021-11-03 9:05 | MySQL Server: Optimizer | Can't repeat (904 days) | S3 | 8.0.23 | Any | Any | Wrong answer when got multiple count(distinct) |
| 101308 | 2020-10-26 0:35 | 2020-10-26 8:46 | MySQL Server: Optimizer | Can't repeat (1277 days) | S1 | 8.0.21 | Any | Any | CROSS JOIN LATERAL and semantically equal CROSS JOIN WHERE have different result |
| 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 |
| 100196 | 2020-07-13 2:19 | 2020-07-14 8:35 | MySQL Server: Optimizer | Can't repeat (1381 days) | S3 | 8.0.18 | Any | Any | The results of REGEXP_SUBSTR() are different |
| 98942 | 2020-03-13 11:53 | 2020-03-18 13:55 | MySQL Server: Optimizer | Can't repeat (1504 days) | S3 | 8.0.19 | Any | Any | Inconsistent results for the queries which should return same result |
| 77403 | 2015-06-18 12:27 | 2020-03-05 12:52 | MySQL Server: Optimizer | Can't repeat (1512 days) | S2 | 5.6.25 | Linux | Any | MySQL server 5.6 consumes all memory on server when running query |
| 8168 | 2005-01-27 18:09 | 2020-02-05 15:35 | MySQL Server: Optimizer | Can't repeat (1541 days) | S3 | 5.0-bk | Any | Any | HELP commands processing different from regular with --ps-protocol |
| 10312 | 2005-05-02 11:51 | 2020-01-14 21:56 | MySQL Server: Optimizer | Can't repeat (1563 days) | S2 | 5.0.4 | Linux (linux debian) | Any | subquery cant be optimized correctly |
| 97462 | 2019-11-03 15:05 | 2019-11-12 16:37 | MySQL Server: Optimizer | Can't repeat (1626 days) | S5 | 8.0.17 | FreeBSD (12.0) | x86 | Slow JOIN with ORDER BY due wrong index selection |
| 96464 | 2019-08-08 8:39 | 2019-09-23 16:15 | MySQL Server: Optimizer | Can't repeat (1676 days) | S3 | 8.0 | Windows | Any | bug about json_table function |
| 95678 | 2019-06-06 21:22 | 2019-07-08 12:38 | MySQL Server: Optimizer | Can't repeat (1753 days) | S2 | 5.6.33 | Ubuntu | x86 | query gives empty result when using index_merge |
| Showing 1-30 of 148 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
