| Showing 1-30 of 1629 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 30067 | 2007-07-26 12:42 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S5 | mysql-5.1-telco-6.2 | Linux (32) | Any | DISCOVER TABLE Event: Takes too long after Incorrect info error |
| 75807 | 2015-02-06 10:00 | 2015-02-20 9:54 | MySQL Server: DML | Verified (3981 days) | S5 | 5.6.22 | Linux | Any | Slow Query in MySQL 5.6 |
| 99924 | 2020-06-18 3:27 | 2020-06-23 12:36 | MySQL Server: InnoDB storage engine | Verified (2029 days) | S5 | 8.0 | Any | Any | The record per key value from InnoDB is not suitable when n_diff is zero |
| 74083 | 2014-09-25 18:11 | 2014-10-09 12:58 | MySQL Server: Optimizer | Verified (4113 days) | S5 | 5.6.20, 5.6.22 | Linux (CentOS 6.5) | Any | ENUM index scan is slower than INT index scan |
| 80390 | 2016-02-16 10:14 | 2022-10-04 15:10 | MySQL Server: Optimizer | Verified (3618 days) | S5 | 5.6.30 | Any | Any | Clustered primary key included in index merge may cause higher execution times |
| 34310 | 2008-02-05 14:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4408 days) | S5 | 5.0.51a-log, 5.0.54, 5.6.14 | Linux | Any | Optimizer is inefficient by using ORDER BY function() and LIMIT |
| 86393 | 2017-05-21 4:57 | 2017-05-22 17:09 | MySQL Workbench | Verified (3157 days) | S5 | 6.3.9 | Windows (Microsoft Windows 10 Pro) | Any | System logs feature in workbench displays information in incorrect columns. |
| 90270 | 2018-03-31 13:08 | 2018-04-04 11:42 | MySQL Workbench: SQL Editor | Verified (2840 days) | S5 | 6.3.10 | Linux (LinuxMint 18 x86_64) | Any | HTML UTF8 encoded values in JSON field break Value Editor association as JSON |
| 90604 | 2018-04-24 13:50 | 2018-04-25 4:41 | MySQL Server: InnoDB storage engine | Verified (2819 days) | S5 | 5.7 | CentOS | Any | ut_rnd_ulint_counter () : Default delay for spin wait gives better performance |
| 49276 | 2009-12-01 17:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5886 days) | S5 | 5.0.85-community-log, 5.0.89, 5.1.42 | Linux | Any | Optimization for IN (on InnoDB tables) depends on number of set elements |
| 68697 | 2013-03-17 13:56 | 2013-03-18 19:43 | MySQL Server: Storage Engine API | Verified (4684 days) | S5 | 5.5.31, 5.6.11 | Any | Any | loose rec_per_key precision according to whole integer type |
| 77418 | 2015-06-19 19:56 | 2017-03-18 3:08 | MySQL Workbench: Modeling | Verified (3860 days) | S5 | 6.3.4 | MacOS (OS X 10.10.x Yosemite) | Any | EER: Differences in data-type lengths between Forward Engineer and Sync Model |
| 97228 | 2019-10-15 10:40 | 2019-10-25 12:07 | MySQL Server: InnoDB storage engine | Verified (2271 days) | S5 | 8.0 | Any | ARM | rwlock: refine lock->lock_word with C11 atomics |
| 97230 | 2019-10-15 10:44 | 2019-10-15 14:06 | MySQL Server: InnoDB storage engine | Verified (2281 days) | S5 | 8.0 | Any | ARM | rwlock: refine lock->waiters with C++11 atomics |
| 78407 | 2015-09-11 12:45 | 2022-04-29 5:41 | MySQL Server: Optimizer | Verified (1354 days) | S5 | 7.4.6/5.6.24, 5.7, 8.0 | Linux | Any | wrong index being used in subqueries? |
| 81803 | 2016-06-10 12:35 | 2016-06-15 16:58 | MySQL Server: Optimizer | Verified (3498 days) | S5 | >=5.1 | Any | Any | Mysql 5.1 and later Update performance regression |
| 111720 | 2023-07-11 13:43 | 2023-07-11 14:22 | MySQL Server: InnoDB storage engine | Verified (916 days) | S5 | 8.0.33 | Any | Any | recv_n_pool_free_frames are not maintained correctly |
| 112346 | 2023-09-14 8:21 | 2023-10-11 7:24 | MySQL Server: JSON | Verified (824 days) | S5 | 8.0.34 | Any | Any | MEMBER_OF with multi-valued index on JSON not used in 99% of situations. |
| 115328 | 2024-06-14 2:13 | 2025-08-11 12:05 | MySQL Server: InnoDB storage engine | Analyzing (573 days) | S5 | 8.4.0 | Red Hat (Rocky Linux 8.8) | x86 | Poor write performance due to new default value of innodb_doublewrite_pages |
| 93188 | 2018-11-14 11:16 | 2020-07-15 12:53 | MySQL Server: Optimizer | Verified (2614 days) | S5 | 5.7 | Any | Any | Optimiser chose incorrect join order inside of derived table |
| 118181 | 2025-05-13 12:36 | 2025-07-03 9:33 | MySQL Server: DML | Verified (195 days) | S5 | 8.0.42 | Linux | x86 | Performance regression on query statements after commit 0fa789a |
| 8113 | 2005-01-24 15:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5991 days) | S5 | 5.0, 5.1, azalea bzr | Any | Any | Select with between optimization |
| 31901 | 2007-10-29 2:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6543 days) | S5 | 5.0.45 | Any | Any | read_rnd_buffer_size doesn't seem to be used as written in Reference Manual |
| 43427 | 2009-03-05 17:17 | 2025-12-07 20:45 | MySQL Server: General | Verified (6154 days) | S5 | 5.0 | Any | Any | Don't limit table_cache_size as a function of max_connections |
| 65177 | 2012-05-02 9:43 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (4998 days) | S5 | 5.1,5.5 | Any | Any | perromance issue of "order by rand()" |
| 68979 | 2013-04-17 3:47 | 2018-07-11 15:11 | MySQL Server: Optimizer | Verified (4618 days) | S5 | 5.6.10 | Linux | Any | performance regression of MySQL 5.6.10? |
| 72882 | 2014-06-05 2:24 | 2014-07-25 19:51 | MySQL Server: Charsets | Verified (4189 days) | S5 | 5.5 5.6 | Linux | Any | Metadata character set causes unnecessary cost for cpu-bound scene |
| 88777 | 2017-12-06 9:36 | 2017-12-11 11:56 | MySQL Workbench | Verified (2954 days) | S5 | 6.3.10 | Windows (Microsoft Windows 10 Home) | Any | set default value |
| 101283 | 2020-10-23 10:13 | 2020-10-23 12:08 | MySQL Server: InnoDB storage engine | Verified (1907 days) | S5 | 8.0 | Any | Any | Is single_scan_itr.start() reasonable? |
| 101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1880 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
| Showing 1-30 of 1629 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
