Showing 1-30 of 53 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
83151 | 2016-09-26 14:27 | 2021-09-14 10:08 | MySQL Server: Connection Handling | Verified (1597 days) | S2 | 5.6.33 | CentOS | Any | high number of SHOW WARNINGS can stall server if compressed protocol in use |
98771 | 2020-02-28 6:29 | 2020-03-02 18:39 | MySQL Server: Optimizer | Verified (1196 days) | S2 | 5.7, 5.7.29 | Any | Any | Performance impact while selecting data from a JSON type column |
71140 | 2013-12-13 9:16 | 2015-07-31 8:59 | MySQL Server: Optimizer | Verified (2869 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 |
45424 | 2009-06-10 6:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5111 days) | S2 | 5.0.51a, 5.0.77 and 5.1.34, 5.1, 6.0 bzr | Linux | Any | UPDATE statement cause full table scan ? |
59557 | 2011-01-17 15:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4525 days) | S2 | 5.1, 5.5 | Any | Any | MySQL uses order of fields in GROUP BY when ORDER BY NULL is specified |
47884 | 2009-10-07 3:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4878 days) | S2 | 5.1.39, 5.1.44, 5.5.99 | Linux (Linux web2 2.6.18-92.1.18.el5.028stab060.8 #1 SMP Mon Feb 9 21:44:50 MSK 2009 x86_64) | Any | MySQL 5.1.39 failed to use index |
56924 | 2010-09-22 11:26 | 2018-06-24 20:45 | MySQL Workbench: SQL Editor | Verified (4206 days) | S2 | 5.2.28 | Linux (Ubuntu 10.04) | Any | Memory leak? Possibly not a bug. |
68572 | 2013-03-05 10:57 | 2014-02-19 16:19 | MySQL Server: Federated storage engine | Verified (3746 days) | S3 | 5.5.25a, 5.5.31 | Any | Any | FEDERATED using SHOW TABLE STATUS causes performance problems for InnoDB tables |
27452 | 2007-03-26 17:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5316 days) | S3 | 5.0.40-BK, 5.0.24a-debian-log, 5.1.31-bzr, 6.0.7-alpha, 6.0.9-bzr | Linux | Any | Correlated subquery produces inefficient optimizer plan for INFORMATION_SCHEMA |
60087 | 2011-02-10 13:14 | 2016-12-04 20:45 | MySQL Server: InnoDB storage engine | Verified (4501 days) | S3 | 5.5 | Any | Any | Patch: Minimize InnoDB I/O load by adding a prefetch stage |
58928 | 2010-12-14 20:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4559 days) | S3 | 5.1-bugteam | Any | Any | "not exists" optimization not applied if relevant table is not single inner one |
58008 | 2010-11-05 9:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4598 days) | S3 | 5.1, 5.0 | Any | Any | wrong datatype (blob) in the resultset if the string is larger than 512 bytes |
56965 | 2010-09-23 9:22 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4635 days) | S3 | 5.1.44 | Linux (2.6.18-164.6.1.el5 #1 SMP, CentOS 5.5) | Any | mysqldump poor performance with large number of tables |
75962 | 2015-02-19 3:14 | 2015-03-03 20:46 | MySQL Server: InnoDB storage engine | Verified (3019 days) | S3 | 5.6.24, 5.7.6 | Any | Any | Innodb calls fsync when freeing a LRU page to fulfill page request |
21978 | 2006-09-01 22:13 | 2011-02-16 23:43 | MySQL Server: Options | Verified (5664 days) | S3 | 4.0.18, 5.0, 6.0.10, 5.5 | Windows (Windows 2000) | Any | 'flush_time' value set for 1800 sec. on Non Win9x/Me installs by default |
48359 | 2009-10-27 19:24 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | In progress (4732 days) | S3 | mysql-5.1-telco-7.1 | Linux (RHEL 4) | Any | ALTER TABLE xx COMMENT - locks large tables |
46648 | 2009-08-11 11:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5043 days) | S3 | 5.1.32, 4.1, 5.0, 5.1, azalea bzr | Linux (2.6.28.7) | Any | SQL_CALC_FOUND_ROWS kills performance with ORDER BY and LIMIT |
44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4741 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
42705 | 2009-02-09 16:37 | 2011-02-16 23:43 | MySQL Server: General | Verified (5190 days) | S3 | 5.1.30 | Any | Any | Reduce malloc/free during query lifecycle. |
40367 | 2008-10-28 8:55 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified (5250 days) | S3 | 5.1.28, 5.1.29, 5.0, 5.1 bzr | Any | Any | SHOW on a broad view is taking too long |
38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5428 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
75981 | 2015-02-20 13:56 | 2017-11-05 7:12 | MySQL Server: InnoDB storage engine | Verified (2982 days) | S5 | 5.7.6 | Any | Any | MySQL 5.7.5 30% slower than 5.6.23 for 1 thread write |
89926 | 2018-03-06 10:20 | 2018-03-12 12:21 | MySQL Server: C API (client library) | Verified (1914 days) | S5 | 5.7 | Linux | x86 | Performance degradation in libmysqlclient 20 |
67913 | 2012-12-16 2:31 | 2017-07-18 5:39 | Connector / ODBC | Verified (3790 days) | S5 | 5.2.2, 5.1.11 | Windows (Windows 7 and 8 64-bit) | Any | ODBC connector performance problem |
74408 | 2014-10-15 19:52 | 2018-07-04 15:16 | MySQL Server: InnoDB storage engine | Verified (1800 days) | S5 | 5.6, 5.7, 8.0 | Any | Any | srv_conc_enter_innodb() is not optimal |
91585 | 2018-07-10 1:16 | 2018-08-27 11:06 | MySQL Server: Stored Routines | Verified (1794 days) | S5 | 5.7, 8.0, 8.0.11, 5.7.23 | Any | Any | “dead” code inside the stored proc or function can significantly slow it down |
60261 | 2011-02-26 0:59 | 2016-11-12 22:57 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2399 days) | S5 | mysql-cluster-gpl-7.1.9a | Any | Any | Are transaction hints needed in these situation? |
100119 | 2020-07-06 7:07 | 2020-08-14 13:55 | MySQL Server: InnoDB storage engine | Verified (1028 days) | S5 | 8.0.20 | Any | ARM | Switch to use relaxed memory barrier for redo-log counters |
95080 | 2019-04-23 7:24 | 2019-04-30 14:09 | MySQL Router | Verified (1500 days) | S5 | 8.0.15, 8.0.16 | Oracle Linux (Oracle Linux Server 7.5, Linux 4.1.12-124.18.6.el7uek.x86_64 ) | x86 (Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz) | MySQL Router consuming mor CPU resources than it should |
99432 | 2020-05-04 8:09 | 2020-05-05 12:04 | MySQL Server: InnoDB storage engine | Verified (1130 days) | S5 | 8.0.20 | Any | ARM | Improving memory barrier during rseg allocation |
Showing 1-30 of 53 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |