Showing 1-30 of 149 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
113035 | 2023-11-10 6:05 | 2023-11-10 12:43 | MySQL Server: Optimizer | Can't repeat (161 days) | S3 | CentOS | Any | why MySQL 8.0.32 chooses wrong drive tables in this situation | |
10243 | 2005-04-28 20:36 | 2005-06-08 17:34 | MySQL Server: Optimizer | Can't repeat (6890 days) | S3 | 5.0.4/BK source | Windows (winXP) | Any | -SUM() crash |
30659 | 2007-08-28 1:03 | 2007-08-31 9:59 | MySQL Server: Optimizer | Can't repeat (6076 days) | S3 | 5.2.6 | Linux (2.6.20) | Any | 300% Performance Regression 5.0.45 -> 5.2.6 on Correlated Subquery |
41816 | 2009-01-01 4:35 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (4947 days) | S1 | 5.1.30 | Windows | Any | another multi-table crash with derived tables |
46094 | 2009-07-09 16:19 | 2011-02-16 23:44 | MySQL Server: Optimizer | Can't repeat (4937 days) | S2 | 5.1.37-debug | Any | Any | Assertion failed: inited==RND if filesort interrupted |
38011 | 2008-07-10 11:09 | 2008-11-07 16:07 | MySQL Server: Optimizer | Can't repeat (5642 days) | S1 | 6.0 | Any | Any | Bad data returned with date comparison and ORDER BY with Innodb |
38015 | 2008-07-10 13:11 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5331 days) | S2 | 6.0,5.4 | Any | Any | Bad result: inconsistent treatment of comparisons between data types in subquery |
96464 | 2019-08-08 8:39 | 2019-09-23 16:15 | MySQL Server: Optimizer | Can't repeat (1670 days) | S3 | 8.0 | Windows | Any | bug about json_table function |
108686 | 2022-10-05 11:08 | 2022-10-05 14:02 | MySQL Server: Optimizer | Can't repeat (562 days) | S3 | 8.0.28 | Any | x86 | Bug usibg limit 1 sub select |
106944 | 2022-04-07 12:28 | 2022-05-09 11:53 | MySQL Server: Optimizer | Can't repeat (711 days) | S5 | 8.0 | Any | Any | can_switch_from_ref_to_range() doesn't work for prepare statement |
21418 | 2006-08-02 15:04 | 2006-08-23 14:36 | MySQL Server: Optimizer | Can't repeat (6449 days) | S2 | 5.0.22/4.1;5.0;5.1BK | Linux (Linux (FC3)) | Any | Correlated subqueries with UNIQUE columns used in WHERE clause are incorrect |
46797 | 2009-08-18 22:04 | 2011-02-16 23:44 | MySQL Server: Optimizer | Can't repeat (5267 days) | S3 | 6.0 | Any | Any | Crash in fix_semijoin_strategies_for_picked_join_order with semijoin=on |
58555 | 2010-11-29 10:38 | 2011-07-05 18:26 | MySQL Server: Optimizer | Can't repeat (4672 days) | S1 | bzr_WL5274 | Any | Any | Crash in heap_scan_init at line 30 in hp_scan.c on nested subqueries in FROM |
37415 | 2008-06-15 17:56 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5259 days) | S1 | 6.0 | Any | Any | Crash in row_sel_field_store_in_mysql_format on multiple-table update (innodb) |
29158 | 2007-06-17 7:46 | 2007-06-17 14:35 | MySQL Server: Optimizer | Can't repeat (6151 days) | S1 | 5.0.42 | Windows | Any | crash on cleanup after out of memory scenerio |
33496 | 2007-12-24 8:22 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5593 days) | S1 | 6.0.4 | Any | Any | Crash when reading from Falcon table into variable |
101308 | 2020-10-26 0:35 | 2020-10-26 8:46 | MySQL Server: Optimizer | Can't repeat (1271 days) | S1 | 8.0.21 | Any | Any | CROSS JOIN LATERAL and semantically equal CROSS JOIN WHERE have different result |
44962 | 2009-05-19 19:34 | 2012-10-22 8:10 | MySQL Server: Optimizer | Can't repeat (4197 days) | S5 | 5.1.34, 5.1.36-bzr, 5.1.40-bzr | Linux | Any | DEPENDENT SUBQUERY not using a range index, resulting in slow performance |
33037 | 2007-12-06 12:49 | 2007-12-07 8:43 | MySQL Server: Optimizer | Can't repeat (5978 days) | S5 | 5.0.22-pro-nt-log | Any | Any | Different and much slower access plan used for select when used with insert into |
17590 | 2006-02-20 17:44 | 2006-02-23 9:32 | MySQL Server: Optimizer | Can't repeat (6630 days) | S2 | 5.1.7-beta | Any (All) | Any | Different key-len and # rows reported on all platforms |
45928 | 2009-07-03 0:41 | 2011-02-16 23:44 | MySQL Server: Optimizer | Can't repeat (5307 days) | S3 | 5.4 | Any | Any | Differing query results depending on MRR and engine_condition_pushdown settings |
13646 | 2005-09-30 10:28 | 2006-03-24 12:24 | MySQL Server: Optimizer | Can't repeat (6601 days) | S3 | 4.1.14 | Windows (Windows, Linux) | Any | DISTINCT returns not all expected results |
26925 | 2007-03-07 17:19 | 2007-04-26 12:52 | MySQL Server: Optimizer | Can't repeat (6203 days) | S3 | 4.1.15 | Linux (Linux 2.6.8-022stab078-9) | Any | Empty result in MAX after creation of KEY |
89819 | 2018-02-27 7:17 | 2018-02-27 8:37 | MySQL Server: Optimizer | Can't repeat (2243 days) | S3 | 5.7.20 | Any | Any | Equivalent queries produce different results with LEFT JOIN |
11162 | 2005-06-08 9:55 | 2005-06-15 10:27 | MySQL Server: Optimizer | Can't repeat (6883 days) | S3 | 5.0.7 | all Unix | Any | Execution of prepared "explain select" shows different output |
68871 | 2013-04-05 7:32 | 2014-08-27 4:36 | MySQL Server: Optimizer | Can't repeat (3523 days) | S3 | 5.1.58, 5.5.30, 5.6.10 | Any | Any | EXPLAIN does not show real plan used for query with HAVING |
53442 | 2010-05-05 16:10 | 2011-02-16 23:44 | MySQL Server: Optimizer | Can't repeat (5098 days) | S3 | 5.1.46 - community | Windows | Any | EXPLAIN doesn't detec an index-covered query with InnoDB |
38056 | 2008-07-11 19:14 | 2014-11-03 14:22 | MySQL Server: Optimizer | Can't repeat (3455 days) | S3 | 4.1, 5.0, 5.1, 6.0-bk, | Any | Any | EXPLAIN doesn't report "Using where" for a LEFT JOIN query with ON expression |
9930 | 2005-04-15 13:53 | 2005-05-11 16:23 | MySQL Server: Optimizer | Can't repeat (6918 days) | S3 | 5.0.3-beta-debug | Linux (Linux linux 2.6.8-24.14-smp #1 S) | Any | EXPLAIN for SELECT on view |
39756 | 2008-09-30 12:59 | 2014-05-05 5:54 | MySQL Server: Optimizer | Can't repeat (3637 days) | S5 | 6.0,5.4, 5.1 | Any | Any | EXPLAIN for uncorrelated NOT EXISTS query is slow |
Showing 1-30 of 149 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |