| Showing all 23 (Edit, Save, CSV, Feed) |
| ID# | Date | Type | Status | Sev | Version | Target | OS | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|
| 26232 | 2007-02-09 18:28 | Server: Optimizer | Verified (1012 days) | S3 | 4.1.22, 5.0.34, 5.0.36-BK | Linux (Linux) | review of bug #20944 / proof of concept attached | Sergey Petrunya | |
| 27199 | 2007-03-16 6:03 | Server: Optimizer | Verified (403 days) | S2 | 5.0.22, 5.0.37, 4.1 BK, 5.1 BK | Linux (linux) | Performance problem when query contains a left join against a subquery | Ramil Kalimullin | |
| 27975 | 2007-04-20 13:20 | Server: Optimizer | Verified (403 days) | S3 | 5.0.38, 5.0.44, 4.1, 5.0, 5.1, 5.2 BK | Linux (RHEL 4) | optimizer error after discovering impossible where clause in a large view | Igor Babaev | |
| 29443 | 2007-06-29 15:28 | Server: Optimizer | In progress (852 days) | S3 | 5.1.19 | Any | cost calculations are off | Sergey Petrunya | |
| 30342 | 2007-08-09 20:52 | Server: Optimizer | Analyzing (757 days) | S5 | 5.0.37 | Any | Equality propagation can make optimization much slower | Valeriy Kravchuk | |
| 31188 | 2007-09-25 18:52 | Server: Optimizer | Verified (739 days) | S5 | 5.0.37 | Any | Optimizer does not do index range scans using predicates in IN lists | ||
| 31648 | 2007-10-16 21:01 | Server: Optimizer | Verified (737 days) | S2 | 5.1.22, 5.0.50 | Any | full table scans being done when range should be used | Sergey Petrunya | |
| 33321 | 2007-12-18 7:34 | Server: Optimizer | Verified (237 days) | S3 | 5.0.52, 5.0-bzr, 5.1-bzr | Any | print_plan does not print appropriate values. | ||
| 35794 | 2008-04-03 14:06 | Server: Optimizer | Verified (525 days) | S3 | 5.0.45, 5.0, 5.1, 6.0 BK | Any | Very bad query optimization on DELETE with subquery | Sergey Petrunya | |
| 36474 | 2008-05-02 16:13 | Server: Falcon | Verified | S3 | 6.0.5 | 6.0-rc | Any | Falcon reports unrealistic row estimate on simple key lookup | Ann Harrison |
| 36562 | 2008-05-07 13:55 | Server: Falcon | Verified | S2 | 6.0.5 | 6.0-rc | Any | Falcon reports unrealistic row estimate with IN() | Ann Harrison |
| 36802 | 2008-05-19 17:42 | Server: Optimizer | Verified (420 days) | S3 | 5.0, 5.1, 6.0 BK | Any | MySQL only use covered index when selecting from a view (or subquery) with union | Gleb Shchepa | |
| 37577 | 2008-06-23 8:40 | Server: Falcon | Verified (516 days) | S5 | MySQL6.0 | 6.0-rc | Linux (SLES10SP1 (2.6.16.46-0.12-smp, x64)) | Query Q9 of DBT3 is running on Falcon slower than Innodb | Ann Harrison |
| 38745 | 2008-08-12 11:44 | Server: Optimizer | Verified (3 days) | S2 | 5.1 | Any | MySQL 5.1 optimizer uses filesort for ORDER BY when it should use index | Gleb Shchepa | |
| 42094 | 2009-01-14 0:01 | Server: Optimizer | Verified (245 days) | S3 | 5.1 | Any | Optimizer chooses a wrong index when group by, order by and limit is present | Gleb Shchepa | |
| 42948 | 2009-02-18 0:02 | Server: Optimizer | Verified (265 days) | S5 | 5.0.67-0ubuntu6, 6.0.11 | Linux (Ubuntu 8.10) | MySQL Optimizer does not properly use Indexes on Views with "Group By" | ||
| 43319 | 2009-03-03 3:24 | Server: Optimizer | Verified | S3 | 5.0, 5.1 | Any | Table/index scan when quoting large numbers in an 'IN' of a SELECT ... WHERE | Evgeny Potemkin | |
| 44201 | 2009-04-10 5:04 | Server: Optimizer | Verified (224 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr | Any | Performance problem with View | Gleb Shchepa | |
| 44549 | 2009-04-29 19:47 | Server: Optimizer | Verified | S3 | 5.0.80, 5.1.34 | Any | optimizer incorrectly chooses table scan and filesort over index | ||
| 45227 | 2009-06-01 0:48 | Server: Optimizer | Need Doc Info (10 days) | S3 | 5.4 | 5.4+ | Any | Queries with IN + condition, HAVING, ORDER BY 'pk' and LIMIT produce bad results | Evgeny Potemkin |
| 46376 | 2009-07-24 19:05 | Server: Optimizer | Verified (117 days) | S5 | 5.0.85, 5.1.36, 5.1.38, 5.1.39 | Microsoft Windows (XP) | Optimizer choose wrong index even when where clause and order-by are covered | ||
| 47454 | 2009-09-19 21:33 | Server: Optimizer | Verified (64 days) | S3 | 5.1.35 | Any | Not exists optimization method is not used for NULL columns in the right table | ||
| 48049 | 2009-10-14 18:46 | Server: Optimizer | Verified | S3 | 5.1.37 | Any | SELECT MIN(1) reports differently for MERGE tables in 5.0 and 5.1 |
| Showing all 23 (Edit, Save, CSV, Feed) |
