Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
53121 | 2010-04-23 16:32 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5079 days) | S2 | 5.0.26 | Linux (OpenSUSE) | Any | INSERT and unindexed SELECT on same table deadlock even with low LIMIT |
69390 | 2013-06-03 18:27 | 2018-04-24 1:00 | MySQL Server: Optimizer | No Feedback (2187 days) | S2 | 5.6.11 | Linux (Oracle Linux 6.4) | Any | Query is more than 2 orders of magnitude slower on MySQL 5.6.11 |
64043 | 2012-01-16 16:31 | 2012-02-19 1:00 | MySQL Server: Optimizer | No Feedback (4443 days) | S1 | 5.5.19 | Linux (EL6) | Any | After version upgrade form 5.0.26 to mysql server 5.5.19 performance degraded |
63727 | 2011-12-12 22:39 | 2012-01-14 1:00 | MySQL Server: Optimizer | No Feedback (4479 days) | S2 | 14.12 | Linux (CentOS) | Any | Full Table Scan when joining table multiple times with in clause |
63173 | 2011-11-09 21:15 | 2011-12-14 7:00 | MySQL Server: Optimizer | No Feedback (4510 days) | S1 | 5.1, 5.5 | Linux | Any | MySql hangs in state statistics - only with specific amount of data-rows |
61983 | 2011-07-26 12:13 | 2011-09-28 23:00 | MySQL Server: Optimizer | No Feedback (4587 days) | S2 | 5.1.48 | Any | Any | strange explain plan results |
61852 | 2011-07-13 11:23 | 2011-09-14 23:00 | MySQL Server: Optimizer | No Feedback (4600 days) | S3 | 5.1.54 | Linux | Any | Query returns wrong order of rows with InnoDB + Joins + Order By + Null |
60941 | 2011-04-21 7:56 | 2011-06-27 23:00 | MySQL Server: Optimizer | No Feedback (4680 days) | S2 | 5.1.52-log, 5.1.56 | Any (Debian 5.0.8, Windows XP) | Any | Invalid use of join conditions |
60874 | 2011-04-14 18:30 | 2011-05-14 23:00 | MySQL Server: Optimizer | No Feedback (4723 days) | S2 | mysql-cluster-gpl-noinstall-7.1.10-win32 | Any | Any | inner join bug |
60317 | 2011-03-03 16:20 | 2011-04-03 23:00 | MySQL Server: Optimizer | No Feedback (4764 days) | S3 | 5.1.30-community-log | Linux (centos) | Any | equivalent queries give different results |
59950 | 2011-02-04 16:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | No Feedback (4394 days) | S5 | 5.5.8 | Linux (centos 5.5 64bit) | Any | Identical query taking longer on 5.5.8 compared to 5.1 |
53553 | 2010-05-11 7:14 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5060 days) | S2 | 5.1.46 | Windows (Windows 7 x64) | Any | "Copying to tmp table" spend a lot time |
70012 | 2013-08-13 11:12 | 2014-01-10 1:00 | MySQL Server: Optimizer | No Feedback (3752 days) | S2 | 5.6.12 | Solaris (SunOS db-stage02.fmk.netic.dk 5.10 Generic_147441-27 i86pc i386 i86pc) | Any | Different Optimizer (slower) for Query in 5.6 compared to 5.1 |
51677 | 2010-03-03 8:32 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5024 days) | S5 | 5.1.34sp1 | Linux (rh5.3) | Any | optimizer choose wrong index when using uncorrect character for client |
51097 | 2010-02-11 14:05 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5152 days) | S3 | 5.0.51b | Windows (WinXP sys32) | Any | SELECT INDEX USE |
50707 | 2010-01-29 1:18 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5163 days) | S5 | Ver 5.1.26-rc-5.1.26rc-log for debian-li | Linux (Debian) | Any | InnoDB optimizer does a full table scan for query with IN (...) ORDER BY pk |
49360 | 2009-12-02 17:53 | 2013-02-03 19:22 | MySQL Server: Optimizer | No Feedback (4764 days) | S3 | 5.0.66 , 5.0.84 , 5.0.84 , 5.1.41, 5.1.43 | Any | Any | In some circumstances, GROUP BY WITH ROLLUP is faster then GROUP BY |
49092 | 2009-11-25 9:37 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5228 days) | S5 | 5.0.26 | Linux | Any | EXISTS clause optimization |
48068 | 2009-10-15 6:49 | 2011-12-17 16:51 | MySQL Server: Optimizer | No Feedback (4506 days) | S5 | MYSQL-5.0.45 | Linux (RHEL 5.2) | Any | "Copying to tmp table" taking too much time to execute |
47906 | 2009-10-08 4:56 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5275 days) | S1 | 5.0.85, 5.1.37, 5.1.39, 6.0.9 | Any | Any | Having an extra field in a table changes optimizer index choice for other column |
45886 | 2009-07-01 18:38 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5314 days) | S3 | 5.0.45-log, 5.0.83 | Any | Any | Index |
45228 | 2009-05-31 22:56 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5290 days) | S3 | 5.4 | Any | Any | Queries with WHERE <col_1> AND <condition> GROUP BY <col_2> produce bad results |
45226 | 2009-05-31 22:42 | 2011-02-16 23:44 | MySQL Server: Optimizer | No Feedback (5290 days) | S3 | 5.4 | Any | Any | extra rows returned for queries using IN,GROUP BY and HAVING clauses |
9523 | 2005-03-31 13:15 | 2011-02-16 23:43 | MySQL Server: Optimizer | No Feedback (5208 days) | S2 | 5.0.9-beta, 4.1.10a | Windows (Windows XP) | Any | abuse of index in simple query |
80677 | 2016-03-09 19:37 | 2018-03-24 1:00 | MySQL Server: Optimizer | No Feedback (2218 days) | S5 | 5.6.25, 5.7.18 | Any | Any | Optimizer chooses wrong index for LEFT JOIN ORDER BY query |
112354 | 2023-09-15 7:52 | 2023-10-20 1:00 | MySQL Server: Optimizer | No Feedback (182 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
101805 | 2020-11-30 16:16 | 2021-01-02 1:00 | MySQL Server: Optimizer | No Feedback (1203 days) | S2 | 5.7.32 | Any | Any | Using index for group-by doesn't work with InnoDB compressed table |
100764 | 2020-09-08 8:50 | 2020-10-16 1:00 | MySQL Server: Optimizer | No Feedback (1281 days) | S1 | 8.0 | Any | Any | Rename Table causes other SQL execution plans to change. |
92724 | 2018-10-09 21:33 | 2018-11-12 13:21 | MySQL Server: Optimizer | No Feedback (1986 days) | S3 | 5.7.21, 5.7.23 | CentOS | Any | Optimizer is using wrong index that isn't in possible index list |
86205 | 2017-05-06 23:13 | 2017-06-10 1:00 | MySQL Server: Optimizer | No Feedback (2505 days) | S3 | 5.6/5.7 | Windows | Any | optimizer index using select where column in select |
Showing 1-30 of 99 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |