Showing 1-30 of 735 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
60185 | 2011-02-20 15:58 | 2011-03-03 8:35 | MySQL Server: Optimizer | Verified (4786 days) | S3 | 5.0.51, 5.5.11 | Linux | Any | index DEPENDENT SUBQUERY |
60494 | 2011-03-16 17:26 | 2011-03-19 9:43 | MySQL Server: Optimizer | Verified (4761 days) | S3 | 5.1.36-community, 5.1.57 | Any | Any | Order By produces wrong order |
26832 | 2007-03-04 18:17 | 2011-04-05 14:46 | MySQL Server: Optimizer | Verified (4742 days) | S5 | 5.5 | Any | Any | ENUM types not optimized |
60702 | 2011-03-30 23:25 | 2011-04-05 14:55 | MySQL Server: Optimizer | Verified (4747 days) | S5 | 5.1.57 | Any | Any | GROUP BY orders when used inside a UNION query, though it should not |
61551 | 2011-06-17 12:26 | 2011-06-18 8:34 | MySQL Server: Optimizer | Verified (4669 days) | S3 | 5.1.56 | Any | Any | Loose index scan is not used for select COUNT(distinct a) |
61936 | 2011-07-21 6:27 | 2011-07-31 15:28 | MySQL Server: Optimizer | Verified (4634 days) | S2 | 5.1.48, 5.5.13, 5.5.16 | Linux (x86_64) | Any | STRAIGHT_JOIN has no effect on query with subquery in FROM clause |
62307 | 2011-08-31 1:54 | 2011-09-01 21:29 | MySQL Server: Optimizer | Verified (4593 days) | S3 | 5.5.15 | Any | Any | Condition "TIME = '19:20'" does not use index in sjis |
63563 | 2011-12-03 14:09 | 2011-12-05 7:50 | MySQL Server: Optimizer | Verified (4499 days) | S2 | 5.5.17 | Any | Any | Binary operator now causes a full scan |
63868 | 2011-12-28 19:34 | 2011-12-30 15:41 | MySQL Server: Optimizer | Verified (4474 days) | S3 | 5.1.60, 5.5.20 | Linux (Centos 5 x64) | Any | Left outer join with user defined function on NULL column gives wrong results |
64036 | 2012-01-15 15:51 | 2012-01-15 19:07 | MySQL Server: Optimizer | Verified (4457 days) | S3 | Any | Any | Use non-materializing loose-scan-merge for certain subqueries in FROM with LIMIT | |
63905 | 2012-01-02 23:47 | 2012-01-16 18:35 | MySQL Server: Optimizer | Verified (4456 days) | S5 | 5.1.60 | Windows | Any | handler_read_next is suprisingly high and slows queries |
64016 | 2012-01-12 19:38 | 2012-01-19 11:48 | MySQL Server: Optimizer | Verified (4459 days) | S3 | 5.5.19 | Any | Any | Optimizer doesn't seem to take into account enum definition |
64002 | 2012-01-11 20:01 | 2012-01-19 11:52 | MySQL Server: Optimizer | Verified (4460 days) | S1 | 5.5.19 | Any (Debian, Windows XP) | Any | Aggregate queries with multiple columns and no GROUP BY produce bogus results |
64316 | 2012-02-14 12:04 | 2012-02-14 15:50 | MySQL Server: Optimizer | Verified (4427 days) | S2 | 5.1.49-3\5.5.21 | Linux (Debian) | Any | search with decimal value on INT field with index gives wrong result with LIMIT |
63375 | 2011-11-22 5:36 | 2012-02-24 10:52 | MySQL Server: Optimizer | Verified (4417 days) | S3 | 5.1,5.5 | Any | Any | Change the state from "Sending data" when running do_select |
64634 | 2012-03-13 13:11 | 2012-04-01 10:56 | MySQL Server: Optimizer | Verified (4380 days) | S3 | 5.6.4-m7 | Any | Any | No result when binding to same field with different trailing spaces |
65792 | 2012-07-03 2:19 | 2012-07-04 9:54 | MySQL Server: Optimizer | Verified (4287 days) | S5 | 5.1,5.5 | Any | Any | an unecessary Using temporary in distinct query |
66825 | 2012-09-14 22:38 | 2012-09-15 18:02 | MySQL Server: Optimizer | Verified (4213 days) | S3 | 5.5.27 | Any | Any | 5.5 ignores an index if BINARY is used |
66896 | 2012-09-20 20:24 | 2012-09-21 0:12 | MySQL Server: Optimizer | Verified (4207 days) | S2 | 5.5.24 | Linux (ubuntu 12.04) | Any | Distinct not distinguishing 0 from NULL when GROUP BY is used |
67638 | 2012-11-19 17:00 | 2012-11-26 17:24 | MySQL Server: Optimizer | Verified (4141 days) | S3 | 5.6.8 | Any | Any | Odd optimizer choice for UPDATE .. ORDER BY ... LIMIT query |
67815 | 2012-12-05 8:51 | 2012-12-06 6:15 | MySQL Server: Optimizer | Verified (4131 days) | S3 | 5.5.28, 5.6.7 | Linux | Any | MySQL consistently uses a low cardinality non-referenced column in a index scan |
68044 | 2013-01-06 22:02 | 2013-01-07 1:30 | MySQL Server: Optimizer | Verified (4099 days) | S3 | 5.5.30 | Any | Any | A minor bug in check_simple_equality() |
68072 | 2013-01-12 18:02 | 2013-01-13 15:08 | MySQL Server: Optimizer | Verified (4093 days) | S2 | 5.1, 5.5 | Any (Win64, CentOS Linux) | Any | MySQL 5.1 issue with timediff, group by on multiple columns, join, primary key |
67980 | 2012-12-27 14:54 | 2013-01-19 10:52 | MySQL Server: Optimizer | Verified (4087 days) | S3 | 5.5.28 | Any | Any | MySQL not utilising full index because of possible bad cardinality stats |
68852 | 2013-04-03 9:27 | 2013-04-03 9:41 | MySQL Server: Optimizer | Verified (4013 days) | S3 | 5.5.28 | Any | Any | Wrong behavior with aggregate functions, dates and between |
68899 | 2013-04-09 9:38 | 2013-04-10 11:00 | MySQL Server: Optimizer | Verified (4006 days) | S3 | 5.5.30, 5.6.10 | Linux | Any | High join_buffer_size prevents use of spatial index on joined tables |
68919 | 2013-04-10 14:25 | 2013-04-10 14:33 | MySQL Server: Optimizer | Verified (4006 days) | S5 | 5.6.10 | Any | Any | Performance regression when DS-MRR is used for query with small limit |
69219 | 2013-05-13 20:14 | 2013-05-13 20:32 | MySQL Server: Optimizer | Verified (3973 days) | S5 | 5.6.12 | Any | Any | CREATE TEMPORARY TABLE ... SELECT is slower on 5.6 than on 5.1 |
69285 | 2013-05-20 3:48 | 2013-06-10 10:28 | MySQL Server: Optimizer | Verified (3945 days) | S3 | 5.5+ | Any | Any | count upon not null field can not treated as count(*) |
66849 | 2012-09-17 18:49 | 2013-06-10 19:50 | MySQL Server: Optimizer | Verified (3945 days) | S1 | 5.5.16, 5.1.70, 5.5.32, 5.6.12 | Linux | Any | [REGRESSION] this query hangs the server (100% CPU for several minutes) |
Showing 1-30 of 735 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |