| Showing 1-30 of 59 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 19195 | 2006-04-19 12:09 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5536 days) | S3 | 5.0.27-BK, 5.0.21-BK, 5.0.19 | Linux (Linux) | Any | Optimizer does not use proper index for join |
| 25571 | 2007-01-12 7:27 | 2013-03-03 20:45 | MySQL Server: Federated storage engine | Verified | S3 | 5.0.34-BK, 5.0.27 | Linux (Linux) | Any | EXPLAIN returns incorrect estimation of rows for federated table |
| 25572 | 2007-01-12 10:04 | 2013-03-03 20:45 | MySQL Server: Federated storage engine | Verified | S2 | 5.0.34-BK, 5.0.27 | Linux (Linux) | Any | SHOW INDEX does not report cardinality (always NULL) for FEDERATED table |
| 28404 | 2007-05-13 18:33 | 2018-11-11 14:44 | MySQL Server: Optimizer | Verified (2202 days) | S2 | 4.0.31, 4.1.25, 4.1.26, 5.0.42-BK, 5.0.46, 5.1.33 | Linux | Any | Optimizer does not consider index that can be used for ORDER BY |
| 28554 | 2007-05-21 9:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5662 days) | S3 | 4.1.22, 5.0.42-BK | Any | Any | Optimizer wrongly prefers index for (col = value) over (PK <= value) |
| 59187 | 2010-12-27 15:31 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5078 days) | S2 | 5.1.55, 5.6.2-m5 | Any | Any | Wrong result with NULL NOT IN subquery |
| 61551 | 2011-06-17 12:26 | 2011-06-18 8:34 | MySQL Server: Optimizer | Verified (4906 days) | S3 | 5.1.56 | Any | Any | Loose index scan is not used for select COUNT(distinct a) |
| 64036 | 2012-01-15 15:51 | 2012-01-15 19:07 | MySQL Server: Optimizer | Verified (4694 days) | S3 | Any | Any | Use non-materializing loose-scan-merge for certain subqueries in FROM with LIMIT | |
| 70164 | 2013-08-27 13:57 | 2013-08-28 11:19 | MySQL Server: InnoDB storage engine | Verified (4103 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Misleading comment for the recv_parse_or_apply_log_rec_body() function |
| 70555 | 2013-10-08 17:29 | 2013-10-09 8:03 | MySQL Server: Optimizer | Verified (4061 days) | S3 | 5.6.14 | Any | Any | EXPLAIN for INSERT ... SELECT waits for table lock |
| 70629 | 2013-10-16 8:27 | 2017-05-14 20:45 | MySQL Server: InnoDB storage engine | Verified (4010 days) | S2 | 5.6.14 | Any | Any | InnoDB updated rec_per_key[] statis not published to the optimizer enough often |
| 70630 | 2013-10-16 8:46 | 2013-10-17 23:04 | MySQL Server: InnoDB storage engine | Verified (4053 days) | S3 | 5.6.14 | Any | Any | Why one can access persistent statistics data while they are changing? |
| 70684 | 2013-10-22 8:13 | 2013-10-22 11:35 | MySQL Server: Optimizer | Verified (4048 days) | S3 | 5.5.33, 5.6.14 | Any | Any | HAVING referring to subquery results in WARNING 1292 |
| 71091 | 2013-12-05 12:52 | 2013-12-06 11:15 | MySQL Server: CSV | Verified (4003 days) | S3 | 5.5.33, any, 5.6.15, 5.5.35 | Any | Any | CSV engine does not properly process "", in quotes |
| 71140 | 2013-12-13 9:16 | 2015-07-31 8:59 | MySQL Server: Optimizer | Verified (3401 days) | S2 | 5.1, 5.5, 5.6.15, 5.7.7 | Any | Any | Optimizer does NOT use range checks in typical self-join for InnoDB tables |
| 71146 | 2013-12-14 11:34 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (3993 days) | S3 | any | Any | Any | Manual does not explain when REPAIR or OPTIMIZE TABLE uses repair by sorting |
| 71189 | 2013-12-20 14:56 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (3989 days) | S3 | 5.5, any | Any | Any | Manual does not provide enough details on how loose index scan really works |
| 71191 | 2013-12-20 15:30 | 2013-12-20 20:20 | MySQL Server: Optimizer | Verified (3989 days) | S3 | 5.5.33 | Any | Any | Loose index scan is used even though full table scan/tight index scan is faster |
| 71199 | 2013-12-21 18:16 | 2014-01-28 17:45 | MySQL Server: Optimizer | Verified (3986 days) | S3 | 5.6.14, 5.6.15, 5.5.35 | Any | Any | Optimizer's estimated number of rows is 2 times wrong for (loose?) index scans |
| 71204 | 2013-12-22 15:42 | 2014-01-06 13:43 | MySQL Server: Performance Schema | Verified (3985 days) | S3 | 5.6.14, 5.6.16 | Any | Any | Timing for stages in P_S is different from what SHOW PROFILE reports |
| 71232 | 2013-12-26 11:34 | 2014-07-04 9:51 | MySQL Server: InnoDB storage engine | Verified (3793 days) | S3 | 5.6.15 | Any | Any | Wrong behaviour for auto_increment unsigned bigint column approaching max value |
| 71279 | 2014-01-02 17:29 | 2014-01-08 9:33 | MySQL Server: Security: Privileges | Verified (3976 days) | S3 | 5.6 | Any | Any | Misleading error message for ANALYZE against PERFORMANCE_SCHEMA tables |
| 71280 | 2014-01-02 18:21 | 2014-01-03 8:37 | MySQL Server: Information schema | Verified (3975 days) | S3 | 5.6.14, 5.6.15, 5.6.16 | Any | Any | Misleading error message for ANALYZE against INFORMATION_SCHEMA tables |
| 71293 | 2014-01-04 18:35 | 2021-08-08 20:45 | MySQL Server: Performance Schema | Verified (3972 days) | S3 | 5.6 | Any | Any | Manual page for P_S.FILE_INSTANCES table does not explain EVENT_NAME values |
| 71294 | 2014-01-04 19:24 | 2014-01-24 16:26 | MySQL Server: General | Verified (3972 days) | S3 | 5.6 | Any | Any | Manual page for P_S.FILE_INSTANCES table does not explain '~' in FILE_NAME |
| 71312 | 2014-01-07 13:21 | 2014-01-08 12:27 | MySQL Server: Information schema | Verified (3970 days) | S3 | 5.6.15 | Any | Any | Weird warning for MERGE table while accessing I_S.REFERENTIAL_CONSTRAINTS |
| 71355 | 2014-01-12 17:22 | 2014-01-13 5:06 | MySQL Server: Information schema | Verified (3965 days) | S3 | 5.6 | Any | Any | Strange data type is used for name-related columns in some I_S.INNODB_* tables |
| 71477 | 2014-01-25 12:10 | 2014-01-27 15:11 | MySQL Server: Options | Verified (3951 days) | S3 | 5.6.15 | Any | Any | transaction_allow_batching is available in non-Cluster MySQL Server 5.6 |
| 71479 | 2014-01-25 15:32 | 2014-01-30 14:23 | MySQL Server: Options | Verified (3951 days) | S3 | 5.6 | Windows (Win64) | Any | sort_buffer_size is limited to 4GB-1 on 64-bit Windows |
| 71513 | 2014-01-29 16:08 | 2014-01-30 6:16 | MySQL Server: Errors | Verified (3948 days) | S3 | 5.6.15, 5.5.35 | Any | Any | mysqld --help --verbose doesn't produce error for wrong innodb_flush_method |
| Showing 1-30 of 59 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
