ID,Entered,Modified,Type,Status,Severity,Version,OS,Summary
27452,2007-03-26 17:35:17,2008-11-17 19:38:02,Server: Optimizer,Verified,S3,"5.0.40-BK, 5.0.24a-debian-log, 5.1.31-bzr, 6.0.7-alpha, 6.0.9-bzr","Linux","Correlated subquery produces inefficient optimizer plan for INFORMATION_SCHEMA"
35165,2008-03-08 17:48:33,2008-03-12 21:48:13,Server: CSV,Verified,S5,"5.1","Any","Logging to table is slow for large queries"
38397,2008-07-27 20:13:19,2008-07-28 03:18:51,Server: Optimizer,Verified,S3,"5.1.26, 5.0.62","Any","select distinct + order by desc is executed inefficiently"
40367,2008-10-28 08:55:00,2009-01-22 17:14:21,Server: I_S,Verified,S3,"5.1.28, 5.1.29, 5.0, 5.1 bzr","Any","SHOW on a broad view is taking too long"
42705,2009-02-09 16:37:22,2009-03-23 16:12:22,Server: General,Verified,S3,"5.1.30","Any","Reduce malloc/free during query lifecycle."
44201,2009-04-10 03:04:52,2010-06-15 19:10:38,Server: Optimizer,Verified,S3,"5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99","Any","Performance problem with View"
45424,2009-06-10 06:58:00,2009-06-10 07:59:08,Server: Optimizer,Verified,S2,"5.0.51a, 5.0.77 and 5.1.34, 5.1, 6.0 bzr","Linux","UPDATE statement cause full table scan ?"
46376,2009-07-24 17:05:25,2009-07-29 08:39:23,Server: Optimizer,Verified,S5,"5.0.85, 5.1.36, 5.1.38, 5.1.39","Windows (XP)","Optimizer choose wrong index even when where clause and order-by are covered"
46648,2009-08-11 11:41:04,2009-08-17 13:36:29,Server: Optimizer,Verified,S3,"5.1.32, 4.1, 5.0, 5.1, azalea bzr","Linux (2.6.28.7)","SQL_CALC_FOUND_ROWS kills performance with ORDER BY and LIMIT"
48359,2009-10-27 19:24:18,2010-06-24 08:01:30,Server: Cluster,In progress,S3,"mysql-5.1-telco-7.1","Linux (RHEL 4)","ALTER TABLE xx COMMENT - locks large tables"
47884,2009-10-07 03:24:19,2010-01-29 16:53:06,Server: Optimizer,Verified,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)","MySQL 5.1.39 failed to use index"
21978,2006-09-01 22:13:27,2007-12-05 18:55:30,Server: Options,Verified,S3,"4.0.18, 5.0, 6.0.10, 5.5","Windows (Windows 2000)","'flush_time' value set for 1800 sec. on Non Win9x/Me installs by default"
50367,2010-01-15 14:12:01,2010-03-18 10:15:29,Server: General,Verified,S5,"5.1.42, 5.1 bzr","Any (MS Windows 32 bits, Mac)","REPLACE has quadradic computational complexity on windows server (but not linux)"
55979,2010-08-13 22:05:55,2010-08-16 08:44:10,Server: Optimizer,Verified,S5,"5.1.39","Linux","Key not used if IN() list contains mix of strings and integers"
56924,2010-09-22 11:26:35,2011-12-02 08:00:30,MySQL Workbench: SQL Editor,Verified,S2,"5.2.28","Linux (Ubuntu 10.04)","Memory leak? Possibly not a bug."
56965,2010-09-23 09:22:41,2010-09-29 09:33:52,Client: mysqldump,Verified,S3,"5.1.44","Linux (2.6.18-164.6.1.el5 #1 SMP, CentOS 5.5)","mysqldump poor performance with large number of tables"
58008,2010-11-05 09:38:09,2010-11-05 09:41:30,Server: Optimizer,Verified,S3,"5.1, 5.0","Any","wrong datatype (blob) in the resultset if the string is larger than 512 bytes"
58928,2010-12-14 20:58:53,2010-12-14 21:43:59,Server: Optimizer,Verified,S3,"5.1-bugteam","Any","""not exists"" optimization not applied if relevant table is not single inner one"
59727,2011-01-25 21:36:11,2026-06-10 19:57:56,Server: InnoDB,Verified,S5,"5.1 plugin, 5.5, 5.6","Any","LRU search can be inefficient with compression"
59557,2011-01-17 15:26:08,2011-01-17 16:03:26,Server: Optimizer,Verified,S2,"5.1, 5.5","Any","MySQL uses order of fields in GROUP BY when ORDER BY NULL is specified"
60087,2011-02-10 13:14:51,2011-02-10 13:25:32,Server: InnoDB,Verified,S3,"5.5","Any","Patch: Minimize InnoDB I/O load by adding a prefetch stage"
60345,2011-03-04 17:11:45,2013-01-15 15:18:26,Server,Verified,S5,"5.1.55 6.0.11","Any","trim trailing spaces processes data only byte wise (the continue of  bug14637)"
60348,2011-03-04 20:14:41,2013-01-15 15:24:19,Server,Verified,S5,"5.1.55","Any","trim trailing spaces processes data only byte wise (continue of bug14637 (2))"
60349,2011-03-04 21:20:06,2013-01-15 15:25:20,Server,Verified,S5,"5.1.55","Any","trim beginning spaces processes data only byte wise (continue of bug14637 (3))"
60351,2011-03-04 22:15:10,2013-01-15 15:27:05,Server,Verified,S5,"5.1.55","Any","trim same character processes data only byte wise (continue of bug14637 (4))"
66563,2012-08-28 05:37:03,2012-08-28 06:55:30,Server: InnoDB Plugin,Verified,S5,"5.1,5.6","Any","reduce the number of redundant calls to btr_cur_optimistic_insert()"
69118,2013-05-02 02:28:15,2013-05-02 14:00:54,Client,Verified,S5,"5.6, 5.7","Any","Wasted work in method get_table_structure()"
68572,2013-03-05 10:57:18,2013-03-06 19:46:21,Server: Federated,Verified,S3,"5.5.25a, 5.5.31","Any","FEDERATED using SHOW TABLE STATUS causes performance problems for InnoDB tables"
64340,2012-02-15 14:07:03,2013-06-14 15:35:16,Server: InnoDB Plugin,Verified,S5,"5.1.52, 5.1.61","Any","race on no_flush event during buf_flush_free_margin"
75504,2015-01-14 12:52:54,2015-01-22 14:51:02,Server: InnoDB,Verified,S5,"","Any","btr_search_guess_on_hash makes found block young twice?"
71140,2013-12-13 09:16:24,2015-07-31 08:59:17,Server: Optimizer,Verified,S2,"5.1, 5.5, 5.6.15, 5.7.7","Any","Optimizer does NOT use range checks in typical self-join for InnoDB tables"
78355,2015-09-07 15:53:52,2015-09-15 08:48:57,Server: Optimizer,Verified,S5,"5.5.41, 5.5.46, 5.5.47","Ubuntu (x64)","nested select query not work on mysql 5.5 but it works well in mysql 5.6"
62018,2011-07-28 15:15:34,2013-01-16 17:43:27,Server: InnoDB,Verified,S5,"5.6.3","Any","innodb adaptive hash index mutex contention"
75962,2015-02-19 03:14:32,2015-03-03 20:46:37,Server: InnoDB,Verified,S3,"5.6.24, 5.7.6","Any","Innodb calls fsync when freeing a LRU page to fulfill page request"
30342,2007-08-09 18:52:04,2015-10-07 14:54:53,Server: Optimizer,Verified,S5,"5.0.37, 5.6.17","Any","Equality propagation can make optimization much slower"
81630,2016-05-28 05:46:18,2016-08-31 06:30:31,Server: Replication,Verified,S5,"5.7.12","Any","MySQL 5.7 is 37-45% slower then 5.6 when using binlogging due to defaults change"
60261,2011-02-26 00:59:07,2016-11-12 22:48:13,Server: Cluster,Verified,S5,"mysql-cluster-gpl-7.1.9a","Any","Are transaction hints needed in these situation?"
67913,2012-12-16 02:31:07,2013-01-21 09:51:47,Connector/ODBC,Verified,S5,"5.2.2, 5.1.11","Windows (Windows 7 and 8 64-bit)","ODBC connector performance problem"
75981,2015-02-20 13:56:16,2015-04-09 04:35:24,Server: InnoDB,Verified,S5,"5.7.6","Any","MySQL 5.7.5 30% slower than 5.6.23 for 1 thread write"
89926,2018-03-06 10:20:59,2018-03-12 12:21:07,C API,Verified,S5,"5.7","Linux","Performance degradation in libmysqlclient 20"
74408,2014-10-15 19:52:26,2018-07-04 15:15:11,Server: InnoDB,Verified,S5,"5.6, 5.7, 8.0","Any","srv_conc_enter_innodb() is not optimal"
91585,2018-07-10 01:16:28,2018-07-10 09:39:26,Server: SP,Verified,S5,"5.7, 8.0, 8.0.11, 5.7.23","Any","“dead” code inside the stored proc or function can significantly slow it down"
95080,2019-04-23 07:24:16,2019-04-30 08:31:25,Router,Verified,S5,"8.0.15, 8.0.16","Oracle Linux (Oracle Linux Server 7.5, Linux 4.1.12-124.18.6.el7uek.x86_64 )","MySQL Router consuming mor CPU resources than it should"
83151,2016-09-26 14:27:07,2019-01-23 14:13:48,Server: Connection Handling,Verified,S2,"5.6.33","CentOS","high number of SHOW WARNINGS can stall server if compressed protocol in use"
98771,2020-02-28 06:29:24,2020-02-28 11:16:49,Server: Optimizer,Verified,S2,"5.7, 5.7.29","Any","Performance impact while selecting data from a JSON type column"
99432,2020-05-04 08:09:37,2020-05-04 12:46:04,Server: InnoDB,Verified,S5,"8.0.20","Any","Improving memory barrier during rseg allocation"
100432,2020-08-05 07:55:26,2020-08-05 13:15:42,Server: Performance Schema,Verified,S5,"8.0.21","Any","Optimal memory-barrier for performance-schema counter"
100119,2020-07-06 07:07:22,2020-08-14 13:10:35,Server: InnoDB,Verified,S5,"8.0.20","Any","Switch to use relaxed memory barrier for redo-log counters"
100091,2020-07-02 12:23:49,2020-07-03 08:13:26,Connector/Python,Verified,S5,"8.0.18, 8.0.20","Any","mysqlx interface is a lot slower than the connector.python interface"
104615,2021-08-13 10:26:19,2021-08-13 11:32:24,Server: Logging,Verified,S5,"8.0","Any (rhel7.4)","trx commit slow if there are too many binlog files to purge while rotating"
105982,2021-12-27 08:11:45,2022-01-03 08:02:07,Server: Storage Engines,Verified,S5,"all, 5.7, 8.0","Linux","hard-coded libaio API parameter may not helpful to performance"
110779,2023-04-24 11:32:33,2023-05-12 05:26:04,Server: Optimizer,Verified,S5,"8.0.33, 5.7.42","Any","IN clause cause pick bad performan index"
112902,2023-10-31 14:39:48,2024-02-26 09:39:10,Server: Optimizer,Verified,S5,"8.0.31, 8.0.35","Linux (n.a.)","Optimizer in MySQL 8 is significantly slower on dependent subqueries than 5.7"
115122,2024-05-25 11:17:37,2024-06-16 09:10:00,Server: Optimizer,Verified,S5,"8.4 (Latest), 8.0.37","Ubuntu (22.04 LTS)","Unneeded full table scan, although there is an index and condition"
115107,2024-05-23 18:54:39,2024-10-17 10:01:24,Server: InnoDB,Patch approved,S5,"5.7, 8.0","Any","Optimization in row_purge_poss_sec Function for Undo Purge Process"
81376,2016-05-11 06:48:48,2025-05-14 12:56:00,Server: InnoDB,Verified,S5,"5.7","Any","Single page flushing should be removed"
120574,2026-05-29 14:05:16,2026-06-10 19:57:56,Server: Optimizer,Open,S2,"8.0.41","Any","Range optimizer exceeds memory limit and chooses bad range plan for large IN lists"
120575,2026-05-30 06:57:19,2026-06-10 19:57:56,Server: Optimizer,Open,S2,"8.0.41+","Any","Range optimizer chooses bad range plan for large IN lists and execution is very slow and memory usage spikes."