Showing all 967 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
58766 | 2010-12-06 22:48 | 2014-01-29 0:51 | MySQL Server | Closed (4027 days) | S2 | 5.5.8 | Any (Linux) | Any | Server binary was compiled without fast-mutexes |
61060 | 2011-05-04 16:43 | 2011-05-04 19:48 | MySQL Server | Duplicate (5028 days) | S3 | All | Any | Any | Mixed direction indexes |
65157 | 2012-04-30 17:39 | 2012-05-03 8:13 | MySQL Server | Duplicate (4663 days) | S5 | 5.1.53 | Any | Any | set read_only=1|0 kills performance |
81561 | 2016-05-24 7:22 | 2016-05-28 5:46 | MySQL Server | Closed (3177 days) | S1 | 5.7.12 | Any | Any | MySQL 5.7 is 11% to 37% slower then 5.6 when using 4 threads |
91589 | 2018-07-10 9:44 | 2018-07-10 9:51 | MySQL Server | Closed (2404 days) | S3 | 5.6.33-79.0 | CentOS (6.3) | x86 | Invalid primary key improves query performance |
104128 | 2021-06-28 7:00 | 2023-08-03 12:33 | MySQL Server | Duplicate (1320 days) | S3 | 8.0.25 | Ubuntu (18.04) | x86 (Core i7) | Poor performance for queries with tuple comparison |
112080 | 2023-08-16 6:30 | 2023-08-16 8:13 | MySQL Server | Closed (541 days) | S3 | 8.0 | Any | Any | No need call performance schema interface when open temporary table |
115159 | 2024-05-29 9:39 | 2024-06-03 9:40 | MySQL Server | Duplicate (252 days) | S5 | 8.0 and above | Any | Any | Fix for bug 113187 |
416 | 2003-05-11 12:47 | 2003-05-28 4:18 | MySQL Server | Duplicate (7926 days) | S2 | 4.1.0-alpha | Windows (Windows XP and NT) | Any | Server slow if client not on localhost |
476 | 2003-05-22 2:51 | 2003-07-01 5:11 | MySQL Server | Closed (7892 days) | S3 | 3.23.56 | Linux (linux) | Any | "myisamchk -r" results in loss of index "repair table" restores index |
3341 | 2004-03-30 21:47 | 2004-05-10 10:46 | MySQL Server | Closed (7578 days) | S3 | 3.23.58; 4.0.18 | FreeBSD (Free BSD, Windows) | Any | Not Optimized Min() |
3396 | 2004-04-05 16:57 | 2011-03-29 18:22 | MySQL Server | Closed (5064 days) | S2 | 4.1.1 | Linux (LINUX) | Any | A SUB-QUERY IN MYSQL 4.1.1.max.log MAKE SERVER DOWN :_( |
3799 | 2004-05-17 15:23 | 2008-09-14 2:34 | MySQL Server | Closed (5990 days) | S3 | 4.0.18 | Windows (Windows XP Pro) | Any | WinMySQLAdmin shows no server info |
5879 | 2004-10-04 13:04 | 2019-11-14 14:00 | MySQL Server | Closed (7430 days) | S3 | 4.0 | Any (Any) | Any | Fix for Examined_rows in UNION's with 4.0 |
6483 | 2004-11-07 16:36 | 2004-12-03 3:53 | MySQL Server | Closed (7371 days) | S3 | 5.0.2 | Linux (linux) | Any | ignored character-set and collation |
7939 | 2005-01-16 16:33 | 2005-02-17 17:36 | MySQL Server | Closed (7295 days) | S3 | 4.1.9 | Any | --log-queries-not-using-indexes doesnt apply with 0 or 1 row OR quuery cache | |
9347 | 2005-03-23 4:32 | 2005-03-24 3:16 | MySQL Server | Duplicate (7260 days) | S1 | 1.1.6 | Windows (Windows 2003 Server) | Any | Crashes with MySQL server 5.0.2 |
10031 | 2005-04-20 14:11 | 2005-06-29 20:24 | MySQL Server | Closed (7163 days) | S1 | 5.0.5 | Any (all) | Any | View doesn't use index |
10931 | 2005-05-27 20:54 | 2005-06-21 11:00 | MySQL Server | Closed (7171 days) | S2 | 4.1.x | Any (All) | Any | Hostname cache completely broken in 4.1 |
14637 | 2005-11-04 12:51 | 2011-02-16 23:43 | MySQL Server | Closed (5452 days) | S5 | 5.0-BK | Any (any) | Any | trim trailing spaces processes data only byte wise |
16504 | 2006-01-14 13:53 | 2006-06-02 21:48 | MySQL Server | Closed (6825 days) | S3 | 5.0.21 | Any (*) | Any | Some of the simplest SELECTs are 1000 times slower in v5 compared to v4 |
17792 | 2006-02-28 16:31 | 2006-03-01 13:10 | MySQL Server | Duplicate (6918 days) | S1 | 5.0.18 | Linux (RHEL 4) | Any | Select with long IN clause cause server to run out of memory. |
18416 | 2006-03-22 10:48 | 2006-03-22 12:18 | MySQL Server | Closed (6897 days) | S3 | 5.0.18 | Linux (Linux) | Any | Renaming a table looses all triggers |
18656 | 2006-03-30 16:30 | 2011-02-16 23:43 | MySQL Server | Duplicate (5157 days) | S5 | 5.0.15 | Linux (Suse 10) | Any | User variable in where subquery causes long delay |
19836 | 2006-05-16 2:03 | 2012-05-18 20:19 | MySQL Server | Duplicate (6630 days) | S2 | all | Any (all) | Any | Dependent subquery in on clause is not optimized effectively. |
20986 | 2006-07-12 9:01 | 2008-09-27 11:01 | MySQL Server | Closed (5977 days) | S5 | 5.0.21-community-nt | Windows (Windows XP) | Any | renaming a column very slow on large tables |
21051 | 2006-07-13 23:07 | 2006-08-31 19:29 | MySQL Server | Closed (6735 days) | S3 | 5.0.22 | Any | RESET QUERY CACHE very slow when query_cache_type=0 | |
24556 | 2006-11-23 20:05 | 2006-12-05 22:51 | MySQL Server | Closed (6639 days) | S2 | 5.0.27 | Windows (Win 2003 server) | Any | mysqldump --all-databases does not dump all databases |
25785 | 2007-01-23 15:15 | 2011-03-29 18:52 | MySQL Server | Closed (5064 days) | S2 | 5.1.11 and higher | Linux (linux) | Any | set timestamp get 5 seconds to return |
25786 | 2007-01-23 15:20 | 2011-03-29 18:51 | MySQL Server | Closed (5064 days) | S2 | 5.1.11 | Linux (linux) | Any | select with limit 0 get row scan |
29278 | 2007-06-21 18:51 | 2012-05-18 20:19 | MySQL Server | Duplicate (6408 days) | S3 | Any | Any | log-output should default to FILE for backwards compliance. | |
41293 | 2008-12-08 10:21 | 2011-02-16 23:43 | MySQL Server | Verified (5778 days) | S2 | 5.0 bzr, 5.1 | Any | Any | user variables from remote hosts can be considerably slow |
41390 | 2008-12-11 10:55 | 2011-02-16 23:43 | MySQL Server | Verified (5902 days) | S2 | 3.2, 4.1, 5.0, 5.1, 6.0 bzr | Linux (pc-linux-gnu i486) | Any | mysqlbinlog doesn't properly handle local slow IO |
51153 | 2010-02-12 21:55 | 2011-02-16 23:44 | MySQL Server | Duplicate (5454 days) | S2 | 5.1.43-0.dotdeb.1 | Linux (2.6.31-19-generic #56-Ubuntu) | Any | mysqld/I_S takes hours to finish after boot/restart |
60345 | 2011-03-04 17:11 | 2013-01-15 15:25 | MySQL Server | Verified (4406 days) | S5 | 5.1.55 6.0.11 | Any | Any | trim trailing spaces processes data only byte wise (the continue of bug14637) |
2050 | 2003-12-08 16:07 | 2004-07-09 20:54 | MySQL Server | Closed (7518 days) | S2 | 4.1.1alpha | Windows (w2k) | Any | 10 to 1 performance drop with server 4.1.1 |
3904 | 2004-05-27 2:07 | 2004-06-09 23:37 | MySQL Server | Closed (7548 days) | S2 | 4.1.2 | Linux (Linux) | Any | COUNT DISTINCT performance anomaly in 4.1 |
4114 | 2004-06-12 2:27 | 2004-08-24 6:49 | MySQL Server | Closed (7472 days) | S2 | 4.1.2 | Any (all) | Any | order by - limit optimization is broken for "range" access type. |
6635 | 2004-11-15 12:47 | 2005-03-08 18:36 | MySQL Server | Closed (7276 days) | S2 | 4.1.7 | Linux (Linux x86) | Any | bug in full-text search |
7103 | 2004-12-08 12:58 | 2004-12-08 13:09 | MySQL Server | Duplicate (7366 days) | S1 | 5.0.2 | Windows (Windows 98 SE) | Any | mysql 5.0.2 mysqld crashes on describe any_table; |
16700 | 2006-01-21 13:13 | 2006-01-21 13:51 | MySQL Server | Duplicate (6957 days) | S3 | 5.0.18 | FreeBSD (FreeBSD 6.0-RELEASE-p3) | Any | optimizer marks subquery DEPENDENT though it's not |
22943 | 2006-10-03 15:10 | 2007-02-21 3:26 | MySQL Server | Closed (6561 days) | S2 | all | Windows (Windows) | Any | syscall pruning in libmysql |
25232 | 2006-12-21 13:24 | 2007-01-16 8:44 | MySQL Server | Closed (6597 days) | S2 | 5.0.30 | Linux (Linux AMD64 - SLES9-SP3 2.6.17) | Any | MySQL hangs in FUTEX_WAIT |
29031 | 2007-06-11 21:42 | 2020-05-03 20:45 | MySQL Server | Duplicate (6415 days) | S2 | 5.0.44-BK, 5.0.42 | Linux | Any | Comparison of DATE with DATETIME not using indexes correctly |
33948 | 2008-01-20 15:16 | 2011-02-16 23:43 | MySQL Server | Closed (5670 days) | S5 | 5.1.22 | Linux (rhas5) | Any | performance issue when using sysbench benchmark on a multiple-core system. |
47126 | 2009-09-04 9:18 | 2011-02-16 23:44 | MySQL Server | Closed (5451 days) | S3 | 5.1 | Any | Any | equal flag values causing unexpected behaviour |
18215 | 2006-03-14 8:52 | 2006-04-22 4:17 | MySQL Server | Closed (6866 days) | S2 | 4.1.18 | Linux (Linux) | Any | Long latency in connection establish |
79951 | 2016-01-13 12:58 | 2017-06-04 11:35 | MySQL Server | Closed (2805 days) | S2 | 5.7.10 | Windows | Any | Large table queries are very slow compared to 5.6 |
8475 | 2005-02-12 14:19 | 2005-03-08 0:35 | MySQL Server | Closed (7276 days) | S3 | 4.1 | Any (all) | Any | If multi-query: query does not get into slow query log if it's not last |
14275 | 2005-10-24 21:41 | 2005-10-24 23:53 | MySQL Server | Closed (7046 days) | S3 | 4.0.25 | Linux (Fedora Core 4 64bit) | Any | spitting out the wrong slow logs |
60348 | 2011-03-04 20:14 | 2013-01-15 15:25 | MySQL Server | Verified (4406 days) | S5 | 5.1.55 | Any | Any | trim trailing spaces processes data only byte wise (continue of bug14637 (2)) |
37536 | 2008-06-19 22:34 | 2011-02-16 23:43 | MySQL Server | Closed (5349 days) | S5 | 5.1.24 | Solaris (Nevada Bld 87 on X86) | Any | Thread scheduling causes performance degradation at low thread count |
14780 | 2005-11-09 8:44 | 2005-12-09 0:23 | MySQL Server | Closed (7000 days) | S3 | 4.1 | Linux (linux) | Any | memory leak for mysql 4.1.14 with openssl enabled |
38900 | 2008-08-19 20:14 | 2011-02-16 23:43 | MySQL Server | Duplicate (6014 days) | S2 | 5.0.66a | Any | Any | mysql_insert_id() and possibly last_insert_id() incorrect |
23135 | 2006-10-10 12:10 | 2006-10-10 13:39 | MySQL Server | Duplicate (6695 days) | S5 | 5.0.19 | Linux (Linux) | Any | Slow views performance |
23370 | 2006-10-17 13:32 | 2006-10-20 9:11 | MySQL Server | Duplicate (6685 days) | S1 | mysql-5.1.11-beta-win32 and 5.1.26 | Linux (Linux and Win) | Any | Bad nested group by performance |
24169 | 2006-11-10 7:41 | 2007-02-28 7:26 | MySQL Server | Closed (6554 days) | S1 | 5.1.12, 5.1.14 | Linux (Linux (Debian/Sarge)) | Any | Dramatic speed loss when going from 5.1.11 to 5.1.12 (or to 5.0.26) |
87756 | 2017-09-14 12:55 | 2017-10-02 11:17 | MySQL Server | Closed (2685 days) | S5 | 5.6 | Any | Any | JOINS and SUBQUERIES: huge performance difference between MySQL 5.5 and 5.6 |
2683 | 2004-02-09 6:48 | 2004-02-10 14:42 | MySQL Server | Closed (7668 days) | S3 | 4.1.1a | NT 4 Server SP 6a | Any | Poor Performance on a Multi-Homed System |
13762 | 2005-10-05 7:37 | 2007-12-04 21:17 | MySQL Server | Closed (6275 days) | S3 | 4.1.14 | Linux (linux) | Any | SHOW CREATE TABLE slowdown with InnoDB |
35918 | 2008-04-08 23:17 | 2014-02-25 19:54 | MySQL Server | Duplicate (4000 days) | S5 | 5.1.24 | Linux | Any | mysql-bench: slowdown for create table in 5.1.24 vs 5.0.58&5.1.23 |
8367 | 2005-02-08 9:46 | 2005-06-22 0:05 | MySQL Server | Closed (7170 days) | S3 | All | Any (All) | Any | slow log doesn't gives complete information about prepared statements |
10737 | 2005-05-19 11:38 | 2005-05-19 13:57 | MySQL Server | Duplicate (7204 days) | S2 | 4.1.12 | Linux (Linux) | Any | PS API queries in --log-slow-queries are unusable |
16493 | 2006-01-13 19:21 | 2012-05-18 20:19 | MySQL Server | Duplicate (6800 days) | S3 | 5.0.19-BK | probably all | Any | Slow query log logs SHOW statements |
17368 | 2006-02-14 10:04 | 2006-05-04 15:49 | MySQL Server | Closed (6854 days) | S2 | 5.1.6/5.1.7 BK | Windows (Windows XP) | Any | General log and slow query log don't work |
40263 | 2008-10-22 18:41 | 2008-10-22 18:47 | MySQL Server | Duplicate (5952 days) | S3 | 5.0+ | Any | Any | Server default log filenames do not use hostname |
106410 | 2022-02-08 17:16 | 2022-02-08 19:31 | MySQL Server | Duplicate (1095 days) | S3 | 5.734 | Any | Any | Upgraded Mysql 5.6 to Mysql 5.7. All Queries are running damn slow after upgrade |
10480 | 2005-05-09 15:11 | 2005-06-16 7:44 | MySQL Server | Closed (7176 days) | S2 | 4.1.11-standard-log | Linux (Linux Redhat Fedora Core 1) | Any | Slow queries |
60961 | 2011-04-23 18:59 | 2014-03-28 19:39 | MySQL Server | Closed (4649 days) | S2 | 5.6, 5.5, 5.1 | Any | Any | show tables very slow when not in system disk cache |
796 | 2003-07-06 7:35 | 2003-07-06 12:36 | MySQL Server | Closed (7887 days) | S3 | 4.1 | Any (any) | Any | memory leak in group_concat |
2613 | 2004-02-02 8:20 | 2004-06-16 16:18 | MySQL Server | Closed (7541 days) | S3 | 4.0 | Any | memory leak in drop database with raid | |
47623 | 2009-09-24 16:20 | 2011-02-16 23:44 | MySQL Server | Duplicate (5406 days) | S1 | 5.0.44, 5.0.85 | Linux (Centos) | Any | Suspected memory/temporary file leak |
56382 | 2010-08-30 19:11 | 2011-02-16 23:44 | MySQL Server | Closed (5231 days) | S2 | 5.1.50 | Any | Any | valgrind leak warning from main.loaddata |
100114 | 2020-07-05 8:03 | 2020-07-13 12:47 | MySQL Server | Closed (1672 days) | S2 | 5.7.25 | CentOS (7.6) | Any | bluk_insert may lead to memory leak |
60349 | 2011-03-04 21:20 | 2013-01-15 15:25 | MySQL Server | Verified (4406 days) | S5 | 5.1.55 | Any | Any | trim beginning spaces processes data only byte wise (continue of bug14637 (3)) |
60351 | 2011-03-04 22:15 | 2013-01-15 15:27 | MySQL Server | Verified (4406 days) | S5 | 5.1.55 | Any | Any | trim same character processes data only byte wise (continue of bug14637 (4)) |
106390 | 2022-02-07 10:08 | 2022-07-18 11:45 | MySQL Server | Duplicate (1095 days) | S5 | 8.0.28 | Debian | Any | CREATE TABLE performance in MySQL 8 is considerably slower than 5.7 |
3531 | 2004-04-21 19:09 | 2004-04-22 8:20 | MySQL Server | Closed (7596 days) | S2 | 5.0.0 & 4.1.1a-alpha | Windows (Windows XP) | Any | Prepared statement memory leak while connection is open |
1952 | 2003-11-25 13:49 | 2003-12-11 17:26 | MySQL Server | Closed (7729 days) | S3 | Any | Any (Any) | Any | SHOW TABLE STATUS very slow w/large number of tables |
4497 | 2004-07-10 1:21 | 2004-08-09 23:15 | MySQL Server | Closed (7487 days) | S3 | 4.0.21 | Linux (linux) | Any | Serious regression if disk based TMP table is used. |
9968 | 2005-04-18 9:31 | 2005-08-06 23:23 | MySQL Server | Closed (7125 days) | S1 | 5.0 | Any (all) | Any | slow query log contains useless entries |
12240 | 2005-07-28 14:04 | 2006-10-20 17:46 | MySQL Server | Closed (6685 days) | S3 | 4.1.13 | Windows (Windows\Linux) | Any | Rows Examined in Slow Log showing incorrect number? |
12831 | 2005-08-26 13:21 | 2008-04-02 13:50 | MySQL Server | Closed (6155 days) | S3 | 4.1.13/BK 4.1 source | Any (5.4) | Any | long_query_time is flawed because it is an integer |
15774 | 2005-12-15 13:39 | 2005-12-16 10:18 | MySQL Server | Closed (6993 days) | S1 | 5.0 | Windows (Windows XP PRO Sp2) | Any | slow / increase memory / crashing / OS freezing |
18669 | 2006-03-30 22:22 | 2006-05-31 1:18 | MySQL Server | Closed (6827 days) | S3 | 5.0,5.1 | Linux (Linux) | Any | Session COM_STATISTICS breaks mysqladmin status |
39461 | 2008-09-15 20:54 | 2008-10-20 13:05 | MySQL Server | Closed (5954 days) | S3 | 5.0.60 | Linux | Any | Slow Query |
61818 | 2011-07-11 8:22 | 2011-07-11 9:03 | MySQL Server | Closed (4960 days) | S2 | 5.1.57 | Linux (debian 6 64 bit) | Any | debian 6 64 bit + mysql 5.1.57 insert innodb very very slow |
76585 | 2015-04-03 10:07 | 2018-02-19 14:36 | MySQL Server | Closed (2545 days) | S3 | 5.6.27, 5.7.21 | Any | Any | Runtime changes to `long_query_time` are ignored. |
96340 | 2019-07-26 12:13 | 2023-09-29 7:51 | MySQL Server | Closed (1899 days) | S3 | 8.0.17 | Any | Any | Slow startup for mysql 8.0 with many tables due to the tablespace files scan |
1697 | 2003-10-29 3:45 | 2003-12-13 3:36 | MySQL Server | Closed (7727 days) | S2 | 4.0.16 | Any (all) | Any | DELETE ... WHERE ... ORDER BY ... wrong execution leads to very bad performance |
485 | 2003-05-23 12:38 | 2003-06-05 10:38 | MySQL Server | Duplicate (7918 days) | S2 | 4.1 | Windows (Windows ONLY) | Any | Remote Performance Issue Windows in 4.1 |
5969 | 2004-10-08 5:49 | 2004-10-10 10:52 | MySQL Server | Closed (7425 days) | S1 | 5.0.2 | Linux (Linux) | Any | Performance Problem with updatable VIEW |
12662 | 2005-08-19 2:20 | 2005-08-19 2:41 | MySQL Server | Duplicate (7112 days) | S2 | 5.0.9 | FreeBSD (FreeBSD 5.4) | Any | Poor View Performance |
40006 | 2008-10-13 15:04 | 2008-10-22 10:56 | MySQL Server | Closed (5952 days) | S5 | 5.0.18 | Any | Any | Performance depends on functions used? |
42908 | 2009-02-17 1:20 | 2011-02-16 23:43 | MySQL Server | Closed (5206 days) | S5 | 5.0.74, 5.0.76, 5.0.77 | Linux (SLES 10) | Any | Performance degradation on SELECT_DISTINCT_RANGES (as in Sysbench) |
46085 | 2009-07-09 13:49 | 2011-02-16 23:44 | MySQL Server | Duplicate (5630 days) | S3 | 5.4.2 (summit), mysql-trunk | Linux | Any | Valgrind warnings (InnoDB code) in test rpl_trigger |
54518 | 2010-06-15 14:25 | 2012-10-15 13:31 | MySQL Server | Closed (4498 days) | S5 | 5.0.22 | Windows (Vista) | Any | Very bad performance with subselect |
66865 | 2012-09-19 3:18 | 2017-01-25 14:20 | MySQL Server | Closed (2935 days) | S3 | 5.6 | Any | Any | Performance degradation in MySQL 5.6 |
71041 | 2013-11-29 18:39 | 2017-09-05 1:11 | MySQL Server | Closed (2712 days) | S3 | 5.6 | Any | Any | Please, document every instrument in P_S.setup_instruments in details |
75108 | 2014-12-04 19:35 | 2015-01-15 19:26 | MySQL Server | Closed (3676 days) | S2 | 6.2.3 | Windows (Microsoft Windows 7 Home Premium Service Pack 1) | Any | No Connection to MySQL server. Port 3306 not available. |
76117 | 2015-03-03 6:56 | 2015-03-04 7:40 | MySQL Server | Duplicate (3628 days) | S5 | 5.6.16-log | Windows | Any | Index cardinality not being updated when the data is changed |
109603 | 2023-01-12 12:06 | 2023-01-12 14:10 | MySQL Server | Duplicate (757 days) | S3 | Any | Any | MySQL8 write performance degrades compares to MySQL 5.7 | |
111868 | 2023-07-25 2:54 | 2024-03-21 11:18 | MySQL Server | Duplicate (563 days) | S5 | Any | Any | benchmarksql performance degradation since 8.0.27 | |
10064 | 2005-04-21 15:39 | 2007-11-09 9:27 | MySQL Server | Closed (6300 days) | S1 | 3.1 | Linux (RedHat 4) | Any | udf deinit not called when using PreparedStatements |
10107 | 2005-04-23 0:53 | 2005-04-28 15:29 | MySQL Server | Closed (7225 days) | S3 | 5.0-bk | Any | Memory leak in view over subquery | |
11247 | 2005-06-10 15:14 | 2005-08-18 21:01 | MySQL Server | Closed (7113 days) | S3 | 5.0 | Any (Any) | Any | Stored procedures: Function calls in long loops leak memory |
13471 | 2005-09-25 17:13 | 2005-09-26 9:52 | MySQL Server | Closed (7074 days) | S2 | 5.0.14-rc, tadays pull | Linux (Linux) | Any | Memory leak in ha_tina |
18174 | 2006-03-13 0:29 | 2006-03-13 5:56 | MySQL Server | Duplicate (6906 days) | S2 | 5.0.19-standard-log/Oficial tarball | Linux (Debian/Gnu ia32/2.4.32) | Any | Memory leak on update with big NOT IN (). |
19739 | 2006-05-11 20:10 | 2006-05-18 23:28 | MySQL Server | Closed (6840 days) | S3 | 5.0.20 | Windows (Windows XP) | Any | stored function call in primary select causes memory leak |
19798 | 2006-05-14 0:16 | 2006-05-23 8:02 | MySQL Server | Closed (6835 days) | S2 | 5.1.10-pre | Linux (Red Hat RHAS4 x86 x86_64) | Any | Test 'func_encrypt' leaks memory when using yaSSL |
25396 | 2007-01-03 20:26 | 2007-01-24 20:28 | MySQL Server | Closed (6589 days) | S1 | 5.1 | Any | Valgrind leak in closecon_handlerton | |
26750 | 2007-03-01 14:52 | 2007-03-07 21:37 | MySQL Server | Closed (6547 days) | S1 | 5.0 | Any | valgrind leak in sp_head | |
21461 | 2006-08-06 1:28 | 2007-07-13 0:37 | MySQL Server: Archive storage engine | Closed (6419 days) | S5 | 5.0 | Any (all) | Any | Long Varchars created unneeded waste in compression in Archive |
26773 | 2007-03-01 22:16 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Duplicate (5412 days) | S1 | 5.0.27-max | Linux (Debian 3.1 (kernel 2.6.14.2)) | Any | Possible Memory Leak with Archive Tables |
99694 | 2020-05-26 13:06 | 2020-06-01 15:23 | MySQL Server: Charsets | Verified (1712 days) | S5 | 8.0 | Any | Any | Improving performance of my_hash_sort_utf8(mb4)/my_strnncollsp*utf8(mb4) |
55606 | 2010-07-28 15:25 | 2015-08-30 17:21 | MySQL Server: Charsets | Verified (4292 days) | S5 | 5.1.47, 5.1.50-bzr, 5.5.23, 5.6.11 | Linux | Any | Charset on ENUMS influencing performance too much |
85331 | 2017-03-06 19:46 | 2017-09-27 2:00 | MySQL Server: Charsets | Closed (2690 days) | S3 | 5.6, 5.7, etc, 5.6.35 | Any | Any | _characterset specifications have lousy performance for some character sets |
116492 | 2024-10-28 11:47 | 2024-11-06 13:48 | MySQL Server: Charsets | Verified (93 days) | S5 | 8.0, 8.0.40 | Any | Any | The utf8mb4 character set has worse performance |
68366 | 2013-02-13 16:03 | 2018-01-18 13:19 | MySQL Server: Charsets | Closed (2577 days) | S5 | 5.5.29-0ubuntu0.12.10.1-log for debian- | Linux (Ubuntu 12.10) | Any | regression: >=mysql-5.4 utf8 collations are marked as not ascii compatible |
72715 | 2014-05-21 22:39 | 2014-05-22 8:02 | MySQL Server: Charsets | Verified (3914 days) | S3 | 5.6.17 | Any | Any | character set code endianness dependent on CPU type rather than endianness of CP |
83319 | 2016-10-10 12:44 | 2017-07-05 15:37 | MySQL Server: Charsets | Closed (3007 days) | S3 | 8.0.1 | Any | Any | Performance regression when changing character set to utf8mb4 |
99190 | 2020-04-06 11:51 | 2020-04-06 14:06 | MySQL Server: Charsets | Verified (1768 days) | S5 | 8.0 | Any | Any | my_tosort_unicode: unnecessary max_char check while utf8-mb3 processing |
38720 | 2008-08-11 14:07 | 2018-01-18 13:11 | MySQL Server: Charsets | Closed (2577 days) | S2 | 5.0, 5.1, 6.0 bzr | Linux (Etch 4.0(am64 and x86)) | Any | SELECT DISTINCT on multiple attributes containing spaces in UTF8 are slow. |
43707 | 2009-03-17 16:29 | 2011-02-16 23:43 | MySQL Server: Charsets | Verified | S3 | 6.0.10, 5.6 | Linux (2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 x86_64 x86_64 x86_64 GNU/Linux) | Any | Columns in general_log and slow_log changed to "longtext" during upgrade |
60726 | 2011-04-01 21:01 | 2011-04-03 11:54 | MySQL Server: Charsets | Duplicate (5059 days) | S2 | 5.5.10 | Linux (Debian Lenny, Arch Linux, adm64 and x86) | Any | Functions doing implicit int to string conversion called repeatedly slow down |
68795 | 2013-03-27 12:22 | 2013-07-30 13:47 | MySQL Server: Charsets | Closed (4210 days) | S3 | 5.5.30 | Any | Any | Datetime field comparisons do not work properly with utf8_unicode_ci collation |
84577 | 2017-01-20 8:49 | 2017-08-21 19:47 | MySQL Server: Charsets | Closed (2923 days) | S3 | Any | Any | strnxfrm runs slower when tailoring rule contains contraction | |
35165 | 2008-03-08 17:48 | 2022-12-04 20:45 | MySQL Server: CSV | Verified (6176 days) | S5 | 5.1 | Any | Any | Logging to table is slow for large queries |
93394 | 2018-11-29 5:46 | 2018-11-29 14:55 | MySQL Server: CSV | Verified (2262 days) | S3 | 5.7.21 | Any | Any | memory leak when csv engine has no permission to meta file |
95792 | 2019-06-13 15:21 | 2019-07-10 18:39 | MySQL Server: Data Dictionary | Closed (2039 days) | S2 | 8.0.18 | Any | Any | DD function for fetching tables in engine |
98449 | 2020-01-31 12:25 | 2023-11-02 6:26 | MySQL Server: Data Dictionary | Closed (463 days) | S5 | 8.0.19 | Any | Any | SELECT from I_S.INNODB_COLUMNS is slow in 8.0 |
103195 | 2021-04-02 9:48 | 2021-04-13 13:23 | MySQL Server: Data Dictionary | Verified (1397 days) | S5 | 8.0 | Linux (rhel-7.4) | Any (x86-64) | it gets very slow to access an empty table after drop a big database |
91420 | 2018-06-26 10:03 | 2018-08-14 17:43 | MySQL Server: Data Dictionary | Closed (2369 days) | S3 | 8.0.11 | Any | Any | Allocate DD auto releaser maps on demand |
115524 | 2024-07-05 10:13 | 2024-07-18 8:48 | MySQL Server: Data Dictionary | Verified (205 days) | S3 | 8.0.38, 9.0.0 | Any | Any | key_object_cache_mutex and key_object_loading_cond are not registered |
82631 | 2016-08-18 11:45 | 2016-11-29 1:59 | MySQL Server: DDL | Closed (3091 days) | S3 | 8.0.1 | Any | Any | std::basic_string instantiation w/ PFS instrumentation for the DD |
106399 | 2022-02-08 1:55 | 2022-02-09 4:18 | MySQL Server: DDL | Duplicate (1095 days) | S3 | 8.0.26 | Any | Any | Regression on DDL statements with big stage/sql/checking permissions |
114465 | 2024-03-24 6:32 | 2024-08-29 22:44 | MySQL Server: DDL | Closed (162 days) | S5 | 8.0.36, 8.3.0 | Any | Any | Regression in 8.0.27+ related to Parallel DDL IO Amplification |
51680 | 2010-03-03 8:36 | 2011-02-16 23:44 | MySQL Server: DDL | Duplicate (5455 days) | S3 | 5.1.43 | IBM AIX | Any | "ALTER TABLE ... DELAY_KEY_WRITE=1" causes a full table copy |
94610 | 2019-03-08 19:09 | 2020-08-05 0:00 | MySQL Server: DDL | Verified (1647 days) | S5 | 5.6.41 | CentOS (7.5) | x86 | Server stalls because ALTER TABLE on partitioned table holds dict mutex |
106560 | 2022-02-24 14:51 | 2023-10-19 10:51 | MySQL Server: DDL | Duplicate (1077 days) | S3 | 8.0.28 | Any | Any | slow DDL in mysql 8.0 as compare to 5.7 taking more time for checking permission |
24495 | 2006-11-22 3:37 | 2008-09-27 10:42 | MySQL Server: DDL | Closed (5977 days) | S5 | 5.1.14-BK, 5.1.12-beta,5.0.24a | Linux (Linux, Windows Server 2003 x64) | Any | "create index" gets slower the more indexes there are |
116738 | 2024-11-21 4:09 | 2024-11-29 10:11 | MySQL Server: DDL | Verified (70 days) | S5 | 8.0.40 | Any | Any | The DDL performance of 8.0.40 has not been restored to 8.0.26 |
22487 | 2006-09-19 17:57 | 2020-05-03 20:45 | MySQL Server: DDL | Verified (6540 days) | S5 | 5.0.26 | Any | Any | mysql performs extremely slow when creating unique indexes on huge table |
8565 | 2005-02-17 11:50 | 2022-12-04 20:45 | MySQL Server: DDL | Duplicate (4592 days) | S2 | 5.0.30 | Any (*) | Any | ALTER TABLE MODIFY adds duplicate keys which slow down SELECTs |
74487 | 2014-10-21 19:07 | 2015-02-16 20:38 | MySQL Server: DDL | Closed (3644 days) | S3 | 5.7.5-labs-preview | Any | Any | primary key missing for query_rewrite.rewrite_rules |
42259 | 2009-01-22 6:36 | 2012-07-31 12:15 | MySQL Server: DML | Closed (4574 days) | S2 | 5.5.25 | Linux (Ubuntu 12.04 x86_64) | Any | Utilizing a SELECT within a WHERE IN performs poorly (slow) |
109548 | 2023-01-09 7:55 | 2023-12-20 12:33 | MySQL Server: DML | Closed (415 days) | S5 | 8.0.13,8.0.31 | Any | Any | Poor performance when using HASH field to check unique |
40374 | 2008-10-28 17:32 | 2008-11-29 15:56 | MySQL Server: DML | Closed (5914 days) | S3 | 5.0.51a | Linux (Debian Lenny amd64) | Any | LOAD DATA with CONVERT_TZ causes memory leak |
45962 | 2009-07-06 8:39 | 2011-02-16 23:44 | MySQL Server: DML | Closed (5623 days) | S2 | 5.0.84, 5.1.37, 6.0.12 | Any | Any | memory leak after 'sort aborted' errors |
50774 | 2010-02-01 2:23 | 2011-05-13 14:21 | MySQL Server: DML | Closed (5019 days) | S1 | 5.1.44, 5.1.49, 5.5.99, 5.5.6rc | Any | Any | Wrong resultset when timestamp values are appended with .0 |
75807 | 2015-02-06 10:00 | 2015-02-20 9:54 | MySQL Server: DML | Verified (3642 days) | S5 | 5.6.22 | Linux | Any | Slow Query in MySQL 5.6 |
107026 | 2022-04-14 16:17 | 2022-04-15 12:13 | MySQL Server: DML | Closed (1029 days) | S3 | 5.7.36 | Debian | x86 | Update performs full table scan due to too many indexes |
69368 | 2013-05-31 20:36 | 2013-10-11 16:23 | MySQL Server: DML | Closed (4137 days) | S5 | 5.6.6 | Any | Any | performance regression in 5.6.6+ for insert into .... select ... from |
70202 | 2013-08-30 15:36 | 2013-09-02 11:53 | MySQL Server: DML | Verified (4176 days) | S3 | 5.5, 5.6 | Any | Any | REPLACE working differently for a table having PK or UK only versus both PK+UK |
87637 | 2017-09-01 8:44 | 2017-12-18 8:46 | MySQL Server: DML | Verified (2608 days) | S5 | 5.7.17 | Linux | Any | High CPU occupancy rate |
116393 | 2024-10-17 12:46 | 2025-01-16 11:29 | MySQL Server: DML | Closed (23 days) | S5 | 8.0 | Any | Any | Degrading performance of MD5(), SHA2() functions |
102150 | 2021-01-05 11:53 | 2021-01-06 8:16 | MySQL Server: DML | Verified (1493 days) | S5 | MySQL 8.0.22 | Any | Any | Performance of repeat() function need to be optimized |
113800 | 2024-01-30 5:30 | 2024-01-31 8:28 | MySQL Server: DML | Verified (373 days) | S5 | 8.0.22, 8.0.36, 8.0.11 | Linux | x86 | Performance degradation of Blob operations comparing with MySQL 5.7 |
102774 | 2021-03-02 0:37 | 2021-03-06 7:15 | MySQL Server: DML | Verified (1434 days) | S3 | 5.7.31,8.0.22, 5.7.33 | Any | Any | A scenario that result in memory leak |
67892 | 2012-12-13 2:37 | 2012-12-14 13:18 | MySQL Server: Errors | Closed (4438 days) | S3 | 5.5.28, 5.6.9 | Any | Any | Warning recommends to use a deprecated or non-existing option |
60968 | 2011-04-24 18:40 | 2011-04-25 19:50 | MySQL Server: Errors | Verified (5037 days) | S3 | 5.1.43sp1-enterprise-gpl-advanced-log | Any | Any | Cancelled queries not reported in slow query log |
70402 | 2013-09-23 21:35 | 2013-11-12 1:47 | MySQL Server: Errors | Closed (4105 days) | S5 | 5.7.2 | Any | Any | new deprecation warnings introduce unwanted performance degradation side-effect |
26697 | 2007-02-27 21:53 | 2013-03-03 20:45 | MySQL Server: Federated storage engine | Verified (6539 days) | S2 | 5.0.38-BK, 5.0.27, 5.1 | Linux (Linux, Windows 2000) | Any | Every query to a federated table results in a full scan of MyISAM table. |
40875 | 2008-11-20 7:10 | 2011-02-16 23:43 | MySQL Server: Federated storage engine | Closed (5910 days) | S2 | 5.0 | Any | Any | Memory leak in FEDERATED handler |
21472 | 2006-08-07 7:13 | 2006-08-26 12:46 | MySQL Server: Federated storage engine | Duplicate (6740 days) | S5 | 5.1.12 | Linux (linux) | Any | question about the query against to the federated engine tables |
68572 | 2013-03-05 10:57 | 2014-02-19 16:19 | MySQL Server: Federated storage engine | Verified (4356 days) | S3 | 5.5.25a, 5.5.31 | Any | Any | FEDERATED using SHOW TABLE STATUS causes performance problems for InnoDB tables |
34789 | 2008-02-24 13:49 | 2008-04-22 14:15 | MySQL Server: Federated storage engine | Closed (6135 days) | S3 | 5.1.23, 5.1.24-rc | Any | Any | drop server/create server leaks memory ! |
75763 | 2015-02-04 13:29 | 2015-02-05 8:19 | MySQL Server: FULLTEXT search | Verified (3655 days) | S2 | 5.6.21, 5.6.24 | Any | Any | InnoDB FULLTEXT index reduces insert performance by up to 6x on JSON docs |
102249 | 2021-01-14 15:56 | 2021-01-27 17:40 | MySQL Server: Group Replication | Verified (1481 days) | S3 | 8.0.22 | Any | Any | Slow query log filling up with performance_schema queries |
99133 | 2020-03-31 15:08 | 2024-01-30 17:50 | MySQL Server: Group Replication | Verified (1767 days) | S3 | 8.0.19 | Any | Any | Group Replication Performance Degradation with partial network outage |
116013 | 2024-09-05 15:36 | 2024-10-23 12:45 | MySQL Server: Group Replication | Verified (107 days) | S5 | all versions | Any | Any | Mitigate Performance Fluctuations in MySQL Group Replication |
84773 | 2017-02-01 14:29 | 2017-10-04 14:14 | MySQL Server: Group Replication | Closed (2683 days) | S5 | 5.7.17 | Linux | Any | Flow control slows down throughput while a node join the cluster |
84774 | 2017-02-01 14:53 | 2024-11-05 3:01 | MySQL Server: Group Replication | Verified (2927 days) | S5 | 5.7.17 | Any | Any | Performance drop every 60 seconds |
86626 | 2017-06-08 16:42 | 2017-11-08 10:28 | MySQL Server: Group Replication | Closed (2699 days) | S3 | 5.7.19 | Any | Any | Group replication partition handling thread is not instrumented on perf schema |
89195 | 2018-01-11 19:15 | 2019-07-25 14:45 | MySQL Server: Group Replication | Closed (2024 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Total ordering of transactions is not respected in Group Replication. |
91151 | 2018-06-05 17:12 | 2019-05-06 3:33 | MySQL Server: Group Replication | Verified (2438 days) | S3 | 8.0.11 | Any | Any | Add a Learner/Observer role to leverage it in WAN setup |
110518 | 2023-03-27 23:53 | 2023-12-23 13:54 | MySQL Server: Group Replication | Closed (412 days) | S3 | all, 8.0 | Any | Any | Memory leak possible |
115162 | 2024-05-29 13:01 | 2024-09-18 9:06 | MySQL Server: Group Replication | Closed (143 days) | S2 | 8.0 | Any | Any | Potential Memory Leak in file `xcom\network\xcom_network_provider_native_lib.cc` |
26967 | 2007-03-08 18:00 | 2014-12-21 11:15 | MySQL Server: General | Verified (6542 days) | S3 | 5.0.37 | Any (all) | Any | SHOW PROFILE: Inconsistent output capitalization |
34820 | 2008-02-25 21:03 | 2008-10-05 16:43 | MySQL Server: General | Closed (5969 days) | S3 | 5.1 | Any | Any | log_output can be set to illegal value |
57058 | 2010-09-28 9:57 | 2011-02-16 23:44 | MySQL Server: General | Closed (5146 days) | S3 | 5.5.6 | Any | Any | SERVER_QUERY_WAS_SLOW not wired up. |
60811 | 2011-04-08 23:41 | 2020-08-15 10:10 | MySQL Server: General | Verified (5052 days) | S5 | 5.0.93, 5.5.12, 5.0.77-4.el5_5.4 | Any (RHEL 5.5, Mac OS X) | Any | slow timezone functions |
61621 | 2011-06-23 22:51 | 2011-06-24 4:06 | MySQL Server: General | Duplicate (4977 days) | S3 | 5.5.13 | Linux (Ubuntu) | Any | ALTER TABLE very slow on empy partitioned table |
107903 | 2022-07-18 14:42 | 2022-07-19 11:48 | MySQL Server: General | Analyzing (934 days) | S3 | Any | Any | Contribution: Each slow log prints out the database name | |
24509 | 2006-11-22 15:09 | 2011-02-16 23:43 | MySQL Server: General | Closed (5351 days) | S3 | 5.0,5.1 | Windows (Windows) | Any | 2048 file descriptor limit on windows needs increasing |
28382 | 2007-05-11 15:48 | 2007-05-11 18:30 | MySQL Server: General | Duplicate (6482 days) | S3 | Several | Any | Any | Query cache considered harmful |
30439 | 2007-08-15 14:45 | 2007-08-16 5:14 | MySQL Server: General | Duplicate (6385 days) | S3 | 5.0.45 | Linux | Any | tmpdir is not followed for temporary tables in group by |
39492 | 2008-09-17 0:58 | 2011-02-16 23:43 | MySQL Server: General | Closed (5897 days) | S5 | 5.0.51a | Solaris | Any | solaris should use a separate alarm thread |
42705 | 2009-02-09 16:37 | 2011-02-16 23:43 | MySQL Server: General | Verified (5800 days) | S3 | 5.1.30 | Any | Any | Reduce malloc/free during query lifecycle. |
43427 | 2009-03-05 17:17 | 2012-03-18 18:41 | MySQL Server: General | Verified (5815 days) | S5 | 5.0 | Any | Any | Don't limit table_cache_size as a function of max_connections |
47286 | 2009-09-12 11:22 | 2011-11-28 15:40 | MySQL Server: General | Closed (4820 days) | S3 | 5.1.38 | Any | Any | 'have_federated' variable not implemented |
49491 | 2009-12-06 23:14 | 2011-02-16 23:44 | MySQL Server: General | Closed (5446 days) | S5 | 5.1.38 and above | Any | Any | Much overhead for MD5() and SHA1() on short strings |
54790 | 2010-06-25 3:58 | 2011-06-03 2:10 | MySQL Server: General | Closed (4998 days) | S3 | 5.1.47 | Any | Any | Use of non-blocking mode for sockets limits performance |
112175 | 2023-08-24 13:32 | 2023-08-24 13:40 | MySQL Server: General | Analyzing (533 days) | S3 | Any | Any | Contribution: [performance optimization] | |
52410 | 2010-03-27 18:43 | 2011-02-16 23:44 | MySQL Server: General | Closed (5377 days) | S3 | 5.5.3-m3 | Any | Any | Test "mysqld--help-*": further output differences |
61204 | 2011-05-17 15:24 | 2011-05-18 9:35 | MySQL Server: General | Closed (5014 days) | S3 | 5.0.51a | Linux (mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (x86_64)) | Any | Inacurate statistics on a server with 50% persistent connections |
34254 | 2008-02-02 20:26 | 2008-02-04 2:23 | MySQL Server: General | Closed (6213 days) | S2 | 5.1.22 RC (x64) | Windows (XP x64 AMD DC) | Any | Very slow queries when using functions in SELECT statements |
22947 | 2006-10-03 16:16 | 2006-10-03 16:20 | MySQL Server: General | Duplicate (6702 days) | S2 | 4.1.21 | Linux 2.4.18 SMP kernel | Any | Performance regression in C API 4.1 versus 4.0 |
51286 | 2010-02-18 15:56 | 2011-02-16 23:44 | MySQL Server: General | Verified (5468 days) | S3 | any | Any | Any | Request to add performance regression to release acceptance tests |
21798 | 2006-08-23 17:36 | 2006-10-25 19:21 | MySQL Server: General | Closed (6680 days) | S2 | 5.0.24 | Linux (Linux 2.6.15 (Ubuntu 6.06 LTS)) | Any | memory leak during query execution with subquery in column list using a function |
25659 | 2007-01-16 22:38 | 2007-05-24 7:27 | MySQL Server: General | Closed (6469 days) | S3 | 5.1 | Any | Any | memory leak via "plugins" test |
42412 | 2009-01-28 10:53 | 2011-02-16 23:43 | MySQL Server: General | Closed (5638 days) | S3 | 6.0,5.4 | Any | Any | IPv6 connection handling code bugs |
42158 | 2009-01-16 13:48 | 2011-02-16 23:43 | MySQL Server: General | Closed (5706 days) | S2 | 4.1, 5.0, 5.1, 6.0 | Any | Any | leak: SSL_get_peer_certificate() doesn't have matching X509_free() |
25222 | 2006-12-20 19:15 | 2007-03-13 19:10 | MySQL Server: General | Closed (6541 days) | S3 | 5.0 | Windows (windows) | Any | Win32 HANDLE leak in my_sopen() |
52629 | 2010-04-06 18:54 | 2011-02-16 23:44 | MySQL Server: General | Closed (5348 days) | S3 | 5.1.45, 5.1 bzr | Any | Any | memory leak from sys_var_thd_dbug in binlog.binlog_write_error |
47937 | 2009-10-09 9:11 | 2011-02-16 23:44 | MySQL Server: General | Verified (5600 days) | S5 | Any | Any | Appending to fields using CONCAT gets very slow | |
37703 | 2008-06-27 21:20 | 2015-04-29 0:09 | MySQL Server: General | Closed (3572 days) | S5 | MYSQL 6.0.4 (Source Distribution) | Linux (EL5.1) | Any | MySQL performance with and without Fast Mutexes using Sysbench Workload |
42608 | 2009-02-04 21:42 | 2011-02-16 23:43 | MySQL Server: General | Closed (5831 days) | S3 | Summit v0.2.0 | Any | Any | Summit may need changes to default config parameters for optimal performance |
50367 | 2010-01-15 14:12 | 2011-02-16 23:44 | MySQL Server: General | Verified (5440 days) | S5 | 5.1.42, 5.1 bzr | Any (MS Windows 32 bits, Mac) | Any | REPLACE has quadradic computational complexity on windows server (but not linux) |
27271 | 2007-03-19 18:38 | 2007-03-25 13:23 | MySQL Server: General | Closed (6529 days) | S3 | 5.0.32-Debian_7-log | Linux (Debian Etch 64bit) | Any | Repeating a query slows it down |
27924 | 2007-04-18 10:36 | 2007-05-21 10:27 | MySQL Server: General | Closed (6472 days) | S2 | 5.0.24-Debian_1~bpo.1-log | Linux (Debian 3.1 i386) | Any | FLUSH LOGS crashes database |
102599 | 2021-02-15 12:11 | 2023-12-19 10:19 | MySQL Server: GIS | Verified (1452 days) | S5 | 8.0.22 | Windows (Win 10) | x86 (NVMe RAM) | Slow performance of MySQL 8 compared with 5.7 on geographical SELECT |
96311 | 2019-07-24 9:02 | 2020-02-19 17:38 | MySQL Server: GIS | Duplicate (1815 days) | S5 | 8.0.17 | Any | Any | ST_Intersects() is very slow on MySQL 8.0 |
79406 | 2015-11-25 9:49 | 2017-12-23 10:50 | MySQL Server: GIS | Closed (2653 days) | S2 | 5.7.9 GA, 5.7.11 | Any | Any | Extremely poor selection performance compared to MySQL 5.6.27 on InnoDB & MyISAM |
59111 | 2010-12-22 10:40 | 2011-02-16 23:44 | MySQL Server: GIS | Closed (5112 days) | S3 | 5.6+ | Any | Any | gis crashes when server is compiled without performance schema |
77960 | 2015-08-06 11:21 | 2016-02-04 19:18 | MySQL Server: GIS | Closed (3451 days) | S3 | Any | Any | Upgrade to Boost 1.59.0 | |
79380 | 2015-11-23 8:11 | 2016-06-18 21:34 | MySQL Server: GIS | Closed (3304 days) | S3 | 8.0.0 | Any | Any | Upgrade to Boost 1.60.0 |
89122 | 2018-01-05 16:47 | 2018-03-19 17:49 | MySQL Server: GIS | Closed (2579 days) | S3 | 8.0.5 | Any | Any | Severe performance regression in server bootstrap |
74371 | 2014-10-14 11:32 | 2014-10-31 15:18 | MySQL Server: GIS | Closed (3752 days) | S3 | 5.7.6 | Any | Any | Valgrind: Memory leak when doing spatial operations on geometrycollections |
35414 | 2008-03-18 19:16 | 2012-08-08 11:01 | MySQL Server: GIS | Duplicate (4566 days) | S3 | 5.0.51 and 5.0.51a | Other (Linux / Solaris) | Any | MBRContains fails to select records when using index |
83166 | 2016-09-27 10:09 | 2016-11-21 17:45 | MySQL Server: GIS | Closed (3010 days) | S5 | 5.7.15 | Any | Any | Query execution involving spatial and non-spatial data very slow |
74949 | 2014-11-21 6:30 | 2015-04-06 18:53 | MySQL Server: GIS | Closed (3665 days) | S3 | 5.7.6 | Any | Any | GIS performance issue: too many reallocs |
39990 | 2008-10-12 16:19 | 2022-09-04 20:45 | MySQL Server: Information schema | Duplicate (5961 days) | S3 | 5.1.23, 5.1.28 | Any | Any | poor performace of "SHOW VARIABLES" |
42248 | 2009-01-21 18:27 | 2011-02-16 23:43 | MySQL Server: Information schema | Duplicate (5861 days) | S5 | 6.0.0-alpha-community-nt-debug | Windows | Any | Information schema has no indexes |
52086 | 2010-03-16 12:03 | 2011-02-16 23:44 | MySQL Server: Information schema | Duplicate (5442 days) | S3 | 5.1.44 | Windows (Server 2003) | Any | show function status |
19588 | 2006-05-06 23:47 | 2020-08-25 11:03 | MySQL Server: Information schema | Closed (6267 days) | S5 | 5.0, 5.1 | Any (all) | Any | INFORMATION_SCHEMA performs much too slow on large servers |
29263 | 2007-06-21 9:46 | 2011-02-16 23:43 | MySQL Server: Information schema | Closed (5853 days) | S3 | 5.1 | Any | Any | disabled storage engines omitted in SHOW ENGINES |
47961 | 2009-10-09 21:51 | 2011-02-16 23:44 | MySQL Server: Information schema | Verified (5600 days) | S3 | 5.1.39-community,5.5+ | Linux (only tested on CentOS 5.3) | Any | metadata leak from information_schema.routines via privs on mysql.proc table |
51208 | 2010-02-16 14:29 | 2018-04-12 9:57 | MySQL Server: Information schema | Closed (5193 days) | S3 | 5.1 | Any | Any | Extra string allocation from thd->mem_root in sql_show.cc, find_files() |
77861 | 2015-07-28 17:30 | 2015-07-29 6:58 | MySQL Server: Information schema | Verified (3481 days) | S3 | 5.6, 5.6.26 | Any | Any | "SHOW PROCESSLIST" needs higher resolution time |
98750 | 2020-02-26 20:11 | 2020-05-21 12:09 | MySQL Server: Information schema | Closed (1724 days) | S5 | 8.0, 8.0.19 | Any | Any | SHOW FIELDS command regression on MySQL 8.0 |
117049 | 2024-12-26 13:59 | 2024-12-30 14:09 | MySQL Server: Information schema | Verified (39 days) | S3 | 8.0.22 | Any | Any | if mysql upgrade failed in upgrade_system_schemas(), the rest process cannot be executed again |
98238 | 2020-01-15 12:26 | 2020-05-07 12:32 | MySQL Server: Information schema | Closed (1738 days) | S5 | 8 | Any | Any | I_S.KEY_COLUMN_USAGE is very slow |
116565 | 2024-11-06 3:38 | 2024-11-08 7:47 | MySQL Server: Information schema | Verified (91 days) | S5 | 8.0.40 | Any | Any | select I_S.innodb_tables is very slow for table with many partitions |
40367 | 2008-10-28 8:55 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified (5860 days) | S3 | 5.1.28, 5.1.29, 5.0, 5.1 bzr | Any | Any | SHOW on a broad view is taking too long |
84305 | 2016-12-22 1:22 | 2017-03-24 14:43 | MySQL Server: Information schema | Closed (2877 days) | S2 | 5.6.35 | Any | Any | The fix for Bug#78777 has different behavior with perf. schema vs. without it |
38918 | 2008-08-20 15:44 | 2008-11-13 3:29 | MySQL Server: Information schema | Closed (5930 days) | S3 | 5.1.26,6.0.6 | Any | Any | selecting from information_schema.columns is disproportionately slow |
41925 | 2009-01-07 15:43 | 2022-12-04 20:45 | MySQL Server: Information schema | Verified (5874 days) | S3 | 5.6.30, 5.7.12, 8.0.0 | Any | Any | Warning 1366 Incorrect string value: ... for column processlist.info |
43818 | 2009-03-24 4:05 | 2011-02-27 3:11 | MySQL Server: Information schema | Closed (5094 days) | S5 | 5.1.32 | Any (MS Windows, Linux) | Any | LOJ on I_S too slow |
32837 | 2007-11-29 5:33 | 2007-11-29 12:00 | MySQL Server: Information schema | Duplicate (6280 days) | S5 | 5.0.50 | Windows (Vista) | Any | I_S Querys take too long |
80301 | 2016-02-08 11:23 | 2016-02-19 16:50 | MySQL Server: InnoDB storage engine | Closed (3278 days) | S3 | Any | Any | leaksanitizer detects memory leaks in tde tests | |
80772 | 2016-03-17 1:34 | 2016-06-18 21:36 | MySQL Server: InnoDB storage engine | Closed (3180 days) | S2 | 5.7.8+,8.0.0, 5.7.11, 5.7.13 | Any | Any | Excessive memory used in memory/innodb/os0file starting 5.7.8 |
105028 | 2021-09-24 4:45 | 2021-09-24 5:29 | MySQL Server: InnoDB storage engine | Verified (1232 days) | S3 | 8.0.26 | Any | Any | memory leak caused by recv_sys->saved_recs during recovery |
114829 | 2024-04-30 21:15 | 2024-06-06 9:21 | MySQL Server: InnoDB storage engine | Verified (280 days) | S3 | 8.0 | Any | Any | Scoped_heap incorrect usage may have memory leak |
15653 | 2005-12-10 11:24 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5348 days) | S2 | 4.1, 5.0 | Any (All) | Any | Slow inserts to InnoDB if many thousands of .ibd files |
21112 | 2006-07-18 12:47 | 2006-09-13 17:57 | MySQL Server: InnoDB storage engine | Closed (6722 days) | S3 | 5.0 | Any (All) | Any | InnoDB slow with > 100,000 .ibd files |
25956 | 2007-01-30 21:57 | 2007-02-05 14:30 | MySQL Server: InnoDB storage engine | Closed (6577 days) | S3 | 5.0.27-community-nt | Windows (Win 2000 SP 4) | Any | Create Table with Multiple keys are not created |
39939 | 2008-10-08 18:38 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5347 days) | S2 | 5.x | Any | Any | DROP TABLE/DISCARD TABLESPACE takes long time in buf_LRU_invalidate_tablespace() |
45559 | 2009-06-17 15:59 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Duplicate (5712 days) | S3 | 5.1.32, 5.1.35 | Any | Any | InnoDB Query not using indexes properly? |
54728 | 2010-06-23 9:50 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5281 days) | S3 | 3.23, 4.0, 4.1, 5.0, 5.1, 5.5 | Any | Any | Unnecessary overhead in the 64-bit "dulint" struct type |
58234 | 2010-11-16 16:26 | 2014-02-26 12:47 | MySQL Server: InnoDB storage engine | Verified (4800 days) | S5 | 5.1.49-r1, 5.5.20 | Any | Any | LENGTH() / OCTET_LENGTH() on BLOB field very slow |
59683 | 2011-01-23 21:58 | 2012-02-13 3:40 | MySQL Server: InnoDB storage engine | Closed (4743 days) | S3 | 5.5+ | Any | Any | InnoDB latch deadlock detector/violation debug code is very slow |
67175 | 2012-10-10 9:08 | 2013-01-14 17:18 | MySQL Server: InnoDB storage engine | Duplicate (4407 days) | S3 | 5.6.7 | Any | Any | recovery is very very slow in buf_flush_single_page_from_LRU |
68725 | 2013-03-20 8:30 | 2016-03-24 11:28 | MySQL Server: InnoDB storage engine | Verified (3242 days) | S5 | all | Any | Any | UNIV_MEM_DEBUG needlessly slow, especially with UNIV_ZIP_DEBUG |
74472 | 2014-10-21 6:45 | 2015-04-29 12:33 | MySQL Server: InnoDB storage engine | Closed (3572 days) | S5 | 5.7.5 | Any | Any | ddl like add index is very slow in 5.7.5 |
76182 | 2015-03-05 21:42 | 2015-06-04 18:34 | MySQL Server: InnoDB storage engine | Closed (3538 days) | S2 | 5.7.6, 5.7.7 | Linux | Any | The new created tablespace is not reported in the INFORMATION_SCHEMA |
76750 | 2015-04-20 8:34 | 2018-02-12 15:46 | MySQL Server: InnoDB storage engine | Verified | S3 | 5.5.44 | Any | Any | innodb History list length (trx_rseg_history_len) never reaches 0 |
93530 | 2018-12-08 20:23 | 2020-12-06 17:24 | MySQL Server: InnoDB storage engine | Duplicate (1527 days) | S3 | 5.7.23, 5.7.24 | Any | Any | ALTER TABLE DROP INDEX is very slow |
99717 | 2020-05-28 7:47 | 2024-01-08 10:38 | MySQL Server: InnoDB storage engine | Verified (1403 days) | S5 | 8.0 | Any | Any | Peformance regression of parallel count |
100966 | 2020-09-27 3:46 | 2020-11-16 15:35 | MySQL Server: InnoDB storage engine | Closed (1544 days) | S2 | MySQL8.0.18, 8.0.21 | Any (rhel-7.4) | Any (intel x86) | select count(*) works very slow for uncommitted data |
104619 | 2021-08-13 14:45 | 2022-09-01 5:55 | MySQL Server: InnoDB storage engine | Verified (1271 days) | S3 | 8.0 | Any | Any | long MVCC snapshots will cause commit stalls via GTID persistor periodic compres |
104659 | 2021-08-18 22:19 | 2023-06-26 20:04 | MySQL Server: InnoDB storage engine | Verified (592 days) | S2 | 8.0.26, 5.7.35 | Any | Any | Select * reporting less rows_examined than only fields in an index. |
106604 | 2022-03-01 3:43 | 2022-03-01 8:01 | MySQL Server: InnoDB storage engine | Verified (1074 days) | S5 | 5.7.37 | Linux | Any | Contribution by Tencent Cloud-Native Database team: Purge suspend forever |
108586 | 2022-09-23 7:51 | 2023-03-19 16:53 | MySQL Server: InnoDB storage engine | Verified (865 days) | S3 | 8.0.30 | Linux (below 3.15) | Any | Contribution By Tencent: WL#12527 cause slow startup in Linux < 3.15 |
112964 | 2023-11-04 1:54 | 2024-09-27 9:44 | MySQL Server: InnoDB storage engine | Verified (459 days) | S5 | 8.0, 8.0.35 | Any | Any | SELECT COUNT is slow with O_DIRECT |
113482 | 2023-12-21 9:23 | 2024-06-24 20:52 | MySQL Server: InnoDB storage engine | Closed (228 days) | S5 | 8.0.35, 8.2.0 | Any | Any | innodb_parallel_read_threads>1 makes simple select count more expensive |
15815 | 2005-12-16 23:18 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5347 days) | S2 | 4.0.27,4.1, 5.0, 5.1 | Linux (Linux x86_64) | Any | Very poor performance with multiple queries running concurrently |
24386 | 2006-11-17 10:53 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5347 days) | S2 | 5.0, 5.1 | Any (all) | Any | Performance degradation caused by instrumentation in mutex_struct |
42101 | 2009-01-14 9:27 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5346 days) | S3 | 5.1 | Any | Any | Race condition in innodb_commit_concurrency |
53204 | 2010-04-27 14:17 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5281 days) | S3 | 5.1+ | Windows | Any | os_fastmutex_trylock is implemented incorrectly on Windows |
55716 | 2010-08-03 15:02 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5229 days) | S5 | Any | Any | CHECK TABLES should not perform check on entire adaptive hash index | |
56933 | 2010-09-22 13:26 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5174 days) | S2 | 5.5 | Any | Any | InnoDB does more writes in 5.5 than in 5.1 on buffer pool challenged workloads |
58912 | 2010-12-14 9:15 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5141 days) | S3 | all | Any | Any | InnoDB unnecessarily avoids update-in-place on column prefix indexes |
58974 | 2010-12-16 13:43 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5133 days) | S5 | mysql-5.5-innodb | Any | Any | ha_innobase:info() tries to lock some latches even if HA_STATUS_NO_LOCK is given |
60128 | 2011-02-15 7:22 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | Patch queued (5106 days) | S3 | Any | Any | Add performance schema instrumentation on os_fast_mutex | |
61735 | 2011-07-04 11:30 | 2011-07-08 6:02 | MySQL Server: InnoDB storage engine | Verified (4963 days) | S3 | 5.1, etc | Any | Any | index->lock held while preads are done |
65359 | 2012-05-18 12:41 | 2012-05-30 17:01 | MySQL Server: InnoDB storage engine | Duplicate (4636 days) | S2 | 5.1.62 | Linux | Any | bad select performance |
68171 | 2013-01-24 15:33 | 2013-07-08 13:18 | MySQL Server: InnoDB storage engine | Closed (4232 days) | S3 | 5.6.9-rc | Any | Any | Improve documentation of how InnoDB tables can be copied between instances |
68544 | 2013-03-01 19:52 | 2013-03-02 14:36 | MySQL Server: InnoDB storage engine | Verified (4360 days) | S3 | 5.5 | Any | Any | Ability to support multiple buffer pools with per-table assignment |
68574 | 2013-03-05 13:42 | 2021-08-13 10:40 | MySQL Server: InnoDB storage engine | Closed (1274 days) | S3 | 5.5.30, 5.6.16 | Windows (win7 sp1 ent) | Any | No instrumentation for InnoDB files in P_S on windows |
68588 | 2013-03-06 22:00 | 2019-08-27 15:11 | MySQL Server: InnoDB storage engine | Closed (4309 days) | S5 | 5.6.10 | Any | Any | remove most calls to os_thread_sleep from innodb |
69179 | 2013-05-09 4:22 | 2013-09-23 15:08 | MySQL Server: InnoDB storage engine | Duplicate (4155 days) | S2 | 5.6.11, 5.5.31, 5.6.13 | Any | Any | accessing information_schema.partitions causes plans to change |
69236 | 2013-05-14 22:12 | 2016-03-31 12:22 | MySQL Server: InnoDB storage engine | Verified (3447 days) | S5 | 5.6.11 | Any | Any | performance regressions for single-threaded workloads, part 2 |
69422 | 2013-06-07 9:18 | 2014-02-03 11:41 | MySQL Server: InnoDB storage engine | Closed (4071 days) | S5 | 5.6.12 | Any | Any | small performance impact with heap block debugging info in release builds |
71014 | 2013-11-26 14:25 | 2014-05-31 13:52 | MySQL Server: InnoDB storage engine | Closed (3965 days) | S3 | All Version | Any | Any | two many times of memset decreate the performance under heavy insert |
72123 | 2014-03-25 14:12 | 2017-10-04 3:52 | MySQL Server: InnoDB storage engine | Verified (3970 days) | S3 | 5.6, 5.6.18 | Any | Any | Spurious lock_wait_timeout_thread wakeup in lock_wait_suspend_thread() |
72948 | 2014-06-11 3:44 | 2018-07-30 17:32 | MySQL Server: InnoDB storage engine | Closed (2384 days) | S3 | 5.6 | Any | Any | lock_table can be optimized if updating the same table concurrently |
74280 | 2014-10-08 16:41 | 2014-10-10 13:50 | MySQL Server: InnoDB storage engine | Verified (3773 days) | S5 | 5.7.5 | Any | Any | covering secondary scans worse than PK scan at high concurrency |
74283 | 2014-10-08 17:00 | 2020-11-23 7:43 | MySQL Server: InnoDB storage engine | Verified (2811 days) | S5 | 5.7.5 | Any | Any | Non-covering secondary index scans degrade more in 5.7 than 5.6 |
74325 | 2014-10-10 19:26 | 2015-05-22 13:02 | MySQL Server: InnoDB storage engine | Closed (3549 days) | S5 | 5.7.5 | Any | Any | updates to indexed column much slower in 5.7.5 |
74408 | 2014-10-15 19:52 | 2018-07-04 15:16 | MySQL Server: InnoDB storage engine | Verified (2410 days) | S5 | 5.6, 5.7, 8.0 | Any | Any | srv_conc_enter_innodb() is not optimal |
74832 | 2014-11-13 5:54 | 2017-10-01 13:59 | MySQL Server: InnoDB storage engine | Closed (3321 days) | S3 | 5.7.7 | Any | Any | ut_delay missing compiler barrier, UT_RELAX_CPU isn't at all relaxing |
75981 | 2015-02-20 13:56 | 2017-11-05 7:12 | MySQL Server: InnoDB storage engine | Verified (3592 days) | S5 | 5.7.6 | Any | Any | MySQL 5.7.5 30% slower than 5.6.23 for 1 thread write |
77094 | 2015-05-19 13:13 | 2018-10-09 14:11 | MySQL Server: InnoDB storage engine | Closed (3090 days) | S3 | 5.7.7 | Any | Any | Reduce log_sys->mutex contention by allowing concurrent mtr commit and log write |
83528 | 2016-10-25 13:06 | 2016-12-02 14:58 | MySQL Server: InnoDB storage engine | Duplicate (2989 days) | S3 | 8.0 | Any | Any | InnoDB mutex bs: periodic waiters wakeup |
83568 | 2016-10-27 9:54 | 2018-02-23 0:44 | MySQL Server: InnoDB storage engine | Verified (2993 days) | S5 | 8.0 | Any | ARM | InnoDB memory barriers bs |
85304 | 2017-03-04 8:26 | 2017-09-02 12:52 | MySQL Server: InnoDB storage engine | Verified (2715 days) | S3 | 5.7 | Any | Any | Reduce mutex contention of fil_system->mutex |
85999 | 2017-04-19 9:14 | 2017-04-19 9:56 | MySQL Server: InnoDB storage engine | Verified (2851 days) | S5 | 5.7.17 | Any | Any | Optimize zlib 's fill_window with SIMD instructions |
87827 | 2017-09-21 14:09 | 2023-11-02 6:39 | MySQL Server: InnoDB storage engine | Closed (2576 days) | S5 | 8.0.3 | Any | Any | Performance regression in "create table" speed and scalability in 8.0.3 |
87933 | 2017-10-02 4:06 | 2018-12-12 21:04 | MySQL Server: InnoDB storage engine | Verified (2249 days) | S2 | 5.7.19 | CentOS | ARM | Scalibility issue on Arm platform with the current UT_RELAX_CPU () code. |
88422 | 2017-11-09 12:20 | 2024-11-28 16:41 | MySQL Server: InnoDB storage engine | Verified (2642 days) | S2 | 5.7.19 | Any | Any | MySQL 5.7 innodb purge thread get oldest readview could block other transaction |
89551 | 2018-02-06 9:27 | 2020-02-12 14:10 | MySQL Server: InnoDB storage engine | Verified (2558 days) | S3 | 5.7.21, 8.0.4 | Any | Any | Spatial index query time performance scales linearly |
91837 | 2018-07-31 4:35 | 2018-07-31 12:43 | MySQL Server: InnoDB storage engine | Verified (2383 days) | S3 | 8.0.11, 8.0.12, 5.7.23 | Any | Any | IS.innodb_trx results filtered by trx_started depends on timezone |
94370 | 2019-02-18 3:19 | 2019-02-27 10:16 | MySQL Server: InnoDB storage engine | Verified (2181 days) | S3 | 8.0 | Any | Any | Performance regression of btr_cur_prefetch_siblings |
95390 | 2019-05-16 9:57 | 2019-05-16 13:53 | MySQL Server: InnoDB storage engine | Verified (2094 days) | S5 | 8.0.16 | Any | Any | wake up log_closer background thread in log_wait_for_space_in_log_recent_closed |
95491 | 2019-05-23 11:23 | 2019-06-05 11:48 | MySQL Server: InnoDB storage engine | Verified (2077 days) | S5 | ALL | Any | Any | The unused wake up in simulator AIO of function reserve_slot |
99432 | 2020-05-04 8:09 | 2020-05-05 12:04 | MySQL Server: InnoDB storage engine | Verified (1740 days) | S5 | 8.0.20 | Any | ARM | Improving memory barrier during rseg allocation |
100811 | 2020-09-11 9:22 | 2020-09-11 13:25 | MySQL Server: InnoDB storage engine | Duplicate (1610 days) | S5 | 8.0.20 | Oracle Linux | Any | performance degradation in MySQL-8.0 vs MySQL-5.7 in simple DML operations. |
105926 | 2021-12-17 8:41 | 2021-12-17 10:53 | MySQL Server: InnoDB storage engine | Duplicate (1148 days) | S5 | 8.0.18 | Any | Any | Query information_schema.processlist has performance impact on normal queries |
107700 | 2022-06-29 11:18 | 2024-06-13 20:13 | MySQL Server: InnoDB storage engine | Closed (239 days) | S5 | 8.0.29 | Any | Any | Performance of Temptable is worse than Memory in GROUP BY scenario |
110600 | 2023-04-04 8:55 | 2023-04-04 9:28 | MySQL Server: InnoDB storage engine | Verified (675 days) | S5 | 8.0.32 | Any | Any | optimize for page flush |
110606 | 2023-04-04 10:16 | 2023-04-17 8:24 | MySQL Server: InnoDB storage engine | Verified (662 days) | S5 | 8.0 | Linux | ARM (aarch64) | Improve crc32c code for arm64 |
111353 | 2023-06-11 22:04 | 2024-11-12 15:27 | MySQL Server: InnoDB storage engine | Verified (605 days) | S2 | 8.0, 8.0.33 | Any | Any | 3x Performance Regression from 5.7 to 8.0 on ALTER TABLE FORCE. |
114468 | 2024-03-24 21:51 | 2024-04-10 8:34 | MySQL Server: InnoDB storage engine | Verified (319 days) | S5 | 8.3.0, 8.0.36 | Any | Any | Inconsistent table performance: fresh data import vs after optimization |
115107 | 2024-05-23 18:54 | 2024-10-17 10:42 | MySQL Server: InnoDB storage engine | Verified (113 days) | S5 | 5.7, 8.0 | Any | Any | Optimization in row_purge_poss_sec Function for Undo Purge Process |
115399 | 2024-06-21 3:40 | 2024-10-30 1:35 | MySQL Server: InnoDB storage engine | Closed (100 days) | S5 | 8.x, 8.0.37, 8.4.0 | Any | Any | performance deterioration caused by incorrect cpu usage statistics |
116005 | 2024-09-04 23:43 | 2024-09-12 1:20 | MySQL Server: InnoDB storage engine | Verified (154 days) | S5 | all versions | Any | Any | With NUMA and Read Committed, performance worsens under high concurrency. |
116463 | 2024-10-23 20:38 | 2024-10-24 12:29 | MySQL Server: InnoDB storage engine | Verified (106 days) | S5 | 8.0 | Any | Any | behavior related to innodb_spin_wait_delay changed in 8.0.30 |
68814 | 2013-03-29 15:33 | 2015-04-23 6:14 | MySQL Server: InnoDB storage engine | Verified (3578 days) | S3 | 5.6.10 | Any (Centos 6.3) | Any | MySQL optimizer consider few rows to examine but it is not really obvious why |
71507 | 2014-01-29 12:51 | 2024-05-30 12:20 | MySQL Server: InnoDB storage engine | Verified | S5 | 5.7 | Any | Any | innodb is excessively slow to replace duplicate values in a table |
78262 | 2015-08-28 15:19 | 2015-12-07 18:51 | MySQL Server: InnoDB storage engine | Closed (3350 days) | S5 | 5.6.26 | Any (CentOS release 6.6) | Any | Adding indexes on empty table is slow with large innodb_sort_buffer_size. |
93734 | 2018-12-24 18:44 | 2024-01-29 11:07 | MySQL Server: InnoDB storage engine | Closed (459 days) | S5 | Ubuntu (18.04) | x86 | MySQL 8.0 is 36 times slower than MySQL 5.7 | |
112137 | 2023-08-22 13:48 | 2024-07-03 10:38 | MySQL Server: InnoDB storage engine | Closed (330 days) | S5 | 8.0.33, 8.0.34 | Any | Any | parallel read is slow when innodb_use_native_aio = off |
114154 | 2024-02-28 9:57 | 2024-07-02 19:29 | MySQL Server: InnoDB storage engine | Closed (238 days) | S5 | 8.0.36 | Any | Any | Parallel read is slow after parition table is read in parallel |
98132 | 2020-01-06 10:55 | 2022-01-04 12:51 | MySQL Server: InnoDB storage engine | Verified (1858 days) | S2 | 5.6, 5.7, 8.0, 5.7.28, 8.0.18 | Any | Any | Analyze table leads to empty statistics during online rebuild DDL |
103213 | 2021-04-06 5:13 | 2024-01-08 10:39 | MySQL Server: InnoDB storage engine | Duplicate (1403 days) | S5 | 8.0.17 - 8.0.23 | Any | Any | Poor performance while executing 'select count(*)' on a table |
107473 | 2022-06-03 3:34 | 2022-08-24 7:29 | MySQL Server: InnoDB storage engine | Verified (898 days) | S3 | 8.0.23, 8.0.29 | CentOS | Any | Updating BLOB column slows down purge and causes high trx_rseg_history_len |
113505 | 2023-12-24 18:23 | 2024-09-18 0:14 | MySQL Server: InnoDB storage engine | Closed (142 days) | S5 | 8.0.35 | Any | Any | Performance schema counter increments make parallel index create slow |
5436 | 2004-09-06 19:10 | 2005-05-06 8:58 | MySQL Server: InnoDB storage engine | Closed (7217 days) | S3 | all | Any (all) | Any | SHOW INNODB STATUS is unusable with a lot of concurrent connections |
12125 | 2005-07-22 22:59 | 2005-07-26 21:40 | MySQL Server: InnoDB storage engine | Closed (7136 days) | S1 | 4.1.13 | MacOS (OS X 10.4.2) | Any | Massive Disk I/O Degradation under 4.1.13 in OS X |
20113 | 2006-05-28 15:51 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6827 days) | S5 | 5.0.21 | Linux (Fedora Core5) | Any | Performance degredation on 8 way system ( 4x Opteron 875's ) |
36941 | 2008-05-25 11:58 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5346 days) | S3 | 5.0-bk, 5.1-bk | Any | Any | Performance problem in ha_print_info (SHOW INNODB STATUS) |
36942 | 2008-05-25 12:28 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5346 days) | S3 | 5.0,5.1 | Any | Any | Performance problem in lock_get_n_rec_locks (SHOW INNODB STATUS) |
54914 | 2010-06-30 13:08 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5218 days) | S5 | 5.5.5 | Any | Any | InnoDB: performance drop with innodb_change_buffering=all |
59163 | 2010-12-24 17:20 | 2012-01-05 0:37 | MySQL Server: InnoDB storage engine | Closed (4782 days) | S2 | 5.5.8 | Any | Any | Single user session performance in InnoDB |
66587 | 2012-08-28 23:04 | 2013-05-23 16:55 | MySQL Server: InnoDB storage engine | Closed (4278 days) | S3 | 5.6.7 | Any | Any | Behavior of read-only transactions differs from documentation |
69029 | 2013-04-22 3:04 | 2013-04-25 4:55 | MySQL Server: InnoDB storage engine | Closed (4306 days) | S5 | 5.6.12 | Any | Any | Arbitrary flushing performance limitation is bad |
72703 | 2014-05-21 6:46 | 2014-08-06 14:57 | MySQL Server: InnoDB storage engine | Closed (3844 days) | S3 | Any | Any | page cleaner should be multi-threaded also for recovery and shutdown | |
73763 | 2014-08-28 21:47 | 2016-10-26 15:20 | MySQL Server: InnoDB storage engine | In progress (3026 days) | S5 | 5.7 | Any | Any | New futex-mutex in InnoDB needs perf attention |
76627 | 2015-04-09 3:44 | 2018-12-03 3:24 | MySQL Server: InnoDB storage engine | Closed (3546 days) | S5 | 5.5.24, 5.6.24 | Linux (CentOS6.5) | Any | MySQL/InnoDB mix buffered and direct IO |
76728 | 2015-04-17 4:48 | 2016-06-07 8:56 | MySQL Server: InnoDB storage engine | Closed (3171 days) | S3 | 5.7.7 | Any | Any | reduce lock_sys->mutex contention for transaction that only contains SELECT |
77092 | 2015-05-19 12:16 | 2016-02-04 18:41 | MySQL Server: InnoDB storage engine | Closed (3530 days) | S3 | 5.7.6 | Any | Any | Document potential benefits of InnoDB General Tablespaces |
80979 | 2016-04-06 14:25 | 2022-01-17 9:31 | MySQL Server: InnoDB storage engine | Verified (3228 days) | S3 | 5.7 | Any | Any | Doublewrite buffer event waits should be annotated for Performance Schema |
82524 | 2016-08-10 8:36 | 2016-08-25 8:22 | MySQL Server: InnoDB storage engine | Verified (3088 days) | S5 | 5.6, 5.6.32, 5.7.14 | Ubuntu (16.04) | Any | Significant innodb load performance regression since version 5.5 |
90604 | 2018-04-24 13:50 | 2018-04-25 4:41 | MySQL Server: InnoDB storage engine | Verified (2480 days) | S5 | 5.7 | CentOS | Any | ut_rnd_ulint_counter () : Default delay for spin wait gives better performance |
91485 | 2018-06-29 6:32 | 2018-07-20 17:10 | MySQL Server: InnoDB storage engine | Closed (2394 days) | S5 | 5.7.22, 8.0.11 | Any | Any | ut_crc32_hw() checks ut_crc32_cpu_enabled on each call |
95934 | 2019-06-23 17:13 | 2019-07-05 8:17 | MySQL Server: InnoDB storage engine | Analyzing (2044 days) | S5 | 8.0.* | Any | Any | innodb_flush_log_at_trx_commit = 0 get performance regression on 8 core machine |
96071 | 2019-07-02 10:43 | 2022-07-19 13:12 | MySQL Server: InnoDB storage engine | Verified (1703 days) | S3 | 8.0.16 | Any | Any | TempTable engine uses much more memory than MEMORY engine for temporary table |
96504 | 2019-08-12 4:42 | 2019-08-12 18:21 | MySQL Server: InnoDB storage engine | Verified (2006 days) | S5 | 8.0 | Any | ARM | Refine atomics and barriers for weak memory order platform |
98546 | 2020-02-11 6:38 | 2020-02-12 15:20 | MySQL Server: InnoDB storage engine | Verified (1822 days) | S5 | 8, 5.7 | Any | Any | Transient indexes statistics are updated in foreground causing performance issue |
99118 | 2020-03-31 5:20 | 2020-11-04 15:43 | MySQL Server: InnoDB storage engine | Closed (1556 days) | S5 | 8.0.19 | Linux | ARM | ARM CRC32 intrinsic call to accelerate table-checksum (not crc32c but crc32) |
99593 | 2020-05-15 16:05 | 2024-05-28 3:21 | MySQL Server: InnoDB storage engine | Closed (1719 days) | S5 | 8.0.20 | Ubuntu (20.04) | Any | Performance issues in 8.0.20 |
99966 | 2020-06-24 8:12 | 2020-06-30 12:45 | MySQL Server: InnoDB storage engine | Verified (1683 days) | S5 | 8.0.20 | Any | ARM | Switching to use NUMA-SMART Counter for statistical counters |
100182 | 2020-07-10 13:35 | 2020-07-13 12:40 | MySQL Server: InnoDB storage engine | Verified (1673 days) | S5 | 8.0.20 | Any | ARM | Improving performance of 'row_mysql_store_col_in_innobase_format' |
102289 | 2021-01-19 6:06 | 2021-01-20 13:32 | MySQL Server: InnoDB storage engine | Verified (1479 days) | S5 | 5.7, 8.0 | Any | Any | buf_flush_or_remove_pages causes large tps fluctuation with write-heavy workload |
104779 | 2021-08-31 9:38 | 2021-08-31 10:02 | MySQL Server: InnoDB storage engine | Verified (1256 days) | S5 | 8.0.19 | Any | Any | no need to own sx-latch during the period of page flusing for BUF_FLUSH_LRU |
104967 | 2021-09-17 10:04 | 2021-11-19 19:40 | MySQL Server: InnoDB storage engine | Closed (1176 days) | S5 | 8.0.26 | Any | Any | The fuction buf_validate() affects performance seriously and can be optimized |
109417 | 2022-12-16 23:30 | 2022-12-17 15:30 | MySQL Server: InnoDB storage engine | Verified (783 days) | S5 | 8.0.31 | Any | Any | Bad performance by call btr_drop_ahi_for_table within dict sys_mutex protection |
110644 | 2023-04-10 6:16 | 2023-04-13 9:56 | MySQL Server: InnoDB storage engine | Verified (666 days) | S5 | 8.0 | Linux | ARM (aarch64) | innobase: optimize hash_uint64 with hardware crc on Arm |
113178 | 2023-11-22 9:09 | 2024-02-19 11:23 | MySQL Server: InnoDB storage engine | Closed (360 days) | S5 | 8.0, 8.0.35 | Any | Any | Temptable engine leads to performance degradation |
116198 | 2024-09-23 10:51 | 2024-09-30 8:57 | MySQL Server: InnoDB storage engine | Verified (132 days) | S5 | 8.0 | Any | Any | Addressing the compatibility issues of the CATS algorithm in NUMA scenarios. |
116531 | 2024-11-01 17:02 | 2024-11-05 13:26 | MySQL Server: InnoDB storage engine | Verified (95 days) | S5 | 8.0 | Linux | x86 | Performance regressions from the diff that adds instant add and drop column |
18252 | 2006-03-15 10:36 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5347 days) | S2 | 5.0.3 and later | Any (all) | Any | Disk space leak in updates of InnoDB BLOB rows in 5.0 and 5.1 |
36613 | 2008-05-09 5:33 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (6100 days) | S2 | 5.1.24 | Any | Any | Creating many tables with many columns in innodb leads to out of memory |
45992 | 2009-07-07 8:15 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5346 days) | S3 | 5.4.2-debug | Linux (32-bit fc8) | Any | innodb memory not freed after shutdown |
54764 | 2010-06-24 8:19 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5260 days) | S3 | 5.5.5, innodb 1.1.1 | Any | Any | memory allocated in os_aio_array_create is not freed at shutdown |
115328 | 2024-06-14 2:13 | 2024-07-06 14:02 | MySQL Server: InnoDB storage engine | Analyzing (234 days) | S5 | 8.4.0 | Red Hat (Rocky Linux 8.8) | x86 | Poor write performance due to new default value of innodb_doublewrite_pages |
86705 | 2017-06-15 2:25 | 2018-08-30 11:04 | MySQL Server: InnoDB storage engine | Verified (2787 days) | S2 | 5.5.45, 5.5.56 | Linux (MySQL OOM because of memory leak) | Any | Memory leak of Innodb |
108430 | 2022-09-08 13:52 | 2023-01-16 3:10 | MySQL Server: InnoDB storage engine | Verified (787 days) | S5 | 8.0.29 | Oracle Linux (Oracle Linux Server release 7.9 3.10.0-1160.76.1.0.1.el7.x86_64) | x86 ( Intel(R) Xeon(R) CPU E5-2630 v3 ) | performance degradation of DML operations comparing with MySQL 5.7 |
18054 | 2006-03-08 2:04 | 2007-01-16 16:08 | MySQL Server: InnoDB storage engine | Closed (6597 days) | S1 | 5.0.18 | Miracle Linux ver4 (kernel 2.6) | Any | Severe performance degradation when Hyperthreading is on |
103743 | 2021-05-19 21:07 | 2022-01-03 6:51 | MySQL Server: InnoDB storage engine | Closed (1131 days) | S2 | 8.0.18, 8.0.25 | CentOS | x86 | slow mysql8 start with lots of _encrypted_ tables |
109539 | 2023-01-05 6:09 | 2024-05-20 10:00 | MySQL Server: InnoDB storage engine | Closed (329 days) | S5 | 8.0 | Any | Any | Performance of scanning data_lock_waits worse than expected with read-only trx |
95933 | 2019-06-23 16:06 | 2024-08-23 11:05 | MySQL Server: InnoDB storage engine | Closed (168 days) | S2 | 8.0.16 | Any | x86 | Performance regression of MySQL8.0 on 8 core environment |
93165 | 2018-11-12 15:11 | 2018-11-26 21:02 | MySQL Server: InnoDB storage engine | Verified (2265 days) | S3 | 5.7.23, 5.7.24 | Any | Any | Memory leak in sync_latch_meta_init() after mysqld shutdown detected by ASan |
7150 | 2004-12-10 0:18 | 2005-01-14 13:52 | MySQL Server: InnoDB storage engine | Closed (7329 days) | S3 | 4.1 | Linux (Linux) | Any | InnoDB TRUNCATE can get very slow |
103034 | 2021-03-18 9:29 | 2021-03-18 13:35 | MySQL Server: InnoDB storage engine | Verified (1422 days) | S5 | 8.0 | Any | Any | new undo log purge strategy purge record too slow on single table |
83532 | 2016-10-25 14:11 | 2018-02-18 18:29 | MySQL Server: InnoDB storage engine | Verified (2993 days) | S3 | 8.0 | Any | ARM | InnoDB mutex bs: memory barriers |
90209 | 2018-03-24 21:19 | 2023-11-06 11:33 | MySQL Server: InnoDB storage engine | Verified (1991 days) | S5 | 8.0, 8.0.17 | Any | Any | Performance regression with > 15K tables in MySQL 8.0 (with general tablespaces) |
99638 | 2020-05-20 0:53 | 2020-12-04 12:54 | MySQL Server: InnoDB storage engine | Closed (1527 days) | S5 | 8.0.18 | Any | Any | xa transaction with low performance |
100537 | 2020-08-15 8:11 | 2024-09-19 9:44 | MySQL Server: InnoDB storage engine | Closed (141 days) | S5 | 8.0.21 | Ubuntu (18.04 LTS) | x86 | Performance degradation caused by monitoring sys.innodb_lock_waits in MySQL 8.0 |
38153 | 2008-07-15 22:13 | 2014-02-28 18:58 | MySQL Server: InnoDB storage engine | Verified (3997 days) | S5 | 5.0.66, 5.1.34, 5.6.16 | Any | Any | mysql-bench: slowdown for update_of_primary_key_many_keys test |
55681 | 2010-08-02 10:43 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5169 days) | S2 | trunk | Any | Any | MTR slowdown after default storage engine was changed to InnoDB |
68077 | 2013-01-14 3:37 | 2013-04-03 11:33 | MySQL Server: InnoDB storage engine | Closed (4328 days) | S5 | 5.6 | Any | Any | Mixing 4K/16K blocks increases 8K free blocks and holds buf pool mutex longer |
87621 | 2017-08-31 9:45 | 2017-09-28 9:11 | MySQL Server: InnoDB storage engine | Verified (2713 days) | S3 | 5.6.37, 5.7.19 | Any | Any | Huge InnoDB slowdown when selecting strings without indexes |
61188 | 2011-05-16 16:43 | 2011-11-02 16:32 | MySQL Server: InnoDB storage engine | Closed (4846 days) | S3 | 5.5.12-log | Linux (CentOS release 5.3 (Final)) | Any | DROP TABLE extremely slow |
95582 | 2019-05-31 5:02 | 2019-06-21 13:41 | MySQL Server: InnoDB storage engine | Verified (2058 days) | S3 | 8.0.16, 5.7.26 | Any | Any | DDL using bulk load is very slow under long flush_list |
101900 | 2020-12-08 3:21 | 2025-01-29 10:09 | MySQL Server: InnoDB storage engine | Verified (1522 days) | S2 | 8.0.21 | Linux (7.6) | Any | Add partition is slow |
97822 | 2019-11-27 23:58 | 2020-01-28 2:23 | MySQL Server: InnoDB storage engine | Closed (1837 days) | S5 | 5.7.28 | Linux (Centos7) | Any | buf_page_get_gen buf_pool->stat.n_page_gets++ is a cpu waste |
18384 | 2006-03-21 8:14 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5347 days) | S2 | 5.0.3 and later | Any (All) | Any | InnoDB memory leak on duplicate key errors in 5.0 if row has many columns |
57480 | 2010-10-15 11:19 | 2014-09-13 16:19 | MySQL Server: InnoDB storage engine | Closed (4782 days) | S2 | 5.1, 5.0 | Any | Any | Memory leak when having 256+ tables |
64987 | 2012-04-15 20:13 | 2014-08-15 20:09 | MySQL Server: InnoDB storage engine | Duplicate (4648 days) | S3 | 5.6.6 | Any | Any | Memory leak in mysql-5.6.6-labs-april-2012 |
91860 | 2018-08-01 20:51 | 2018-08-02 6:28 | MySQL Server: InnoDB storage engine | Duplicate (2381 days) | S2 | 5.7.22 | Any | Any | The buf_LRU_free_page function may leak some memory in a particular scenario |
111570 | 2023-06-26 20:03 | 2023-06-28 0:31 | MySQL Server: InnoDB storage engine | Verified (590 days) | S3 | 8.0.33, 5.7.42 | Any | Any | Looking for inexistent data reports 0 rows examined |
54563 | 2010-06-16 19:19 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5349 days) | S3 | 5.5.5pre | Any | Any | InnoDB: Performance drop in varios sysbench tests |
56332 | 2010-08-27 18:17 | 2013-07-07 11:39 | MySQL Server: InnoDB storage engine | Closed (4233 days) | S3 | 5.0.87, 5.0.91 | Any | Any | Performance regression in DROP TABLE performance post 5.0.77 |
57981 | 2010-11-04 14:57 | 2012-02-13 3:42 | MySQL Server: InnoDB storage engine | Closed (4743 days) | S3 | 5.5.7-m3 | Solaris | Any | UNIV_DEBUG causes big performance degradation for some operations on Solaris |
80737 | 2016-03-14 21:24 | 2016-03-17 0:14 | MySQL Server: InnoDB storage engine | Closed (3250 days) | S3 | 5.7 | Any | Any | "How MySQL Uses Memory" is myisam centric |
100512 | 2020-08-13 9:17 | 2023-03-03 14:14 | MySQL Server: InnoDB storage engine | Closed (997 days) | S5 | 5.7.31,8.0.21 | Linux (3.10.107) | x86 (96 cores) | adaptive hash index(AHI) building causing contention on btr_search_latches |
111594 | 2023-06-28 8:21 | 2024-11-07 14:48 | MySQL Server: InnoDB storage engine | Verified (506 days) | S3 | 8.0 | Any | Any | Some Scalability Issues in Specific Scenarios |
112767 | 2023-10-19 6:07 | 2024-04-17 22:38 | MySQL Server: InnoDB storage engine | Closed (357 days) | S5 | 8.0.34, 8.0.35 | Any | Any | SELECT COUNT(*) degraded performance on 8.0 compared to 5.7 |
81804 | 2016-06-10 12:35 | 2019-07-02 10:59 | MySQL Server: InnoDB storage engine | Verified (3161 days) | S2 | 5.7.13 | Any | Any | Memory leak or bug in P_S instrumentation for InnoDB threads |
1942 | 2003-11-25 1:13 | 2004-03-17 9:43 | MySQL Server: InnoDB storage engine | Closed (7632 days) | S2 | 4.0.16 | Linux (Linux) | Any | Slow queries with "order by" |
59143 | 2010-12-24 0:13 | 2017-05-14 20:45 | MySQL Server: InnoDB Plugin storage engine | Duplicate (5131 days) | S2 | 5.1.52, 5.5, 5.6 | Any | Any | valgrind leak warning from innodb_plugin.innodb-index for mysql 5.1.52 |
63276 | 2011-11-16 0:19 | 2013-07-30 14:25 | MySQL Server: InnoDB Plugin storage engine | Closed (4210 days) | S5 | 5.1.52, 5.1.60 | Any | Any | skip sleep in srv_master_thread when shutdown is in progress |
52102 | 2010-03-16 16:20 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5168 days) | S5 | 5.0, 5.1, 5.5.5m3 | Windows (Any) | Any | InnoDB Plugin shows performance drop compared to InnoDB (Windows) |
59214 | 2010-12-29 15:45 | 2011-05-05 23:48 | MySQL Server: InnoDB Plugin storage engine | Closed (5027 days) | S5 | 5.1,5.5 | Any | Any | increase rate limit for insert buffer prefetch reads |
61341 | 2011-05-28 15:37 | 2012-01-05 20:15 | MySQL Server: InnoDB Plugin storage engine | Closed (4782 days) | S5 | 5.1.52 | Any | Any | buf_LRU_insert_zip_clean can be O(N) on LRU length |
61456 | 2011-06-09 7:40 | 2012-10-18 22:40 | MySQL Server: InnoDB Plugin storage engine | Closed (4495 days) | S5 | 5.1.52 | Any | Any | Optimistic Insert/Update uses wrong heuristics for compressed page size |
65886 | 2012-07-12 19:24 | 2012-12-24 19:11 | MySQL Server: InnoDB Plugin storage engine | Closed (4428 days) | S5 | 5.1.52, 5.1.64 | Any | Any | is the call to ibuf_merge_or_delete_for_page from buf_page_get_gen redundant? |
70139 | 2013-08-23 16:03 | 2014-06-23 9:17 | MySQL Server: InnoDB Plugin storage engine | Closed (3882 days) | S5 | 5.1.72 | Windows | Any | Performance of "ALTER TABLE..." queries |
85819 | 2017-04-06 3:04 | 2018-02-18 18:29 | MySQL Server: InnoDB Plugin storage engine | Verified (2863 days) | S5 | 5.7 | Linux | ARM | Optimize AARCH64 CRC32c implementation |
35077 | 2008-03-05 12:13 | 2011-02-16 23:43 | MySQL Server: InnoDB Plugin storage engine | Closed (5347 days) | S3 | 5.1.42 | Any | Any | Very slow DROP TABLE (ALTER TABLE, OPTIMIZE TABLE) on compressed tables |
53572 | 2010-05-11 16:09 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5342 days) | S1 | 1.1.0 | Any | Any | slow shutdown does not wait for the purge thread to purge everything |
53654 | 2010-05-14 16:12 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5324 days) | S2 | 1.0, 1.1 | Any | Any | after 2nd shutdown innodb_file_format_check attains strange values |
64181 | 2012-01-31 14:41 | 2012-02-09 12:20 | MySQL Server: InnoDB Plugin storage engine | Verified (4752 days) | S5 | 5.1.52, 5.1.61 | Any | Any | unzip_LRU length management might need to be updated for SSD |
49169 | 2009-11-27 16:09 | 2013-02-28 13:27 | MySQL Server: InnoDB Plugin storage engine | Closed (4362 days) | S5 | 5.0,5.1,5.1 plugin | Any | Any | read_view_open_now is inefficient with many concurrent sessions |
52588 | 2010-04-05 2:45 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5329 days) | S2 | 5.5.4/iplugin1.1 | Any | Any | InnoDB: performance regression in sysbench OLTP_RW test |
52806 | 2010-04-14 6:32 | 2024-05-06 13:49 | MySQL Server: InnoDB Plugin storage engine | Closed (277 days) | S5 | 5.1 | Any | Any | Make InnoDB mutexes green |
68022 | 2013-01-03 18:00 | 2013-07-07 11:28 | MySQL Server: InnoDB Plugin storage engine | Closed (4233 days) | S1 | 5.1,5.5 | Any | Any | DROP TABLE slow when it decompress compressed-only pages |
53165 | 2010-04-26 15:15 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5308 days) | S3 | mysql-5.5 | Any | Any | Setting innodb_change_buffering=DEFAULT produces incorrect result |
53852 | 2010-05-20 11:14 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5175 days) | S3 | 5.1.47/plugin1.0.8 | Any | Any | InnoDB: Performance drop in SELECT_SUM_RANGES test at higher number of threads |
54538 | 2010-06-16 1:23 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5169 days) | S3 | 5.1.47 | Any | Any | use of exclusive innodb dictionary lock limits performance |
64340 | 2012-02-15 14:07 | 2013-06-14 15:35 | MySQL Server: InnoDB Plugin storage engine | Verified (4256 days) | S5 | 5.1.52, 5.1.61 | Any | Any | race on no_flush event during buf_flush_free_margin |
64673 | 2012-03-16 23:14 | 2012-03-18 17:15 | MySQL Server: InnoDB Plugin storage engine | Verified (4710 days) | S5 | 5.1 | Any | Any | InnoDB allocates too many empty pages in ibd files |
46656 | 2009-08-11 16:13 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5347 days) | S3 | 5.1 | Linux (64bit) | Any | InnoDB plugin: memory leaks (Valgrind) |
82210 | 2016-07-13 6:50 | 2016-11-19 1:57 | MySQL Server: JSON | Closed (3123 days) | S3 | 8.0.0 | Any | Any | JSON memory usage missing from the memory summary tables |
53045 | 2010-04-22 4:58 | 2022-12-04 20:45 | MySQL Server: Locking | Verified (5405 days) | S5 | 5.1.45, 5.5 | Any | Any | LOCK_thread_count locked when per connection threads created |
66473 | 2012-08-21 1:49 | 2016-08-04 0:38 | MySQL Server: Locking | Closed (4365 days) | S5 | 5.6.6-m9 | Any | Any | MySQL 5.6.6-m9 has more mutex contention than MySQL 5.1 |
58689 | 2010-12-03 6:02 | 2012-07-31 1:44 | MySQL Server: Locking | Closed (4574 days) | S3 | 5.0, 5.1, 5.6.1 | Any | Any | MyISAM Selects locks inserts inside procedure only |
52289 | 2010-03-23 2:04 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5321 days) | S2 | 5.5.3pre/5.5.4pre | Any | Any | performance regression for MyISAM in sysbench OLTP_RW test |
61401 | 2011-06-03 17:47 | 2011-06-16 19:49 | MySQL Server: Locking | Closed (4985 days) | S5 | MySQL 5.5.3+ | Any | Any | UPDATE performance degrades gradually if a trigger exists |
85191 | 2017-02-27 6:40 | 2017-02-28 12:30 | MySQL Server: Locking | Verified (2901 days) | S3 | 5.7, 5.7.17 | Any | Any | performance regression with HANDLER READ syntax |
48832 | 2009-11-17 11:00 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5404 days) | S5 | 5.0+ | Any | Any | Disconnection is slow when using non-persistent mysql connections |
106610 | 2022-03-01 10:32 | 2022-04-04 11:34 | MySQL Server: Locking | Verified (1040 days) | S2 | 5.7.33 | Linux | x86 | Concurrent INSERT IGNORE in InnoDB table may trigger the database to stall |
69030 | 2013-04-22 12:55 | 2013-04-24 11:23 | MySQL Server: Locking | Closed (4307 days) | S1 | 5.1.66 | Any | Any | Optimize table locks whole database |
53096 | 2010-04-23 7:32 | 2012-08-13 16:18 | MySQL Server: Locking | Closed (4561 days) | S5 | 5.1.44 | Any | Any | Disconnection is slow when using non-persistent mysql connections |
42930 | 2009-02-17 11:44 | 2012-10-05 16:42 | MySQL Server: Locking | Closed (4508 days) | S5 | 5.0, 5.1, 6.0 | Any | Any | 'show global status' causes lock contention on LOCK_thread_count |
27638 | 2007-04-04 7:28 | 2007-04-07 18:29 | MySQL Server: Logging | Closed (6516 days) | S3 | 5.1.18-bk | Any | Any | slow logging to CSV table inserts bad query_time and lock_time values |
30000 | 2007-07-24 8:11 | 2007-08-03 2:23 | MySQL Server: Logging | Closed (6398 days) | S3 | 5.1.20 | Linux | Any | SHOW commands once again ends up in the slow query log |
31700 | 2007-10-18 19:44 | 2007-11-26 18:50 | MySQL Server: Logging | Closed (6283 days) | S3 | 5.0, 5.1, 4.1, 5.2 bk | Any | Any | thd->examined_row_count not incremented for 'const' type queries |
32748 | 2007-11-27 1:54 | 2008-05-20 23:15 | MySQL Server: Logging | Closed (6107 days) | S3 | 5.1 | Any | Any | Inconsistent handling of assignments to general_log_file/slow_query_log_file |
38889 | 2008-08-19 11:14 | 2011-02-16 23:43 | MySQL Server: Logging | Duplicate (5909 days) | S3 | 6.0.7-alpha-debug | Linux (suse-linux-gnu on i686) | Any | Assignment of a variable to "slow_query_log_file" failed. |
49756 | 2009-12-17 4:39 | 2011-02-16 23:44 | MySQL Server: Logging | Closed (5230 days) | S3 | 5.0.44, 5.1.43 | Any | Any | Rows_examined is always 0 in the slow query log for update statements |
63548 | 2011-12-02 19:13 | 2011-12-05 8:06 | MySQL Server: Logging | Verified (4816 days) | S3 | any | Any | Any | disable logging to slow log session-wise |
69420 | 2013-06-07 7:18 | 2013-10-16 15:02 | MySQL Server: Logging | Closed (4132 days) | S5 | 5.6.12 | Any | Any | log_slow_statement could bail out earlier if slow logging is disabled |
73974 | 2014-09-18 21:41 | 2015-09-28 19:08 | MySQL Server: Logging | Closed (3420 days) | S3 | 5.7.6 | Windows | Any | trunk - slow query log shows some bogus SET timestamp=4294966218; value |
73978 | 2014-09-19 10:14 | 2014-12-01 7:23 | MySQL Server: Logging | Closed (3733 days) | S3 | 5.6.15, 5.6.20 | Any | Any | slow_log table doesn't store fractional time part |
88937 | 2017-12-15 11:27 | 2017-12-19 11:51 | MySQL Server: Logging | Verified (2607 days) | S3 | 5.6.38, 5.7.20 | Any | Any | mysql client history file grows without bounds, slows down connecting to server |
95775 | 2019-06-13 2:13 | 2019-06-13 5:59 | MySQL Server: Logging | Verified (2066 days) | S3 | 5.6 | Any | Any | Version 5.6 has the wrong format for slow logging time |
105540 | 2021-11-12 7:10 | 2023-06-07 15:17 | MySQL Server: Logging | Verified (1183 days) | S3 | 5.7,8.0 | Any | Any | the incorrect value of start_time field in the system table 'mysql.slow_log' |
107352 | 2022-05-20 11:00 | 2025-01-22 5:01 | MySQL Server: Logging | Verified (984 days) | S3 | 8.0.28, 8.0.29 | Any | Any | ROWS_EXAMINED confusing in MySQL 8 |
112414 | 2023-09-21 13:45 | 2023-09-28 10:12 | MySQL Server: Logging | Verified (500 days) | S3 | 8.0 | Any | Any | log_slow_admin_statements cause store procedure record dml in slow log |
115285 | 2024-06-11 16:56 | 2024-06-12 14:00 | MySQL Server: Logging | Verified (240 days) | S3 | 8.0 | Any | Any | log_slow_extra duplicates session number in Id and Thread_id |
116814 | 2024-11-28 3:43 | 2024-11-28 9:46 | MySQL Server: Logging | Verified (71 days) | S3 | 8.0.40 | Any | Any | The mysql.slow_log table uses @@session.time_zone to record time |
50954 | 2010-02-05 19:46 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5480 days) | S3 | MySQL 5.1.32, 5.1, 5.5.99 | Linux (Red Hat 4.1.2-44) | Any | start_time in slow query log is recording the query end time, not start time |
53191 | 2010-04-27 9:10 | 2011-02-16 23:44 | MySQL Server: Logging | Closed (5230 days) | S1 | 5.1.45, 5.1.46 | Any (linux, windows) | Any | Lock_time in slow log is negative when logging stored routines |
64822 | 2012-03-31 1:33 | 2013-03-26 22:27 | MySQL Server: Logging | Closed (4336 days) | S3 | 5.1.61, 5.5.20 | Any | Any | ALTER TABLE does not appear in the slow query log |
65715 | 2012-06-22 19:51 | 2012-08-23 16:27 | MySQL Server: Logging | Closed (4551 days) | S3 | 5.5.25 | Any (x86_64) | Any | Wrong connection ID (thread ID) in the general and slow query logs |
82870 | 2016-09-06 10:07 | 2018-10-25 12:54 | MySQL Server: Logging | Verified (2583 days) | S3 | 5.7.14 | Any | Any | mysqld opens too many descriptors for slow query log |
82899 | 2016-09-08 3:14 | 2016-09-08 6:31 | MySQL Server: Logging | Verified (3074 days) | S3 | 5.7.14, 5.7.15 | Any | Any | Trying to turn-off slow_query_log with an active thrd logging slow query ASSERTs |
109482 | 2022-12-25 9:33 | 2022-12-26 4:56 | MySQL Server: Logging | Verified (774 days) | S3 | 8.0.27 | Any | Any | The mysql slow query log contains invalid content, and the mysql common log file |
110804 | 2023-04-25 13:47 | 2023-04-26 23:03 | MySQL Server: Logging | Verified (653 days) | S3 | 8.0.32 | Any | Any | sql as "select count(*) from table" can't be logged in the slow query log. |
30712 | 2007-08-30 0:00 | 2007-10-09 0:43 | MySQL Server: Logging | Closed (6331 days) | S2 | 5.1 | Any | Any | open_performance_schema_table() cause an open table leak on failures |
115160 | 2024-05-29 9:52 | 2024-05-29 12:51 | MySQL Server: Logging | Verified (254 days) | S5 | 8.0 | Any | Any | Fix for bug 113187 |
32738 | 2007-11-26 20:05 | 2011-02-16 23:43 | MySQL Server: Logging | Closed (5566 days) | S3 | 5.1, 6.0 | Any | Any | mysqld: Two slow log option/variable descriptions are inaccurate |
96722 | 2019-09-03 3:19 | 2019-12-10 6:37 | MySQL Server: Logging | Verified (1886 days) | S3 | 5.6.28, 5.6.45, 5.7.27 | Any | Any | Event does't record slow insert in slow log |
30414 | 2007-08-14 17:09 | 2013-04-23 19:01 | MySQL Server: Logging | Closed (4308 days) | S5 | 5.1 | Any | Any | Slowdown (related to logging) in 5.1.21 vs. 5.1.20 |
98046 | 2019-12-21 8:14 | 2020-01-21 21:34 | MySQL Server: Logging | Verified (1873 days) | S3 | All | Linux | Any | Inconsistent behavior while logging a killed query in the slow query log |
23225 | 2006-10-12 18:20 | 2007-03-08 3:16 | MySQL Server: Logging | Closed (6546 days) | S3 | 5.1 bk | Linux (Linux) | Any | Slow query log: settiing slow_query_log_file writes to wrong file |
110098 | 2023-02-16 11:57 | 2023-02-16 12:33 | MySQL Server: Logging | Verified (722 days) | S3 | Ver 8.0.32 | Any | Any | add database message into slow log file |
89637 | 2018-02-13 1:38 | 2024-06-18 17:45 | MySQL Server: Logging | Closed (2307 days) | S3 | 8.0.4 | Any | Any | Contribution by Facebook: Slow Query Log Changes |
28808 | 2007-05-31 14:00 | 2007-07-10 22:14 | MySQL Server: Logging | Closed (6422 days) | S3 | 5.0.44-BK, 5.0.40, 5.0.34, 5.0.24a | Linux | Any | log_queries_not_using_indexes variable dynamic change is ignored |
47905 | 2009-10-07 23:43 | 2011-02-16 23:44 | MySQL Server: Logging | Closed (5348 days) | S3 | 5.1.39 | Any | Any | stored procedures with multiple statements not being logged to slow query log |
71892 | 2014-02-28 22:00 | 2015-03-24 21:40 | MySQL Server: Logging | Closed (3608 days) | S2 | 5.5,5.6,5.7 | Any | Any | Missing information in slow query log for slow HANDLER statements |
80467 | 2016-02-22 9:26 | 2016-03-31 10:32 | MySQL Server: Logging | Verified (3235 days) | S3 | 5.7.11 | CentOS | Any | log_queries_not_using_indexes is not working as expected in 5.7 |
98103 | 2020-01-01 5:14 | 2023-09-18 19:09 | MySQL Server: Logging | Verified (1852 days) | S3 | All, 8.0.18 | Any | Any | unexpected behavior while logging an aborted query in the slow query log |
72243 | 2014-04-04 18:48 | 2014-04-04 19:33 | MySQL Server: Logging | Verified (3962 days) | S3 | 5.7.4 | Any | Any | Queries where execution time exceeds 'MAX_STATEMENT_TIME' should go to slow log |
72529 | 2014-05-04 10:13 | 2014-05-04 11:22 | MySQL Server: Logging | Verified (3932 days) | S5 | 5.5 | Any | Any | rm a large slow log file and then flush slow logs, the mysqld will hang |
76639 | 2015-04-09 10:49 | 2015-04-09 10:53 | MySQL Server: Logging | Verified | S3 | 5.6.20 | Any | Any | Index Merge (sort_union) plan gets picked up by log_queries_not_using_indexes=1 |
115526 | 2024-07-05 13:16 | 2024-07-08 8:15 | MySQL Server: Logging | Verified (214 days) | S2 | 8.0, 8.4, 9.0 | Any | Any | Invalid multi-line "use" in slow query log file with multi-line schema. |
104615 | 2021-08-13 10:26 | 2021-08-13 11:36 | MySQL Server: Logging | Verified (1274 days) | S5 | 8.0 | Any (rhel7.4) | Any (intel-x86) | trx commit slow if there are too many binlog files to purge while rotating |
59861 | 2011-02-01 1:50 | 2011-03-07 23:18 | MySQL Server: Logging | Closed (5086 days) | S3 | 5.1, 5.5, trunk | Any | Any | why does log_slow_statement call thd_proc_info twice? |
68626 | 2013-03-10 16:11 | 2014-03-11 21:25 | MySQL Server: Logging | Closed (3986 days) | S3 | 5.6.10 | Any | Any | GRANT statements logged twice in slow query log |
91496 | 2018-06-29 11:40 | 2022-06-07 15:43 | MySQL Server: Logging | Closed (976 days) | S3 | 5.7.3 | Any | Any | Regression: Slow_queries status variable isn't incremented if slow query is off |
93963 | 2019-01-17 12:56 | 2019-02-21 3:08 | MySQL Server: Logging | Closed (2178 days) | S3 | 8.0.13 | Any | Any | Slow query log doesn't log a slow CREATE INDEX with admin statements enabled |
111180 | 2023-05-29 6:19 | 2024-04-10 7:16 | MySQL Server: Logging | Verified (620 days) | S3 | 5.7*, 5.7.42, 5.7.44 | Any | Any | binlog rotate will cause query missing in slow log |
115841 | 2024-08-15 4:15 | 2024-12-06 9:51 | MySQL Server: Logging | Verified (176 days) | S3 | 8.0.39, 8.4.2 | Any | Any | Lock_time in slow log does not correctly record the lock waiting time |
116651 | 2024-11-14 11:27 | 2024-11-22 10:36 | MySQL Server: Logging | Verified (85 days) | S3 | 8.0 | Any | Any | slow log start_time is incorrect |
19699 | 2006-05-10 21:43 | 2006-05-10 22:05 | MySQL Server: Logging | Duplicate (6848 days) | S3 | * | Any (*) | Any | Cannot enable/disable general query log or slow query log at runtime |
19764 | 2006-05-12 10:28 | 2006-11-09 14:55 | MySQL Server: Logging | Closed (6665 days) | S3 | 5.0.15 | Any (*) | Any | SHOW commands end up in the slow log as table scans |
35396 | 2008-03-18 14:15 | 2011-12-01 20:37 | MySQL Server: Logging | Closed (4817 days) | S3 | 5.0.50sp1a, 5.0 bzr | Any | Any | Abnormal / impossible / large Query_time and Lock_time values in slow query log |
39618 | 2008-09-23 21:56 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5917 days) | S3 | 5.0.27, 5.0.67 | Windows (XP) | Any | Using log-short-format does not change what is logged |
68530 | 2013-02-28 21:32 | 2013-08-22 15:44 | MySQL Server: Memcached | Closed (4187 days) | S1 | 5.6.10 GA | Linux (Centos 5) | Any | memory leak with innodb memcached plugin for stale connection |
69066 | 2013-04-25 9:38 | 2013-05-07 18:11 | MySQL Server: Memory storage engine | Duplicate (4294 days) | S3 | 5.6.11 | Any | Any | Memory leak slave_parallel_workers |
69075 | 2013-04-26 3:07 | 2014-02-19 10:39 | MySQL Server: Memory storage engine | Duplicate (4006 days) | S3 | 5.6.11, 5.6.15 | Any | Any | Memory leak slave_parallel_workers |
29349 | 2007-06-26 1:01 | 2014-02-02 14:12 | MySQL Server: Memory storage engine | Verified (6435 days) | S3 | 5.0.27 | Any | Any | dropping MEMORY table very slow |
30090 | 2007-07-27 6:23 | 2012-05-18 20:19 | MySQL Server: Memory storage engine | Duplicate (6275 days) | S3 | 5.0.44 | Any | Any | DELETE from MEMORY table with BTREE primary key extremely slow |
73777 | 2014-08-31 11:00 | 2015-08-24 13:24 | MySQL Server: Memory storage engine | Verified (3812 days) | S3 | 5.6, 5.6.21, 5.5.40 | Linux | Any | DELETE query takes a long time and examines more rows than exist in the table |
23764 | 2006-10-30 10:16 | 2006-11-28 12:28 | MySQL Server: Memory storage engine | Closed (6646 days) | S2 | 5.0.26 5.0.27 | Linux (FC5) | Any | BTREE index deletes only 1 item on memory table |
30743 | 2007-08-31 8:05 | 2013-03-03 20:45 | MySQL Server: Merge storage engine | Verified (5766 days) | S3 | 5.0.37-community/5.1/6.0 | Any | Any | Delete from MERGE-table is slow |
48153 | 2009-10-19 15:09 | 2014-03-13 18:38 | MySQL Server: MyISAM storage engine | Verified (3984 days) | S3 | 5.1.40, 5.6.17 | Any | Any | Slowdown in test-connect |
98511 | 2020-02-07 10:11 | 2020-06-30 17:34 | MySQL Server: MyISAM storage engine | Closed (1683 days) | S5 | 8.0.19, 8.0.20 | Windows | Any | OPTIMIZE TABLE on myisam can increase table size (~2x) and reduce performance |
2643 | 2004-02-04 13:21 | 2004-02-04 18:10 | MySQL Server: MyISAM storage engine | Closed (7674 days) | S2 | 4.0.16 | Linux (linux) | Any | 4.0.16 selects different index than 4.0.14 |
2615 | 2004-02-02 11:03 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | Duplicate (6505 days) | S2 | 4.1 | Linux (Red Hat 9.0) | Any | Performance problem when joining NULLs |
44723 | 2009-05-07 15:34 | 2018-04-01 11:47 | MySQL Server: MyISAM storage engine | Closed (5621 days) | S5 | 5.0/5.1 | Linux | Any | Larger read_buffer_size values can cause performance decrease for INSERTs |
712 | 2003-06-24 10:33 | 2003-08-27 4:43 | MySQL Server: MyISAM storage engine | Closed (7835 days) | S3 | Any | slow indexes in 4.0.13 vs. 3.23 | ||
2420 | 2004-01-16 1:58 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | Duplicate (7691 days) | S2 | 4.1.2-dev latest | Linux (Linux 2.4.21) | Any | Fulltext index corrups table |
100017 | 2020-06-27 14:02 | 2023-05-05 8:00 | MySQL Server: MyISAM storage engine | Duplicate (1684 days) | S5 | 8.0.20 | Any | Any | Extremely slow queries after database repair |
3835 | 2004-05-20 10:51 | 2004-05-24 11:03 | MySQL Server: MyISAM storage engine | Closed (7564 days) | S1 | 4.1.2 | Windows (Win 2000/XP) | Any | alter table enable/disable keys corrupts database |
41871 | 2009-01-05 15:47 | 2018-09-09 20:45 | MySQL Server: MyISAM storage engine | Verified (5607 days) | S5 | 5.1.30 | Any (MS Windows, Mac OS X) | Any | Select + Index + Limit + offset on large MyIsam tables give very bad performance |
43401 | 2009-03-05 8:00 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5818 days) | S3 | 5.1.30 | FreeBSD | Any | Query spends too much time in ``sending data'' state |
31551 | 2007-10-11 22:30 | 2013-06-13 19:31 | MySQL Server: MyISAM storage engine | Verified (6086 days) | S2 | 5.0.45, 5.0 BK, 5.1 BK | Linux (CentOS 4.5) | Any | MyISAM poor performance with multiple queries running concurrently |
40634 | 2008-11-11 11:30 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5800 days) | S5 | 5.1.29, 6.0.x | Any | Any | table scan temporary table is 4x slower due to mmap instead instead of caching |
56523 | 2010-09-03 1:12 | 2011-02-16 23:44 | MySQL Server: MyISAM storage engine | Closed (5193 days) | S2 | 5.6 | Any | Any | Instrumentation regression in myisam/mi_rprev.c |
57430 | 2010-10-13 13:41 | 2015-11-23 10:42 | MySQL Server: Optimizer | Closed (3364 days) | S3 | 5.5.6-rc, 5.5.7 | Linux | Any | query optimizer does not pick covering index for some "order by" queries |
59557 | 2011-01-17 15:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5135 days) | S2 | 5.1, 5.5 | Any | Any | MySQL uses order of fields in GROUP BY when ORDER BY NULL is specified |
60281 | 2011-02-28 14:01 | 2013-01-15 14:37 | MySQL Server: Optimizer | Duplicate (4406 days) | S5 | Any | Any | Performance suggestion: optimize large and simple "LIMIT" queries | |
62307 | 2011-08-31 1:54 | 2011-09-01 21:29 | MySQL Server: Optimizer | Verified (4908 days) | S3 | 5.5.15 | Any | Any | Condition "TIME = '19:20'" does not use index in sjis |
64557 | 2012-03-06 0:12 | 2012-10-08 18:33 | MySQL Server: Optimizer | Closed (4505 days) | S2 | 5.1.56, 5.5.20, 5.6.4 | Windows (XP Pro SP3) | Any | Correlated subquery performance is degraded in releases alfter 5.0 |
64791 | 2012-03-28 20:17 | 2015-07-09 8:35 | MySQL Server: Optimizer | Verified (4698 days) | S2 | 5.1.61, 5.5 | Any | Any | Mixed String/Int values in IN list cause full table scan |
65792 | 2012-07-03 2:19 | 2012-07-04 9:54 | MySQL Server: Optimizer | Verified (4602 days) | S5 | 5.1,5.5 | Any | Any | an unecessary Using temporary in distinct query |
67815 | 2012-12-05 8:51 | 2012-12-06 6:15 | MySQL Server: Optimizer | Verified (4446 days) | S3 | 5.5.28, 5.6.7 | Linux | Any | MySQL consistently uses a low cardinality non-referenced column in a index scan |
68818 | 2013-03-30 5:29 | 2013-04-01 14:37 | MySQL Server: Optimizer | Duplicate (4330 days) | S3 | 5.6.10 | Any | Any | Large Value List in WHERE Clause Spends Too Much Time in 'statistics' State |
70025 | 2013-08-14 7:00 | 2014-02-03 10:42 | MySQL Server: Optimizer | Closed (4091 days) | S2 | 5.6.13 | Linux (Oracle Linux 6) | Any | Update on P_S setup_consumers and threads through JOIN only updates first row |
71171 | 2013-12-18 10:40 | 2014-02-04 14:40 | MySQL Server: Optimizer | Verified (4021 days) | S2 | 5.6.14 | Linux (Debian 7.1) | Any | Optimizer executes inperformant subquery first |
72501 | 2014-05-01 17:31 | 2014-05-01 18:12 | MySQL Server: Optimizer | Verified | S3 | 5.6.17 | Any | Any | joining NULLs + different collation is not efficient |
72518 | 2014-05-02 23:42 | 2015-08-30 20:59 | MySQL Server: Optimizer | Closed (3449 days) | S5 | 5.6.16 | Any | Any | UPDATE ORDER BY does a filesort if updating a column in the index |
74256 | 2014-10-07 22:43 | 2015-11-02 6:19 | MySQL Server: Optimizer | Verified (3677 days) | S2 | 5.6.19, 5.6.22 | Any | Any | index_extensions used incorrectly in select cause performance regression |
76933 | 2015-05-04 17:26 | 2016-11-16 15:56 | MySQL Server: Optimizer | Closed (3005 days) | S5 | 5.6.24, 5.6.25 | Linux | Any | Performance Regression in 5.6: Update does not use index |
79480 | 2015-12-01 10:59 | 2015-12-03 10:42 | MySQL Server: Optimizer | Verified (3354 days) | S3 | 5.7.9 | Any | Any | Suboptimal query plan in simple join compared to MariaDB 10.1 |
80505 | 2016-02-25 9:43 | 2016-02-25 14:53 | MySQL Server: Optimizer | Duplicate (3270 days) | S5 | 5.7.11 | Windows | Any | mysql server 5.7.11 view performance issue |
81854 | 2016-06-15 7:55 | 2016-11-23 18:58 | MySQL Server: Optimizer | Closed (2998 days) | S3 | 5.7, 5.7.13 | Any | Any | Force index is skipped while executing select count(*) |
83287 | 2016-10-06 12:54 | 2016-11-19 16:28 | MySQL Server: Optimizer | Closed (3005 days) | S3 | 5.7 | Any | Any | created_tmp_tables statistic is wrong |
83856 | 2016-11-17 4:19 | 2019-11-15 17:31 | MySQL Server: Optimizer | Verified (2973 days) | S3 | 5.7.13,5.7.16 | CentOS | Any | Index ref not used for multi-column IN - type or collation conversion warning |
85933 | 2017-04-13 13:25 | 2023-11-02 6:30 | MySQL Server: Optimizer | Closed (2690 days) | S5 | 8.0.1-dmr | Any | Any | Performance regression with Prepared Statements |
86710 | 2017-06-15 8:57 | 2017-07-28 2:01 | MySQL Server: Optimizer | Closed (2751 days) | S2 | 8.0.2-dmr-enterprise-commercial-advanced | Linux | Any | Performance issue of explicit COLLATE clause |
86884 | 2017-06-30 12:44 | 2017-10-24 14:25 | MySQL Server: Optimizer | Closed (2776 days) | S3 | 8.0.3 | Any | Any | Create decimal microbenchmarks |
92850 | 2018-10-19 0:46 | 2018-10-22 5:31 | MySQL Server: Optimizer | Verified (2300 days) | S3 | 5.7.23 | Any | Any | Bad select+order by+limit performance in 5.7 |
93845 | 2019-01-07 21:55 | 2021-08-23 12:23 | MySQL Server: Optimizer | Verified (2221 days) | S2 | 5.7,8.0.11,8.0.13 | Any | Any | Optimizer choose wrong index, sorting index instead of filtering index |
94224 | 2019-02-06 16:45 | 2019-11-17 10:39 | MySQL Server: Optimizer | Verified (2192 days) | S3 | 5.6, 5.6.43 | Any (any) | Any (any) | [5.6] Optimizer reconsiders index based on index definition order, not value |
94655 | 2019-03-14 11:04 | 2021-05-17 14:24 | MySQL Server: Optimizer | Closed (1798 days) | S2 | 8.0 | Any | Any | Some GIS function do not use spatial index anymore |
95058 | 2019-04-18 18:12 | 2019-04-25 2:29 | MySQL Server: Optimizer | Verified (2115 days) | S3 | 5.7.21 | Any | Any | Index not used for column with IS TRUE or IS FALSE operators |
98520 | 2020-02-08 9:37 | 2020-05-05 14:51 | MySQL Server: Optimizer | Verified (1739 days) | S5 | 8.0 | Any | ARM | Suboptimal implementations for some load/store functions for little-endian arch |
98771 | 2020-02-28 6:29 | 2020-03-02 18:39 | MySQL Server: Optimizer | Verified (1806 days) | S2 | 5.7, 5.7.29 | Any | Any | Performance impact while selecting data from a JSON type column |
101220 | 2020-10-18 0:37 | 2021-02-23 18:44 | MySQL Server: Optimizer | Closed (1445 days) | S5 | 8.0.21 | Any | Any | Filesort used for ORDER BY ...DESC even when DESCending index available and used |
103010 | 2021-03-17 7:33 | 2021-03-17 11:16 | MySQL Server: Optimizer | Verified (1423 days) | S5 | 8.0.23 | Any | Any | Subquery dependent on const tables gets evaluated for unnecessary multiple times |
104186 | 2021-07-01 15:04 | 2022-01-25 17:07 | MySQL Server: Optimizer | Closed (1235 days) | S5 | 8.0 | Any | Any | Too few chunk files are created for hybrid hash join |
104760 | 2021-08-29 19:12 | 2021-09-20 12:14 | MySQL Server: Optimizer | Verified (1256 days) | S2 | 8.0.26 | Any | Any | incorrect placement of hash join predicates in a left outer join nest |
105303 | 2021-10-22 18:55 | 2021-10-23 6:33 | MySQL Server: Optimizer | Duplicate (1203 days) | S2 | 8.0.20+ | Any | Any | Unmanageable Sort Buffer Behavior in 8.0.20+ |
105304 | 2021-10-22 19:00 | 2021-11-12 22:34 | MySQL Server: Optimizer | Closed (1183 days) | S2 | 8.0.20+ | Any | Any | Unmanageable Sort Buffer Behavior in 8.0.20+ |
106135 | 2022-01-11 15:33 | 2022-01-13 14:49 | MySQL Server: Optimizer | Closed (1121 days) | S5 | 8.0.27 | Any | Any | REGEXP performance failure |
108116 | 2022-08-11 8:21 | 2024-10-30 6:13 | MySQL Server: Optimizer | Verified (911 days) | S3 | 8.0.29, 8.0.30, 5.7.39 | Any (rhel-7.4) | Any (x86-64) | SQL queries with range of Item_row are not optimized |
109601 | 2023-01-12 9:00 | 2023-01-12 9:38 | MySQL Server: Optimizer | Verified (757 days) | S3 | 8.0 | Any | Any | Apply partition pruning if all insert rows have non-null values on autoinc field |
110779 | 2023-04-24 11:32 | 2023-05-12 5:49 | MySQL Server: Optimizer | Verified (637 days) | S5 | 8.0.33, 5.7.42 | Any | Any | IN clause cause pick bad performan index |
111952 | 2023-08-02 19:50 | 2024-10-30 6:12 | MySQL Server: Optimizer | Verified (554 days) | S2 | 8.0.34, 5.7.43, 8.1.0 | Any | Any | Row constructor inequality comparison on Primary Key results in full table scan. |
112362 | 2023-09-15 20:19 | 2024-12-20 10:45 | MySQL Server: Optimizer | Closed (50 days) | S5 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 | WHERE NOT IN with subquery is much slower on 8.1 than 5.7 |
113288 | 2023-11-30 6:58 | 2023-12-01 11:37 | MySQL Server: Optimizer | Verified (435 days) | S5 | 8.0.33 | Any | Any | Explain plan shows dynamic range, but bug causes no chance to use for LEFT JOIN |
114812 | 2024-04-29 9:55 | 2024-04-29 10:19 | MySQL Server: Optimizer | Verified (284 days) | S5 | 8.0.36,5.7.44 | Any | Any | in list values exceed eq_range_index_dive_limit cause index not used |
115190 | 2024-05-31 22:12 | 2024-06-01 9:46 | MySQL Server: Optimizer | Verified (251 days) | S5 | 8.0.36 | Ubuntu (jammy) | Any | Failure to use index with subquery and tuples |
115969 | 2024-08-30 13:59 | 2024-09-02 10:36 | MySQL Server: Optimizer | Verified (158 days) | S5 | 8.0.39 | Any | Any | MySQL need not sort with ORDER BY primary_key on InnoDB on partial index match |
116014 | 2024-09-05 15:43 | 2024-11-07 14:51 | MySQL Server: Optimizer | Verified (135 days) | S5 | 8.0.27+ | Any | Any | Performance Degradation in Query Execution Plans |
116803 | 2024-11-27 11:29 | 2024-12-09 10:06 | MySQL Server: Optimizer | Verified (60 days) | S5 | 8.0.40 | Any | Any | MySQL 8.0.33 is slower than MySQL 8.0.28 with queries using JOINS |
116964 | 2024-12-13 8:06 | 2024-12-13 9:31 | MySQL Server: Optimizer | Verified (56 days) | S2 | 8.0.38, 8.0.40 | Linux | Any | Result mismatch caused by derived condition push down. |
8139 | 2005-01-26 7:49 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (5941 days) | S3 | 4.1.8 | Linux (Linux) | Any | subselect index not used for "in" but used for "=" |
9021 | 2005-03-07 13:23 | 2012-03-26 19:37 | MySQL Server: Optimizer | Closed (4701 days) | S1 | 4.1.7, 5.6.4 | FreeBSD (FreeBSD) | Any | Query with subquery does not use index in outer query |
14295 | 2005-10-25 14:06 | 2012-08-31 16:06 | MySQL Server: Optimizer | Closed (4543 days) | S3 | 4.1 and above | Linux (linux) | Any | very slow 'explain' |
16081 | 2005-12-30 0:19 | 2011-06-16 16:21 | MySQL Server: Optimizer | Closed (4985 days) | S5 | 5.0.19-BK, 5.0.15 | Linux (LINUX) | Any | SLOW SELECT |
17212 | 2006-02-07 23:09 | 2007-04-24 16:40 | MySQL Server: Optimizer | Closed (6499 days) | S1 | 4.1.18, 5.0.18, 4.0.26 | Linux (linux) | Any | results not sorted correctly by ORDER BY when using index |
17560 | 2006-02-19 20:36 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5349 days) | S3 | 5.0.18 | Linux (Linux) | Any | select with subselect does not use indexed key |
19579 | 2006-05-06 10:59 | 2006-10-23 14:10 | MySQL Server: Optimizer | Closed (6682 days) | S5 | 5.0.24-BK, 5.0.16-log, 5.0.18, 5.0.21-log, 5.1.7-log | Linux (Linux) | Any | Optimizer does not choose right index and thus query is slow. |
24770 | 2006-12-02 0:37 | 2018-09-09 20:45 | MySQL Server: Optimizer | In progress (5072 days) | S5 | 5.1 | Any (all) | Any | update with subquery slow |
28554 | 2007-05-21 9:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5740 days) | S3 | 4.1.22, 5.0.42-BK | Any | Any | Optimizer wrongly prefers index for (col = value) over (PK <= value) |
34310 | 2008-02-05 14:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4069 days) | S5 | 5.0.51a-log, 5.0.54, 5.6.14 | Linux | Any | Optimizer is inefficient by using ORDER BY function() and LIMIT |
36660 | 2008-05-12 4:45 | 2011-03-21 4:14 | MySQL Server: Optimizer | Closed (5072 days) | S3 | 5.1.20 | Linux | Any | SUBQUERY slow |
42948 | 2009-02-17 23:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5820 days) | S5 | 5.0.67-0ubuntu6, 6.0.11 | Linux (Ubuntu 8.10) | Any | MySQL Optimizer does not properly use Indexes on Views with "Group By" |
43187 | 2009-02-25 13:45 | 2012-07-30 17:42 | MySQL Server: Optimizer | Closed (4575 days) | S5 | 5.0, 5.1, 5.6 | Linux | Any | SELECT ... WHERE (col1, col2) IN ((const, const)) is optimized, non-SELECT not |
46135 | 2009-07-12 19:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5312 days) | S2 | 5.0, 5.1, next, 6.0.0, 6.0.2, 5.1.36 | Any | Any | LIMIT + JOIN problem |
55979 | 2010-08-13 22:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5289 days) | S5 | 5.1.39 | Linux | Any | Key not used if IN() list contains mix of strings and integers |
56714 | 2010-09-10 12:45 | 2013-04-02 7:20 | MySQL Server: Optimizer | Closed (4329 days) | S5 | 5.1.50, 5.1.51-bzr | Windows | Any | Slow MAX() on primary key retrieved by secondary index in InnoDB |
58101 | 2010-11-10 0:21 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5202 days) | S5 | 5.1.38-community-log, 5.1.54-bzr | Linux | Any | Optimizer picks wrong order of queries |
59203 | 2010-12-29 4:38 | 2015-02-24 16:10 | MySQL Server: Optimizer | Closed (3636 days) | S1 | 5.0.91,5.1.39,5.1.55,5.5.8 | Any | Any | Serious optimizer failure when query is encapsulated in additional SELECT/INSERT |
61541 | 2011-06-16 16:26 | 2011-06-18 13:35 | MySQL Server: Optimizer | Duplicate (4983 days) | S3 | 5.5 | Linux | Any | SLOW QUERY - REWRITE |
61631 | 2011-06-24 14:49 | 2014-01-03 8:40 | MySQL Server: Optimizer | Closed (4053 days) | S5 | 5.5.13, 5.5.22 | Linux (centos 5.5) | Any | slow query plans for queries with low cardinality columns in a key |
63905 | 2012-01-02 23:47 | 2012-01-16 18:35 | MySQL Server: Optimizer | Verified (4771 days) | S5 | 5.1.60 | Windows | Any | handler_read_next is suprisingly high and slows queries |
65177 | 2012-05-02 9:43 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (4659 days) | S5 | 5.1,5.5 | Any | Any | perromance issue of "order by rand()" |
67980 | 2012-12-27 14:54 | 2013-01-19 10:52 | MySQL Server: Optimizer | Verified (4402 days) | S3 | 5.5.28 | Any | Any | MySQL not utilising full index because of possible bad cardinality stats |
68046 | 2013-01-07 9:29 | 2013-02-08 8:49 | MySQL Server: Optimizer | Closed (4399 days) | S2 | 5.6-rc9 | Any (Ubuntu 12.04) | Any | IN() clause with many constant values does not perform |
73046 | 2014-06-19 2:42 | 2016-02-17 11:23 | MySQL Server: Optimizer | Verified (3886 days) | S3 | 5.6.19 | Any | Any | Optimizer chooses wrong plan with (const, range) order by range ASC |
78407 | 2015-09-11 12:45 | 2022-04-29 5:41 | MySQL Server: Optimizer | Verified (1015 days) | S5 | 7.4.6/5.6.24, 5.7, 8.0 | Linux | Any | wrong index being used in subqueries? |
81347 | 2016-05-08 16:10 | 2016-10-13 16:16 | MySQL Server: Optimizer | Closed (3039 days) | S3 | 5.1.73, 5.5.49, 5.6.30,5.7.12 | CentOS | Any | unnecessary scanned all databases for information_schema |
85834 | 2017-04-06 13:31 | 2017-08-01 10:13 | MySQL Server: Optimizer | Duplicate (2747 days) | S5 | 5.7.17 | Windows | Any | InnoDB: Very slow select query with many tables and IS NULL in where clause |
89149 | 2018-01-08 23:41 | 2018-01-16 17:07 | MySQL Server: Optimizer | Verified (2579 days) | S5 | 5.7.20 | Red Hat (7.4) | Any | SELECT DISTINCT on multiple TEXT columns is slow |
89367 | 2018-01-24 2:52 | 2018-01-24 9:04 | MySQL Server: Optimizer | Verified (2571 days) | S3 | 5.7.20, 5.7.21 | Any | Any | Storing result in a variable(UDV) causes query on a view to use derived tables |
93360 | 2018-11-27 9:41 | 2018-12-12 14:48 | MySQL Server: Optimizer | Verified (2249 days) | S5 | 5.6.16,5.7.23 | Linux | x86 | mysterious optimizer behavior |
93922 | 2019-01-14 16:04 | 2019-05-07 9:43 | MySQL Server: Optimizer | Closed (2103 days) | S2 | 8.0.13 | Linux | x86 | UNION ALL very slow with SUM(0) |
97339 | 2019-10-23 8:06 | 2021-07-23 13:05 | MySQL Server: Optimizer | Verified (1928 days) | S2 | 5.7.18, 5.7.28, 5.6.46 | Any | Any | bin() function return Incorrect result set |
105068 | 2021-09-28 22:06 | 2021-10-04 12:07 | MySQL Server: Optimizer | Verified (1226 days) | S3 | 5.7 | Any | Any | Type ref instead of range after reconsidering_access_paths_for_index_ordering. |
107554 | 2022-06-13 20:28 | 2022-06-14 16:02 | MySQL Server: Optimizer | Verified (969 days) | S5 | 8.0.29-0ubuntu0.20.04.3 | Ubuntu (20.04.4 LTS) | x86 | regexp_replace in trigger VERY slow when using unicode category \\p{C} |
112304 | 2023-09-09 18:07 | 2024-07-02 19:34 | MySQL Server: Optimizer | Closed (401 days) | S3 | 8.0 | Any | Any | MEM_ROOT::AllocBlock() does not satisfy minimum_length bigger than wanted_length |
114512 | 2024-03-29 9:35 | 2024-06-17 9:54 | MySQL Server: Optimizer | Verified (235 days) | S5 | 8.3.0, 8.0.36 | Any | Any | MySQL 8: Order by with hash join incredibly slow |
11948 | 2005-07-14 18:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (7128 days) | S3 | 5.0 | Any | Any | MyISAM only, nested JOIN Views, dramatic performance loss |
13814 | 2005-10-06 19:09 | 2005-11-09 3:47 | MySQL Server: Optimizer | Closed (7030 days) | S2 | 4.1.12/4.1 BK source | Linux (linux) | Any | index including TINYBLOB breaks SELECT functionality |
14253 | 2005-10-24 9:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5517 days) | S3 | 5.0, 4.1, 6.0.14-bzr | Linux (Linux) | Any | Optimizer uses partial indexes for subqueries, where it should not |
14816 | 2005-11-10 9:40 | 2005-11-24 0:29 | MySQL Server: Optimizer | Closed (7015 days) | S3 | 5.0.15, 5.0.16-bk | Linux (Linux, Windows) | Any | VIEW performs filesort when using ORDER BY but underlying table does not |
15135 | 2005-11-22 14:28 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5802 days) | S5 | 4.1.14 | Any (NT) | Any | Dependent subquery performs very badly |
19690 | 2006-05-10 16:13 | 2007-02-21 3:17 | MySQL Server: Optimizer | Closed (6561 days) | S2 | 4.1.19/4.1BK | Linux (Gentoo Linux) | Any | ORDER BY eliminates rows from the result |
19895 | 2006-05-17 22:41 | 2013-01-10 13:14 | MySQL Server: Optimizer | Closed (4411 days) | S3 | 5.0.20, 6.0.7, 6.0.14 | Windows (Windows XP) | Any | No optimization of where clause subqueries rewritable as joins |
21174 | 2006-07-20 6:17 | 2007-04-12 21:24 | MySQL Server: Optimizer | Closed (6511 days) | S2 | 5.0.18, 5.1bk | Linux (linux) | Any | Index degrades sort performance and optimizer does not honor IGNORE INDEX |
24972 | 2006-12-11 21:55 | 2012-09-05 16:35 | MySQL Server: Optimizer | Closed (4538 days) | S5 | 5.0.27, 6.0.14 | Any (Windows) | Any | Join and sub-query execution differences |
27199 | 2007-03-16 5:03 | 2013-09-09 9:28 | MySQL Server: Optimizer | Closed (4169 days) | S2 | 5.0.22, 5.0.37, 4.1 BK, 5.1 BK | Linux (linux) | Any | Performance problem when query contains a left join against a subquery |
36569 | 2008-05-07 15:32 | 2014-06-19 23:20 | MySQL Server: Optimizer | Closed (5307 days) | S5 | 5.0.56sp1 | Any | Any | UPDATE ... WHERE ... ORDER BY... always does a filesort even if not required |
37576 | 2008-06-23 6:29 | 2011-12-06 1:00 | MySQL Server: Optimizer | Closed (4812 days) | S5 | 6.0 | Linux (SLES10SP1 (2.6.16.46-0.12-smp)) | Any | MySQL6.0 performance regression compared with MySQL5.1 using Sysbench read test |
37759 | 2008-07-01 9:41 | 2008-07-01 19:56 | MySQL Server: Optimizer | Duplicate (6065 days) | S1 | 5.1.25 | Any | Any | Performance/Index problem updating from 5.1.22 to 5.1.25 |
38213 | 2008-07-17 20:46 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5420 days) | S3 | 5.1.23-rc | Any | Any | MySQL does not seem to execute select count (distinct) efficiently |
38745 | 2008-08-12 9:44 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5316 days) | S2 | 5.1 | Any | Any | MySQL 5.1 optimizer uses filesort for ORDER BY when it should use index |
41740 | 2008-12-25 8:51 | 2011-08-16 1:21 | MySQL Server: Optimizer | Closed (4924 days) | S5 | 5.1.25,5.1.30 | Any | Any | MySQL 5.1 optimizer produces inefficient plan for complex queries |
44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5351 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
45424 | 2009-06-10 6:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5721 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 ? |
46376 | 2009-07-24 17:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5672 days) | S5 | 5.0.85, 5.1.36, 5.1.38, 5.1.39 | Windows (XP) | Any | Optimizer choose wrong index even when where clause and order-by are covered |
46508 | 2009-08-01 13:27 | 2011-02-16 23:44 | MySQL Server: Optimizer | Duplicate (5665 days) | S3 | 5.1.36 | Any | Any | MySQL 5.1.36 where / order by seems to sort first |
49111 | 2009-11-25 20:11 | 2012-08-30 14:32 | MySQL Server: Optimizer | Closed (4544 days) | S3 | 5.5.0-beta, 5.1 | Any | Any | Change in execution plan for count_distinct_group_on_key causes peformance drop |
50212 | 2010-01-10 14:07 | 2011-02-28 8:36 | MySQL Server: Optimizer | Closed (5093 days) | S5 | 5.1.37, 5.1.42, 5.1.43-bzr | Any | Any | MySQL doesn't use Primary Index for ORDER BY |
50571 | 2010-01-24 11:09 | 2011-02-16 23:44 | MySQL Server: Optimizer | Duplicate (5493 days) | S5 | 5.1.42 | Any | Any | MySQL not using an index when using tuples in IN clause |
41890 | 2009-01-05 22:53 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5769 days) | S3 | 6.0.9-release | Any | Any | Falcon: New execution plans with MRR cause slowdown for group of queries |
47330 | 2009-09-15 15:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5616 days) | S5 | 5.0.77, 5.1.34, 5.1.37 | Linux (Debian x64) | Any | Slow query with left join and having. |
21849 | 2006-08-26 10:07 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5420 days) | S5 | 5.0.32-BK, 4 and 5, 5.1.42-bzr | Linux (linux) | Any | select count distinct has rotten performance on at least versions 4&5 of mysql. |
104897 | 2021-09-10 6:29 | 2024-08-06 13:20 | MySQL Server: Optimizer | Closed (185 days) | S5 | 8.0.26, 8.0.17 | Any | x86 | Multi-valued index performance is too slow (Access too many rows than required) |
105017 | 2021-09-23 9:10 | 2024-06-14 20:55 | MySQL Server: Optimizer | Closed (238 days) | S3 | 8.0.26 | Any | Any | Execute a statement with secondary engine, two entries in performance schema |
116241 | 2024-09-26 10:05 | 2024-10-25 11:03 | MySQL Server: Optimizer | Verified (105 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Any | Any | Potential Performance Improvement on TPC-H |
76349 | 2015-03-17 11:35 | 2015-07-19 21:30 | MySQL Server: Optimizer | Closed (3491 days) | S2 | 5.6 | Any | Any | memory leak in add_derived_key() |
17952 | 2006-03-06 5:22 | 2012-10-15 13:48 | MySQL Server: Optimizer | Closed (4498 days) | S5 | 4.1.18 | Linux (Linux) | Any | nested query super slow..should not be |
81469 | 2016-05-17 21:51 | 2016-05-18 6:54 | MySQL Server: Optimizer | Verified (3187 days) | S3 | 5.6.30, 5.7.12 | Any | Any | Slow performance for IN subquery and UNION |
47884 | 2009-10-07 3:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5488 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 |
112597 | 2023-10-03 12:14 | 2023-10-05 14:13 | MySQL Server: Optimizer | Verified (491 days) | S5 | 8.0 | Any | Any | Slow performance |
112634 | 2023-10-05 12:03 | 2023-10-05 12:34 | MySQL Server: Optimizer | Duplicate (491 days) | S5 | 8.0 & 8.1 | Windows | x86 | Slow performance Mysql 8.x |
68979 | 2013-04-17 3:47 | 2018-07-11 15:11 | MySQL Server: Optimizer | Verified (4279 days) | S5 | 5.6.10 | Linux | Any | performance regression of MySQL 5.6.10? |
94296 | 2019-02-12 18:17 | 2019-02-13 19:41 | MySQL Server: Optimizer | Closed (2186 days) | S5 | 8.0.11 | Ubuntu (Ubuntu 16.04.1 LTS) | x86 (x86_64) | Poor Optimizer Performance with Composite Index, IN() function, and many Tuples |
106006 | 2021-12-30 3:10 | 2022-01-11 14:44 | MySQL Server: Optimizer | Closed (1123 days) | S5 | 8.0.25, 8.0.27, 5.7.36 | Any (rhel-7.4) | Any (x86-64) | conditions are not pushed down into subqueries with union all: performance issue |
35468 | 2008-03-20 20:01 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5191 days) | S3 | 6.0.4 | Any | Any | Slowdown and wrong result for uncorrelated subquery w/o where |
36449 | 2008-05-01 10:09 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5884 days) | S2 | 6.0.6-pre | Any | Any | Significant slowdown for (ANY|SOME) subqueries processed with semijoin |
78213 | 2015-08-25 20:03 | 2015-10-23 12:55 | MySQL Server: Optimizer | Closed (3411 days) | S2 | 5.6, 5.6.26, 5.5.46, 5.1.77 | Any (Mac OS X 10.9 and CentOS 6) | Any | Spatial index causes incorrect cardinality for all non-primary indexes |
9017 | 2005-03-07 11:02 | 2005-04-28 15:48 | MySQL Server: Optimizer | Closed (7225 days) | S2 | 4.1.10 | Windows (WinXP SP2, Linux 2.4.22) | Any | Rows are omitted from result set when using JOIN, XOR and ISNULL |
38842 | 2008-08-18 8:17 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5901 days) | S3 | 5.0.45, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | Fix for 25951 seems incorrect |
25130 | 2006-12-18 5:46 | 2012-03-26 19:41 | MySQL Server: Optimizer | Closed (4701 days) | S5 | 5.0.34-BK, 5.0.27, 5.1, 5.5.0 | Windows (Windows, Sparc & Linux) | Any | Extremely Slow "Where in (Select... )" Subqueries GROUP BY / HAVING related |
72854 | 2014-06-03 20:12 | 2017-10-05 15:43 | MySQL Server: Optimizer | Closed (2682 days) | S2 | 5.6.17 | Any | Any | Extremely slow performance with outer joins and join buffer |
48060 | 2009-10-14 21:20 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5561 days) | S3 | 5.5, 6.0-codebase | Any | Any | Memory leak - Item::val_bool() (item.cc:184) from optimizer_subquery grammar |
74590 | 2014-10-27 11:16 | 2014-12-01 16:56 | MySQL Server: Optimizer | Closed (3752 days) | S3 | 5.7.6 | Any | Any | Memory leak in unit test CostEstimationTest.MergeManyBuff |
24035 | 2006-11-07 8:57 | 2007-02-27 20:23 | MySQL Server: Optimizer | Closed (6555 days) | S5 | 5.0.34-BK, 5.0.26, 5.0.27 | Linux (Linux, FREEBSD) | Any | performance of update query difference between 5.0.22-log AND 5.0.27-log |
47914 | 2009-10-08 9:10 | 2012-03-26 19:30 | MySQL Server: Optimizer | Closed (4701 days) | S2 | 4.1 and 5.1 | Windows (Windows Server 2003) | Any | Performance Issue with Subquery |
76460 | 2015-03-23 13:01 | 2015-04-08 13:31 | MySQL Server: Optimizer | Closed (3593 days) | S3 | 5.7.5 | Any | Any | Cost constant cache's mutex not instrumented by performance schema |
83247 | 2016-10-03 14:02 | 2016-12-15 15:06 | MySQL Server: Optimizer | Closed (3039 days) | S3 | 5.6.33 | Any | Any | Severe regression in my_strnxfrm() from mysql-5.5 -> 5.6 |
116776 | 2024-11-25 18:45 | 2024-11-28 7:53 | MySQL Server: Optimizer | Verified (71 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 19 |
19649 | 2006-05-09 17:57 | 2006-10-10 18:58 | MySQL Server: Optimizer | Closed (6695 days) | S2 | 5.0.25-BK, 5.0.18 | Solaris (Solaris) | Any | Extremely slow join |
23410 | 2006-10-18 7:47 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (6541 days) | S5 | 5.0.26 | Any (*) | Any | "select * from... where .. order by" very slow when 0 rows match the where cond |
32665 | 2007-11-23 16:26 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5190 days) | S3 | 5.1.22-rc-Debian_1-log | Any | Any | Query with dependent subquery is too slow |
33833 | 2008-01-12 15:31 | 2008-04-02 17:22 | MySQL Server: Optimizer | Closed (6155 days) | S2 | 5.0-bk, 5.1-bk | Any | Any | No rows are returned, even though query matches |
44802 | 2009-05-11 20:35 | 2011-09-24 17:15 | MySQL Server: Optimizer | Closed (4885 days) | S3 | 4.1, 5.0, 5.1, 6.0.10-apha | Linux | Any | Very slow EXPLAIN when subqueries are used |
68748 | 2013-03-22 16:26 | 2013-04-01 16:14 | MySQL Server: Optimizer | Duplicate (4330 days) | S5 | 5.6.10 | Linux (Centos 5) | Any | Selects with large "IN" conditions are very slow |
74078 | 2014-09-25 16:15 | 2014-10-16 19:49 | MySQL Server: Optimizer | Verified (3767 days) | S5 | 5.6.19/5.5/5.7 | Linux (Ubuntu 14) | Any | join of large table to small table is slow if small table has less than 7 rows |
82725 | 2016-08-25 15:55 | 2016-09-14 6:28 | MySQL Server: Optimizer | Verified (3068 days) | S5 | 5.7.14, 5.7.15 | CentOS (Linux rda-db-rep.ucar.edu 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 11:11:39 UTC 2016 x86_64 x86_6) | Any | Extremely slow query when optimizer_switch='derived_merge=ON' |
100479 | 2020-08-10 9:04 | 2024-07-25 15:10 | MySQL Server: Optimizer | Duplicate (197 days) | S5 | 8.0 | Any | Any | search with in() function runs really slow |
111367 | 2023-06-12 15:36 | 2023-08-04 15:11 | MySQL Server: Optimizer | Verified (553 days) | S5 | 8.0 | Any | Any | OFFSET 99 LIMIT 1 on a compound PK takes ages to execute. |
17164 | 2006-02-06 18:29 | 2006-04-14 18:39 | MySQL Server: Optimizer | Closed (6874 days) | S2 | 5.0.19-BK, 5.0.18 | Linux (Linux) | Any | LEFT JOIN with OR clause not optimized correctly |
25658 | 2007-01-16 19:34 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5885 days) | S1 | 5.2.0 falcon-alpha and now 5.2.3 | Linux (Linux Fedora Core 6) | Any | Group by Performance is slow |
47839 | 2009-10-05 17:52 | 2020-05-03 20:45 | MySQL Server: Optimizer | Duplicate (5565 days) | S5 | 5.1.39 | Any | Any | UNIX_TIMESTAMP() is not treated as a const |
73136 | 2014-06-27 16:34 | 2015-05-20 15:16 | MySQL Server: Optimizer | Verified (3875 days) | S3 | 5.6.12,5.6.19,5.5, 5.5.38, 5.5.20 | Any | Any | Index scan incorrectly selected over ref+sort leading to x1000 worse performance |
109361 | 2022-12-13 12:06 | 2023-01-11 1:03 | MySQL Server: Optimizer | Closed (758 days) | S2 | 8.0.29 | Any | Any | MySQL 8.0.29+ is slower than MySQL 8.0.28 with queries using JOINS |
115679 | 2024-07-24 9:04 | 2024-07-24 9:46 | MySQL Server: Optimizer | Verified (198 days) | S5 | 8.0.37 | Any | Any | Block Nested-Loops Join can sometimes slow down the query |
27452 | 2007-03-26 17:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5926 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 |
27531 | 2007-03-29 18:00 | 2016-02-25 12:24 | MySQL Server: Optimizer | Closed (6482 days) | S2 | 4.1.22 5.0 | Any | Any | Query performance degredation in 4.1.22 and greater |
34364 | 2008-02-06 21:17 | 2012-07-30 17:14 | MySQL Server: Optimizer | Closed (4575 days) | S1 | 5.1.22 | Solaris (SunOS clapton.nms.fnc.fujitsu.com 5.10 Generic_118833-36 sun4u sparc SUNW,Ultra-4) | Any | LEFT JOIN with subquery takes very long time |
34869 | 2008-02-27 2:00 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (6076 days) | S3 | 5.0 | Any | Any | Almost 300% regression in index merge intersect performance |
35850 | 2008-04-05 4:09 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (5346 days) | S5 | 5.1.23 | Any (Tested w/ SUSE) | Any | Performance regression in 5.1.23/5.1.24 |
46648 | 2009-08-11 11:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5653 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 |
50843 | 2010-02-02 18:12 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5346 days) | S2 | 5.1.42 | Any | Any | Optimizer ignores clustered index for GROUP BY even when it improves performance |
53737 | 2010-05-18 9:30 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5307 days) | S2 | mysql-next-mr | Any | Any | Performance regressions after applying patch for bug 36569 |
54531 | 2010-06-15 21:39 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5350 days) | S2 | 5.1.46, 5.1.47 | Any | Any | Performance regression with many joins |
57024 | 2010-09-26 4:44 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5245 days) | S2 | 5.1 | Any | Any | Serious performance issue with an outer join |
58225 | 2010-11-16 11:21 | 2011-07-27 17:07 | MySQL Server: Optimizer | Closed (4944 days) | S2 | 5.1.49, 5.1.54, 5.5.7 | Windows (Server 2003) | Any | Extreme performance degradation with joins |
65957 | 2012-07-20 7:00 | 2013-06-21 19:41 | MySQL Server: Optimizer | Duplicate (4249 days) | S3 | 5.1.62, 5.5.27, 5.6.6 | Linux | Any | Poor correlated subquery performance with order by and limit |
67432 | 2012-10-31 5:46 | 2012-12-11 1:49 | MySQL Server: Optimizer | Closed (4441 days) | S5 | 5.6.7 | Any | Any | Serious performance degradation for the query with ORDER BY ... LIMIT n |
67899 | 2012-12-13 18:26 | 2013-02-24 19:43 | MySQL Server: Optimizer | Closed (4366 days) | S5 | 5.5.27 | Linux (CentOS 6.3) | Any | Adding LIMIT to query increases time from 2 seconds to 42 minutes |
68825 | 2013-04-01 16:28 | 2018-07-11 15:09 | MySQL Server: Optimizer | Verified (3447 days) | S5 | 5.6.10 | Any | Any | performance regressions for single-threaded workloads |
68919 | 2013-04-10 14:25 | 2013-04-10 14:33 | MySQL Server: Optimizer | Verified (4321 days) | S5 | 5.6.10 | Any | Any | Performance regression when DS-MRR is used for query with small limit |
69350 | 2013-05-30 5:44 | 2014-02-20 5:48 | MySQL Server: Optimizer | Verified | S5 | 5.6 | Any | Any | performance regression between 5.5 and 5.6 for simple statement in routine loop |
70002 | 2013-08-12 19:23 | 2013-08-19 7:38 | MySQL Server: Optimizer | Duplicate (4190 days) | S2 | 5.6.13, 5.5, 5.1 | Any | Any | very low performance join - eq_ref and ref access broken for compound indexes |
70021 | 2013-08-13 20:52 | 2013-10-03 13:38 | MySQL Server: Optimizer | Closed (4145 days) | S5 | 5.6.13 | Any | Any | Poor execution of a plan with unnecessary "range checked for each record" |
77414 | 2015-06-19 9:36 | 2016-02-04 20:01 | MySQL Server: Optimizer | Closed (3417 days) | S3 | 5.7.7 | Any | Any | Query digest does not reflect new optimizer hints |
81803 | 2016-06-10 12:35 | 2016-06-15 16:58 | MySQL Server: Optimizer | Verified (3159 days) | S5 | >=5.1 | Any | Any | Mysql 5.1 and later Update performance regression |
88671 | 2017-11-28 0:16 | 2017-12-04 15:41 | MySQL Server: Optimizer | Verified (2622 days) | S5 | 5.7.19 | Any | Any | ALL + BNL chosen over REF in query plan with a simple SELECT + JOIN |
99244 | 2020-04-14 3:22 | 2020-04-22 12:45 | MySQL Server: Optimizer | Verified (1753 days) | S1 | 8.0.19 | Any | Any | bad performance in hash join because join with no join condition between tables |
99414 | 2020-04-30 17:48 | 2020-05-20 12:20 | MySQL Server: Optimizer | Verified (1740 days) | S3 | 8.0.20 | Any | Any | Where exists performance 8.0.16 onwards |
103710 | 2021-05-15 14:26 | 2023-11-02 6:38 | MySQL Server: Optimizer | Closed (1344 days) | S5 | 8.0.25 | Linux | x86 | Prepared statement performance slower with prefer_ordering_index optimization |
107035 | 2022-04-15 9:12 | 2022-04-15 13:34 | MySQL Server: Optimizer | Verified (1029 days) | S5 | 8.0 | Any | Any | MRR may cause performance downgrade when multi-range on partition key |
109155 | 2022-11-22 5:43 | 2023-12-13 11:44 | MySQL Server: Optimizer | Verified (808 days) | S5 | 8.0.18, 8.0.31, 8.0.35 | Any | Any | Invalid scan on left join tables of which columns not in distinct output fields |
110998 | 2023-05-11 15:33 | 2023-12-01 6:49 | MySQL Server: Optimizer | Verified (632 days) | S5 | 8.0.20+, 8.0.33 | Linux | Any | Performance regression with SELECT query when sorting on limited fields |
112198 | 2023-08-28 8:21 | 2024-03-05 6:06 | MySQL Server: Optimizer | Verified (529 days) | S1 | 8.0, 8.0.34 | Any | Any | Incorrect multiple equality optimization causes performance degradation |
113647 | 2024-01-16 8:55 | 2024-03-07 20:37 | MySQL Server: Optimizer | Closed (337 days) | S5 | 8.0.35,8.2.0 | Any | Any | identical tables are checked in HashJoin because of no STOP_AT_MATERIALIZATION |
115227 | 2024-06-05 10:45 | 2024-08-09 9:32 | MySQL Server: Optimizer | Verified (247 days) | S5 | 8.0 | Any | Any | prepared statement encounter performance degradation compared with normal select |
115555 | 2024-07-10 10:31 | 2024-09-16 9:49 | MySQL Server: Optimizer | Verified (158 days) | S5 | 8.4, 8.0.39 | Any | Any | Severe performance regression in filesort |
115671 | 2024-07-23 9:47 | 2024-07-23 13:49 | MySQL Server: Optimizer | Verified (199 days) | S5 | 8.0.37, 8.0.39 | Any | Any | The optimizer has chosen a poor execution plan. |
115676 | 2024-07-24 4:34 | 2024-07-24 9:46 | MySQL Server: Optimizer | Verified (198 days) | S5 | 8.0.37, 8.0.39 | Any | Any | The optimizer has chosen a poor execution plan. |
115908 | 2024-08-23 5:55 | 2024-08-27 2:58 | MySQL Server: Optimizer | Duplicate (165 days) | S5 | 5.7.21,8.0.25 | Any | Any | Poor performance in scanning the entire table in non indexed field order |
116309 | 2024-10-07 10:39 | 2024-10-22 11:32 | MySQL Server: Optimizer | Verified (108 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Ubuntu | Any | Performance of TPC-H Query |
116456 | 2024-10-23 6:43 | 2024-11-06 13:57 | MySQL Server: Optimizer | Verified (99 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Any | Any | Performance of TPC-H Query 8 |
116484 | 2024-10-26 20:54 | 2024-10-31 15:06 | MySQL Server: Optimizer | Verified (99 days) | S5 | 596f0d23 (9.0.0), 9.1.0 | Any | Any | Unexpected Performance Dropdown for Query 11 in TPC-H |
116534 | 2024-11-03 10:40 | 2024-11-06 12:58 | MySQL Server: Optimizer | Verified (93 days) | S5 | 596f0d23 (9.0.0) | Any | Any | Another Performance of TPC-H Query 16 |
116612 | 2024-11-11 11:46 | 2024-11-11 14:11 | MySQL Server: Optimizer | Verified (88 days) | S5 | 8.0.40 | Any | Any | Performance degradation of distinct operator from 5.7 to 8.0 |
116773 | 2024-11-25 17:40 | 2024-11-28 8:02 | MySQL Server: Optimizer | Verified (71 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 7 |
116774 | 2024-11-25 18:00 | 2024-11-28 8:02 | MySQL Server: Optimizer | Verified (71 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 15 |
116775 | 2024-11-25 18:34 | 2024-11-28 8:00 | MySQL Server: Optimizer | Verified (71 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 16 |
116777 | 2024-11-25 19:50 | 2024-11-27 12:52 | MySQL Server: Optimizer | Verified (72 days) | S5 | 596f0d23 (9.0.0), 8.0.40 | Any | Any | Performance of TPC-DS Query 47 |
117085 | 2024-12-31 8:50 | 2024-12-31 9:32 | MySQL Server: Optimizer | Verified (38 days) | S5 | 8.0.40 | Any | x86 | Performance issue with Multi-Valued Index and ORDER BY DESC LIMIT (Reads more data than expected) |
27732 | 2007-04-10 13:18 | 2008-03-30 8:34 | MySQL Server: Optimizer | Closed (6158 days) | S1 | 5.0.56,5.1.22 | Any (windows, linux) | Any | Possible memory leak with index_merge |
59110 | 2010-12-22 9:49 | 2011-03-02 3:21 | MySQL Server: Optimizer | Closed (5091 days) | S2 | 5.6.99, 5.5, 5.1 -> | Any | Any | Memory leak of QUICK_SELECT_I allocated memory |
59308 | 2011-01-05 11:46 | 2011-02-28 20:57 | MySQL Server: Optimizer | Closed (5093 days) | S2 | 5.6.99, 5.5, 5.1 -> | Any | Any | Incorrect result for SELECT DISTINCT <col>... ORDER BY <col> DESC |
58106 | 2010-11-10 10:24 | 2011-02-16 23:44 | MySQL Server: Options | Verified (5203 days) | S3 | 5.1-bugteam | Any | Any | Wrong directory info in general_log_file/slow_query_log_file. |
69295 | 2013-05-21 16:22 | 2013-05-22 9:04 | MySQL Server: Options | Verified (4279 days) | S3 | 5.1.44, 5.6.10 | Any | Any | Slow_queries status variable incremented when it should not |
105957 | 2021-12-22 7:44 | 2021-12-22 8:01 | MySQL Server: Options | Verified (1143 days) | S3 | 5.7.35, 8.0.27 | Linux | Any | The table "slow_log" not close when config option slow_query_log set into OFF |
80989 | 2016-04-07 8:09 | 2016-04-08 1:29 | MySQL Server: Options | Duplicate (3227 days) | S2 | Any | Any | Severe performance degradation from 5.6 to 5.7 with a long query on a larg table | |
80089 | 2016-01-21 1:58 | 2016-05-09 14:52 | MySQL Server: Options | Closed (3196 days) | S3 | 5.6, 5.6.28 | Linux | Any | Memory leak from open files limit |
105442 | 2021-11-03 13:05 | 2021-11-03 14:19 | MySQL Server: Options | Verified (1192 days) | S3 | 5.7 | Any | Any | Contribution: Fix memory leak when host_cache_size is 0. |
59393 | 2011-01-10 12:47 | 2011-04-25 13:15 | MySQL Server: Options | Closed (5037 days) | S2 | 5.5.8, 5.5.9-bzr | Any (SunOS 5.10 Generic_142910-17 i86pc i386 i86pc) | Any | have_innodb=YES when mysqld started with --skip-innodb |
105933 | 2021-12-19 8:11 | 2021-12-21 8:04 | MySQL Server: Options | Verified (1144 days) | S3 | 5.7.35, 8.0.27 | Linux | Any | The table "general_log" not close when config option general_log set into OFF |
105964 | 2021-12-23 1:43 | 2021-12-23 5:06 | MySQL Server: Options | Verified (1142 days) | S3 | 5.7.35, 8.0.27 | Linux | Any | The table "general_log/slow_log" not close when config log_output set into NONE |
59860 | 2011-02-01 1:28 | 2013-02-22 3:49 | MySQL Server: Options | Closed (4368 days) | S3 | 5.1, 5.5, trunk | Any | Any | log-slow-admin-statements and log-slow-slave-statements not displayed |
96799 | 2019-09-10 0:32 | 2020-10-20 6:52 | MySQL Server: Options | Closed (1647 days) | S3 | 8.0.13 | Any | Any | Contribution by Facebook: Periodic fsync in select into outfile controlled ... |
69419 | 2013-06-07 7:04 | 2013-08-26 14:08 | MySQL Server: Options | Closed (4183 days) | S2 | 5.6.12 | Any | Any | Undocumented and untested table_open_cache table_definition_cache default change |
29921 | 2007-07-20 3:39 | 2008-03-04 22:29 | MySQL Server: Parser | Closed (6184 days) | S5 | 5.0.37 | Any | Any | MYSQLparse uses 3X more CPU in MySQL 5.0 than yyparse in MySQL 4.0 |
30237 | 2007-08-03 22:10 | 2007-10-09 17:07 | MySQL Server: Parser | Closed (6331 days) | S5 | 5.0 | Any | Any | Performance regression in boolean expressions |
30333 | 2007-08-09 14:47 | 2007-10-09 17:01 | MySQL Server: Parser | Closed (6331 days) | S5 | 4.0, 4.1, 5.0, 5.1 | Any | Any | Performance, expressions lists in the parser |
30625 | 2007-08-24 15:28 | 2007-10-09 17:05 | MySQL Server: Parser | Closed (6331 days) | S5 | 5.0, 5.1 | Any | Any | Performance, reduce depth for expressions |
76509 | 2015-03-27 14:45 | 2015-04-06 23:36 | MySQL Server: Parser | Closed (3602 days) | S3 | 5.7 | Any | Any | use atomics to avoid MUTEX CONTENTION ON LOCK_PLUGIN DUE TO QUERY REWRITE FRAMEW |
70001 | 2013-08-12 18:46 | 2017-06-23 9:11 | MySQL Server: Partitions | Closed (4111 days) | S1 | 5.6.13 | Any | Any | Partitioned tables do not use ICP - severe performance loss after partitioning |
105204 | 2021-10-13 11:22 | 2021-11-01 8:41 | MySQL Server: Partitions | Verified (1213 days) | S3 | 8.0.26 | Any | Any | ha_innopart traverse all partitions instead of only used partitions causing loss |
106039 | 2022-01-05 7:08 | 2022-01-11 6:10 | MySQL Server: Partitions | Verified (1123 days) | S5 | 8.0.27 | Any | Any | Skip using priority queue and visiting unused partitions when single partition |
113750 | 2024-01-25 6:50 | 2024-01-26 10:12 | MySQL Server: Partitions | Verified (378 days) | S2 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | stats of partitions could be empty after some kind of alter table DDL statements |
35845 | 2008-04-04 20:08 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5529 days) | S5 | 5.1.23 | Any | Any | unneccesary call to ha_start_bulk_insert for not used partitions |
67351 | 2012-10-24 8:02 | 2017-05-03 16:04 | MySQL Server: Partitions | Verified (4451 days) | S2 | 5.5.27-29.0 | Linux | Any | Cardinality samples of partitioned tables sometimes widely off |
72115 | 2014-03-24 19:29 | 2015-07-22 7:17 | MySQL Server: Partitions | Closed (3488 days) | S2 | 5.6.16 | Any | Any | Very slow create/alter table with partitions and STATS_PERSISTENT=1 |
17894 | 2006-03-03 12:00 | 2006-03-15 12:52 | MySQL Server: Partitions | Closed (6904 days) | S1 | 5.1.7 | Linux (Linux, Windows) | Any | Comparison with "less than" operator fails with Range partition |
52455 | 2010-03-30 1:54 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5230 days) | S3 | 5.1 | Any | Any | Subpar INSERT ON DUPLICATE KEY UPDATE performance with many partitions |
52517 | 2010-04-01 3:10 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5230 days) | S3 | 5.1.45 | Any | Any | Regression in ROW level replication performance with partitions |
26527 | 2007-02-21 14:49 | 2007-10-29 18:41 | MySQL Server: Partitions | Closed (6311 days) | S5 | 5.1.14-log | Linux (Ubuntu 6.10 x86_64/Windows) | Any | LOAD DATA INFILE extremely slow with partitioned table |
55506 | 2010-07-23 11:45 | 2011-02-16 23:44 | MySQL Server: Partitions | Duplicate (5311 days) | S3 | 5.1 | Any | Any | Memory leak on partition_error.test |
84107 | 2016-12-08 11:15 | 2016-12-21 10:50 | MySQL Server: Partitions | Closed (2972 days) | S3 | 5.7.16 | Any | Any | Severe slowdown on partitioned table with simple ORDER BY ASC change to DESC |
83470 | 2016-10-20 18:24 | 2017-05-16 2:53 | MySQL Server: Partitions | Closed (2824 days) | S3 | 5.7.16-debug-log | Any | Any | Reverse scan on a partitioned table does ICP check incorrectly, causing slowdown |
79145 | 2015-11-06 2:42 | 2016-02-08 12:57 | MySQL Server: Partitions | Closed (3375 days) | S3 | 5.7.10 | Any | Any | Memory Leak in Ha_innopart_share::set_v_templ partitioned on virtual column |
37252 | 2008-06-06 19:56 | 2015-02-06 19:01 | MySQL Server: Partitions | Closed (4622 days) | S3 | 5.1, 6.0 | Any | Any | Partitioning performance drops drastically with hundreds of partitions |
44059 | 2009-04-03 2:26 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5529 days) | S5 | 5.1.32, 5.1.35-bzr | Linux (CentOS 5 kernel 2.6.18-53.el5 SMP x86_64) | Any | Incorrect cardinality of indexes on a partitioned table |
48229 | 2009-10-22 13:22 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5348 days) | S5 | 5.1.37,5.1.38 | Linux (CentOS 4.4) | Any | group by performance issue of partitioned table |
105490 | 2021-11-08 11:28 | 2022-01-26 8:45 | MySQL Server: Partitions | Verified (1187 days) | S3 | 8.0.27 | Any | Any | Empty loop brings loss to performance when pruning partitions for INSERT command |
56380 | 2010-08-30 18:07 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5126 days) | S2 | 5.1.50 | Any | Any | valgrind memory leak warning from partition tests |
114300 | 2024-03-11 13:45 | 2024-03-11 14:41 | MySQL Server: Performance Schema | Verified (333 days) | S3 | 8.0 | Any | Any | The "fake index" of performance_schema.data_lock_waits causes slow sql |
69382 | 2013-06-02 19:42 | 2013-07-09 14:16 | MySQL Server: Performance Schema | Closed (4231 days) | S3 | 5.6.11 | Any | Any | Performance schema, degradation under stress when internal buffers are full |
54782 | 2010-06-24 15:31 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5301 days) | S3 | 5.5.3-m3, 5.5.4-m3 | Any | Any | Performance schema per thread accounting and thread cache |
55087 | 2010-07-08 15:38 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5307 days) | S5 | Any | Any | Performance schema: optimization of the instrumentation interface | |
55416 | 2010-07-20 21:17 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5264 days) | S1 | Any | Any | Renaming of performance_schema tables in 5.5 | |
55462 | 2010-07-21 23:22 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5285 days) | S5 | 5.5.3-m3 | Any | Any | Performance schema: reduce the overhead of PFS_events_waits::m_wait_class |
56475 | 2010-09-01 23:17 | 2011-07-22 18:21 | MySQL Server: Performance Schema | Closed (4949 days) | S3 | 5.6 | Any | Any | Missing thread states in performance_schema.THREADS / SHOW PROFILE |
59799 | 2011-01-28 18:00 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5111 days) | S3 | 5.5.6 | Any | Any | handler statistics for the performance schema engine |
70028 | 2013-08-14 8:08 | 2013-10-01 16:39 | MySQL Server: Performance Schema | Closed (4147 days) | S2 | 5.6.13 | Linux (Oracle Linux 6) | Any | P_S threads.INSTRUMENTED not set according to setup_actors |
71278 | 2014-01-02 17:22 | 2014-02-17 18:07 | MySQL Server: Performance Schema | Closed (4008 days) | S3 | 5.6 | Any | Any | NUMBER OF ROWS IN PERFORMANCE SCHEMA TABLES |
73112 | 2014-06-25 11:47 | 2016-02-23 15:52 | MySQL Server: Performance Schema | Verified (3272 days) | S3 | 5.6.16, 5.6.17, 5.6.20 | Linux | Any | Performance Schema - Statement Tables - Stored Procedures Counters are 0 |
76305 | 2015-03-13 0:13 | 2015-04-08 13:26 | MySQL Server: Performance Schema | Closed (3593 days) | S3 | 5.7.6 | Any | Any | Com_stmt_reprepare missing in Performance Schema implementation of SHOW STATUS |
76562 | 2015-04-01 15:11 | 2016-02-03 19:32 | MySQL Server: Performance Schema | Closed (3565 days) | S3 | 5.7.8 | Any | Any | Several performance schema unit tests fails |
78315 | 2015-09-03 10:15 | 2016-02-04 16:23 | MySQL Server: Performance Schema | Closed (3445 days) | S3 | 5.7.9 | Any | Any | Default value of two options in perf schema is not updated in 5.7 |
79784 | 2015-12-28 6:50 | 2016-01-21 15:06 | MySQL Server: Performance Schema | Closed (3305 days) | S3 | 5.6.24 5.7.10 | Any | Any | update setup_instruments do not affect the global mutex/rwlock/cond |
92532 | 2018-09-21 16:26 | 2021-01-19 15:13 | MySQL Server: Performance Schema | Closed (1481 days) | S3 | 8.0.11 | Any | Any | Contribution by Facebook: Performance schema for Query attributes |
97600 | 2019-11-12 20:05 | 2019-11-26 3:43 | MySQL Server: Performance Schema | Closed (1900 days) | S3 | 8.0.17 | Any | Any | Perfschema socket stats are not captured for SSL connections |
100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1647 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
101764 | 2020-11-26 0:38 | 2022-04-20 16:17 | MySQL Server: Performance Schema | Closed (1103 days) | S3 | 8.0.20 | Any | Any | Contribution by Facebook: Add CPU time to statement metrics |
108533 | 2022-09-19 12:04 | 2022-09-20 6:56 | MySQL Server: Performance Schema | Verified (871 days) | S3 | 8.0, 8.0.30 | Any | Any | NULL query text in performance schema after thread killed |
95502 | 2019-05-23 16:47 | 2019-05-23 16:52 | MySQL Server: Performance Schema | Closed (2087 days) | S2 | 5.7.20-log | CentOS (CentOS release 6.5 (Final)) | x86 (Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz) | Memory leak on memory/performance_schema/table_handles |
106939 | 2022-04-07 2:51 | 2022-05-13 10:28 | MySQL Server: Performance Schema | Closed (1001 days) | S3 | 5.7.18 | Any | Any | TRUNCATE performance_schema.accounts causes duplicated counts in global_status |
44016 | 2009-04-01 17:14 | 2011-02-16 23:43 | MySQL Server: Performance Schema | Closed (5503 days) | S3 | mysql-6.0-perf | Any | Any | performance_schema_enabled=0 at server startup has no effect |
44190 | 2009-04-09 15:17 | 2011-02-16 23:43 | MySQL Server: Performance Schema | Closed (5503 days) | S3 | mysql-6.0-perf | Any | Any | Performance schema: nanosecond and ticks timers not implemented on windows |
44210 | 2009-04-11 2:04 | 2011-02-16 23:43 | MySQL Server: Performance Schema | Closed (5452 days) | S2 | mysql-6.0-perf | Any | Any | Performance schema: pool-of-threads threads instrumentation is missing |
44710 | 2009-05-07 9:07 | 2011-02-16 23:43 | MySQL Server: Performance Schema | Closed (5503 days) | S3 | 6.0-perfschema | Linux | Any | assertion failure in mdl when server starts, related to performance schema |
45090 | 2009-05-26 7:58 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5503 days) | S3 | 6.0.12-alpha-log-perfschema | Any | Any | performance schema is enabled at startup |
45510 | 2009-06-15 22:09 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5503 days) | S3 | mysql-6.0-perfschema | Any | Any | Performance schema: STAT and FSTAT are not generating waits |
45956 | 2009-07-06 0:03 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5503 days) | S3 | 6.0.12-alpha | Any | Any | Performance schema: exotic mysqld startup, bad results |
48631 | 2009-11-09 9:26 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5503 days) | S3 | mysql-trunk-perfschema | Any | Any | Performance schema: unit test failures |
51295 | 2010-02-18 20:27 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5448 days) | S2 | mysql-next-mr, 5.5.99-m3 | Any | Any | Build warnings in mdl.cc |
51612 | 2010-03-01 16:22 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5452 days) | S3 | mysql-next-mr, 5.5.99-m3 | Any | Any | Un initialized locker_lost variable in pfs_instr.cc |
52502 | 2010-03-31 12:56 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5301 days) | S1 | mysql-trunk (5.5.3) | Any | Any | Performance schema does not start with large mutex_instance buffers |
53874 | 2010-05-21 6:56 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5266 days) | S3 | 5.5.3-m3, 5.5.4-m3 | Any | Any | SETUP_INSTRUMENTS.TIMED='NO' should not change TIMER_WAIT in aggregations |
56324 | 2010-08-27 11:06 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5209 days) | S3 | next-mr, next-mr-bugfixing | Any | Any | Race Condition while shutting down MySQL: "PSI_server" |
57106 | 2010-09-29 16:04 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5172 days) | S3 | 5.6 | Any | Any | Robustness of memcpy calls in the performance schema |
59740 | 2011-01-26 14:07 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5111 days) | S3 | 5.6 | FreeBSD | Any | Performance schema test failures on freebsd |
67098 | 2012-10-05 10:19 | 2012-12-13 16:57 | MySQL Server: Performance Schema | Closed (4439 days) | S3 | 5.6.5, 5.7.0 | Any | Any | performance schema shows stray temporray tables |
68009 | 2013-01-02 9:22 | 2022-11-05 12:45 | MySQL Server: Performance Schema | Duplicate (4411 days) | S2 | 5.5.28, 5.5.29 | Any | Any | Floating point exception in "insert_events_waits_history_long" |
68413 | 2013-02-18 2:45 | 2013-09-25 2:58 | MySQL Server: Performance Schema | Verified (4153 days) | S5 | 5.6.10, 5.6.13 | Any | Any | performance_schema overhead is at least 10% |
70018 | 2013-08-13 19:42 | 2013-10-07 18:18 | MySQL Server: Performance Schema | Closed (4141 days) | S5 | 5.6 / 5.7 | Any | Any | PFS Overhead on frequent connect/disconnect |
71298 | 2014-01-05 12:31 | 2014-03-29 18:21 | MySQL Server: Performance Schema | Closed (4018 days) | S3 | 5.6.15 | Any | Any | "Waiting to get readlock" stage is not used in 5.6 any more |
71808 | 2014-02-23 12:38 | 2018-01-31 14:40 | MySQL Server: Performance Schema | Closed (2564 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Remove the TICK timer in performance_schema |
74546 | 2014-10-24 11:31 | 2014-10-24 11:43 | MySQL Server: Performance Schema | Closed (3759 days) | S3 | Any | Any | PERFORMANCE SCHEMA QUERY ON EVENTS_STATEMENTS_CURRENT WRONG WITH ORDER BY | |
75765 | 2015-02-04 15:17 | 2015-03-10 13:30 | MySQL Server: Performance Schema | Closed (3622 days) | S3 | 5.6.23 | Any | Any | Performance Schema statement digest generation is broken with null values |
77620 | 2015-07-05 15:29 | 2018-02-18 18:29 | MySQL Server: Performance Schema | Closed (3416 days) | S3 | 5.5, 5.6, 5.7 | Any | ARM | No cycle timer implementation for AArch64 |
78068 | 2015-08-14 12:21 | 2015-08-18 13:08 | MySQL Server: Performance Schema | Verified (3464 days) | S3 | 5.7.8 | Any | Any | replication_* tables miss information about binary log position and other |
79487 | 2015-12-02 6:21 | 2016-01-15 13:07 | MySQL Server: Performance Schema | Verified (3354 days) | S3 | 5.6, 5.7 | Any | Any | Provide non-Windows implementations for LF_BACKOFF |
79934 | 2016-01-12 10:48 | 2016-02-19 17:58 | MySQL Server: Performance Schema | Closed (3278 days) | S3 | 5.7.11 | Any | Any | i_perfschema.table_leak random result failure |
82663 | 2016-08-20 5:12 | 2017-06-27 7:40 | MySQL Server: Performance Schema | Verified (3087 days) | S1 | 5.7.13, 5.7.14 | Any | Any | mysqld hangs when accessing Performance Schema tables |
83912 | 2016-11-21 15:28 | 2020-03-09 16:52 | MySQL Server: Performance Schema | Verified (2998 days) | S3 | 5.6, 5.7, 5.6.34 | Any | Any | Time spent sleeping before entering InnoDB is not measured/reported separately |
84457 | 2017-01-10 12:53 | 2017-02-16 14:10 | MySQL Server: Performance Schema | Closed (2913 days) | S3 | 5.6.35 | Linux | Any | Performance Schema 5.6.35 unittest pft-t failing |
84786 | 2017-02-02 8:17 | 2017-02-03 16:04 | MySQL Server: Performance Schema | Closed (2926 days) | S1 | 5.7.17-11 | Any | Any | --performance-schema-digests-size=1 leads to SIGSEGV |
92364 | 2018-09-11 12:06 | 2019-02-28 18:07 | MySQL Server: Performance Schema | Closed (2171 days) | S3 | 5.7.22, 8.0.12 | Any | Any | events_transactions_summary_global_by_event_name not working as expected |
93281 | 2018-11-22 4:03 | 2018-12-17 23:09 | MySQL Server: Performance Schema | Closed (2261 days) | S1 | 8.0.12 | Any | Any | Odd memory load/increase when using --performance-schema-max-digest-length=large |
94925 | 2019-04-06 0:15 | 2019-04-24 13:37 | MySQL Server: Performance Schema | Verified (2116 days) | S3 | 8.0.15 | Any | Any | Wrong Query Sample Text in Performance Query |
98545 | 2020-02-10 23:45 | 2022-05-02 7:22 | MySQL Server: Performance Schema | Closed (1012 days) | S3 | 8.0.19 | Any | Any | Perfschema tables are not collation aware |
99989 | 2020-06-26 1:06 | 2021-01-10 22:04 | MySQL Server: Performance Schema | Closed (1489 days) | S3 | 8.0.x, 8.0.20 | Any | Any | Inconsistency when joining Perf Schema schema tables when PK is larger than 48 c |
100336 | 2020-07-27 15:58 | 2020-07-28 13:45 | MySQL Server: Performance Schema | Verified (1655 days) | S3 | 5.7 | Any | Any | performance_schema.status_by_thread table not populating on Linux |
100624 | 2020-08-24 15:05 | 2021-02-03 17:46 | MySQL Server: Performance Schema | Closed (1465 days) | S3 | 5.7.30, 8.0.21, 5.7.31 | Any | Any | Total memory allocation for P_S is different in different sources |
100962 | 2020-09-26 5:17 | 2020-10-26 11:42 | MySQL Server: Performance Schema | Analyzing (1565 days) | S3 | 5.7 | Any | Any | memory_summary_%_by_event_name Have different values |
101018 | 2020-10-01 9:28 | 2020-10-09 15:44 | MySQL Server: Performance Schema | Closed (1582 days) | S5 | 8.0 | Any | Any | High contention on last_value in my_timer_microseconds |
104643 | 2021-08-17 14:11 | 2021-10-06 16:24 | MySQL Server: Performance Schema | Closed (1220 days) | S3 | 8.0.26 | Any | Any | Defaults in performance schema tables incompatible with sql_mode |
108750 | 2022-10-12 10:08 | 2022-10-14 15:56 | MySQL Server: Performance Schema | Closed (847 days) | S3 | 8.0.26 | Any | Any | TABLE ACCESS SERVICE INDEX READ MAP ISSUES |
110555 | 2023-03-29 22:22 | 2024-01-17 17:33 | MySQL Server: Performance Schema | Closed (445 days) | S3 | 8.0.32 | Any | Any | Some performance schema tables return invalid rows |
111860 | 2023-07-24 8:59 | 2023-09-18 10:17 | MySQL Server: Performance Schema | Closed (521 days) | S3 | Any | Any | shutdown plugin core when init_events_waits_history_long failed | |
112035 | 2023-08-10 19:33 | 2024-09-19 9:05 | MySQL Server: Performance Schema | Closed (141 days) | S2 | 8.0.37, 8.4.0 | Any | Any | Materializing performance_schema.data_locks can lead to excessive mem usage/OOM |
113761 | 2024-01-25 13:33 | 2024-09-24 12:57 | MySQL Server: Performance Schema | Closed (141 days) | S5 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | Access performance_schema.data_locks causes SQL execution stuck |
114545 | 2024-04-03 17:26 | 2024-04-04 9:40 | MySQL Server: Performance Schema | Verified (309 days) | S3 | 8.0.35, 8.0.36 | Any | Any | performance_schema.processlist tuncates query info |
117176 | 2025-01-10 6:20 | 2025-01-10 7:00 | MySQL Server: Performance Schema | Verified (28 days) | S3 | 8.0.40 | Any | Any | The stages about DDL in PFS.events_stages_history_long are wrong |
112621 | 2023-10-04 16:39 | 2023-11-20 15:30 | MySQL Server: Performance Schema | Closed (445 days) | S5 | 8.0.34 | Any | Any | Performance degradation from 8.0.30 onwards related to performance_schema |
78975 | 2015-10-27 8:02 | 2016-06-18 21:28 | MySQL Server: Performance Schema | Closed (3192 days) | S3 | 8.0.0-m17 | Any | Any | SYSSCHEMA.PR_STATEMENT_PERFORMANCE_ANALYZER TEST still FAILING ON PB2 ON WINDOWS |
78303 | 2015-09-02 10:02 | 2016-09-22 7:50 | MySQL Server: Performance Schema | Verified (3446 days) | S3 | 5.7 | Any | Any | Add some DNS latency timings to performance_schema (host_cache?) |
89379 | 2018-01-24 11:41 | 2022-03-31 8:21 | MySQL Server: Performance Schema | Verified (2571 days) | S5 | 5.7.20, 5.7.21 | Any | Any | summary_by_user tables get extremely slow with many users. |
52134 | 2010-03-17 11:08 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5301 days) | S3 | mysql-next-mr, 5.6.99-m3 | Any | Any | performance schema file io, symlink in path |
69727 | 2013-07-11 18:41 | 2016-02-25 12:24 | MySQL Server: Performance Schema | Closed (4137 days) | S3 | 5.6.11 | Windows | Any | --performance_schema_instrument value quoting is problematic |
51447 | 2010-02-24 7:08 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5441 days) | S2 | mysql-5.5.99 (Celosia) | Any | Any | performance schema evil twin files |
77863 | 2015-07-28 19:00 | 2015-07-30 13:05 | MySQL Server: Performance Schema | Closed (3480 days) | S5 | 5.6.26 | Any | Any | slowdown caused by memset in sql_digest_storage.reset() |
112959 | 2023-11-03 17:53 | 2023-11-07 10:41 | MySQL Server: Performance Schema | Verified (459 days) | S3 | 8.0 | Any | Any | Wrong rows examined in P_S and slow log for Index Merge. |
53696 | 2010-05-17 11:07 | 2011-02-16 23:44 | MySQL Server: Performance Schema | Closed (5153 days) | S3 | 5.6.99 | Any | Any | Performance schema engine violates the PSEA API by calling my_error() |
70577 | 2013-10-09 21:47 | 2013-10-15 18:19 | MySQL Server: Performance Schema | Closed (4133 days) | S3 | 5.6.14 | Any | Any | Read/Write mutexes on Binlog delegate classes are not counted on perf schema |
77577 | 2015-07-01 10:51 | 2015-07-15 12:18 | MySQL Server: Performance Schema | Closed (3496 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | setup_timers initialization assumes CYCLE timer is always available |
77944 | 2015-08-05 7:11 | 2015-08-21 18:43 | MySQL Server: Performance Schema | Closed (3458 days) | S3 | 5.7.8-rc, 5.7.9 | Linux | Any | performance_schema_instrument='%=OFF', not disable all instruments |
80780 | 2016-03-17 11:55 | 2016-04-14 0:45 | MySQL Server: Performance Schema | Closed (3237 days) | S3 | 5.7 | Any | Any | Add Performance Schema / sys Schema Memory Monitoring Example |
101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1541 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
111310 | 2023-06-07 6:51 | 2023-06-08 8:30 | MySQL Server: Prepared statements | Verified (610 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | Prepared statement with CTE memory leak |
73056 | 2014-06-19 21:34 | 2018-03-15 14:17 | MySQL Server: Prepared statements | Closed (3255 days) | S5 | 5.7, 5.7.8 | Any | Any | Prepared Statements ABSURDLY SLOW due to inefficient query creation for logging |
67676 | 2012-11-22 6:37 | 2014-07-14 12:23 | MySQL Server: Prepared statements | Closed (4337 days) | S2 | 5.6.7 | Any | Any | prepared statement is very slow while binlog was enabled |
29687 | 2007-07-10 10:09 | 2007-07-23 0:47 | MySQL Server: Prepared statements | Closed (6409 days) | S1 | 5.1.17, 5.1.20 | Any | Any | mysql_stmt_store_result memory leak in libmysqld |
62117 | 2011-08-08 19:53 | 2011-08-10 10:47 | MySQL Server: Prepared statements | Duplicate (4930 days) | S2 | 5.1.58-enterprise | Solaris | Any | Large Batch Update causes apparent large memory leaks and crashes server |
38626 | 2008-08-07 11:28 | 2008-08-07 12:36 | MySQL Server: Prepared statements | Duplicate (6028 days) | S3 | 5.0.66a | Any | Any | memory leak with materialized cursor and prepared statement |
114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (351 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
38551 | 2008-08-04 22:08 | 2011-02-16 23:43 | MySQL Server: Query Cache | Closed (5547 days) | S5 | 5.1, 6.0 | Any | Any | RBR/MBR + Query Cache + "invalidating query cache entries (table)" => slow slave |
64924 | 2012-04-10 9:03 | 2015-03-15 20:45 | MySQL Server: Query Cache | Duplicate (4655 days) | S3 | 5.1.61 | Linux (2.6.32-5-amd64 #1 SMP) | Any | Cacheing long SELECT statement does too many prunes |
60801 | 2011-04-08 3:51 | 2011-05-09 3:59 | MySQL Server: Query Cache | Closed (5023 days) | S2 | mysql Ver 14.12 Distrib 5.0.45 | Linux (Red Hat Enterprise Linux Server release 5.3 ) | Any | Select Query is too much slow and taking upto 23 seconds to complete |
47529 | 2009-09-22 22:15 | 2022-12-04 20:45 | MySQL Server: Query Cache | Duplicate (5174 days) | S5 | 5.1.38, 5.1.39 | Any | Any | query cache performance is bad on multi-core servers |
73648 | 2014-08-19 22:10 | 2018-07-06 3:09 | MySQL Server: Row Based Replication ( RBR ) | Verified (2555 days) | S2 | Server version: 5.6.16-log MySQL Communi, 5.6.39 | Linux | Any | innodb table replication is very slow with some of the partioned table |
99140 | 2020-04-01 6:53 | 2020-05-18 12:10 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (1772 days) | S3 | 8.0.19 | CentOS | x86 | 8.0 single thread applying performance regression of update_non_index |
81500 | 2016-05-19 9:10 | 2018-04-30 11:20 | MySQL Server: Row Based Replication ( RBR ) | Closed (2475 days) | S3 | 5.7+ | Any | Any | dead branch in search_key_in_table() |
104546 | 2021-08-05 9:50 | 2024-01-30 15:57 | MySQL Server: Row Based Replication ( RBR ) | Verified (374 days) | S5 | 8.0.26 | Ubuntu (18.04.5 LTS) | x86 (Skylake-SP) | MySQL 8.0.26 single thread replication performance is slower than MySQL 5.7.35. |
113251 | 2023-11-28 11:54 | 2023-11-29 9:24 | MySQL Server: Row Based Replication ( RBR ) | Verified (436 days) | S3 | MySQL8.0 | Any | Any | the slow log in slave is logged ,when binlog_format is row |
20198 | 2006-06-01 12:39 | 2016-10-16 20:45 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (6824 days) | S3 | 5.1 source | Any | RBR injector is too slow | |
35843 | 2008-04-04 19:56 | 2008-10-17 17:23 | MySQL Server: Row Based Replication ( RBR ) | Closed (5957 days) | S3 | 5.1.23 | Any | Any | Slow replication slave when using partitioned myisam table |
38207 | 2008-07-17 16:56 | 2012-05-18 20:19 | MySQL Server: Row Based Replication ( RBR ) | Duplicate (6028 days) | S5 | 5.1.25 | Linux (x86_64) | Any | Row-based Replication (RBR) is CPU bound (invalidating query cache) |
82003 | 2016-06-25 16:15 | 2016-08-18 11:12 | MySQL Server: Row Based Replication ( RBR ) | Closed (3095 days) | S3 | 5.7.13 | Any | Any | Rows event are decoded one byte at a time |
39106 | 2008-08-28 20:09 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Closed (5956 days) | S3 | 5.1 | Any | Any | SUPER is not required to change binlog format for session |
46554 | 2009-08-04 19:50 | 2011-02-16 23:44 | MySQL Server: Row Based Replication ( RBR ) | Closed (5184 days) | S3 | 6.0-codebase, mysql-next-mr-wl5092 | Any | Any | RBR: pending rows event can be flushed too soon sometimes. |
191 | 2003-03-25 14:24 | 2003-04-18 13:56 | MySQL Server: Replication | Closed (7966 days) | S3 | 3.23 | Linux (Linux at least) | Any | Many connections from the slave to the master cause "alarm queue is full" |
18280 | 2006-03-16 13:27 | 2006-03-18 18:03 | MySQL Server: Replication | Closed (6901 days) | S3 | 5.1.8 | Any (ALL) | Any | RBR: Extreneous table maps when writing to slow_log and general_log |
30703 | 2007-08-29 17:26 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5566 days) | S3 | 5.0 (all) | Any | Any | SHOW STATUS LIKE 'Slave_running' is not compatible with `SHOW SLAVE STATUS' |
37578 | 2008-06-23 7:00 | 2016-10-16 20:45 | MySQL Server: Replication | Verified (6071 days) | S3 | 5.1, 5.0, 6.0 | Any | Any | Execute Stored Functions Without Prelocks |
48632 | 2009-11-09 9:38 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5345 days) | S3 | All | Any | Any | Fix for Bug #23300 Has Not Been Backported To 5.x Release |
64503 | 2012-03-01 5:27 | 2012-05-02 11:21 | MySQL Server: Replication | Closed (4713 days) | S2 | 5.1 | Any | Any | mysql frequently ignores --relay-log-space-limit |
69341 | 2013-05-29 0:55 | 2016-04-07 5:46 | MySQL Server: Replication | Closed (4235 days) | S5 | 5.6.11 | Any | Any | semi-sync replication is very slow with many clients |
74233 | 2014-10-06 10:40 | 2017-07-26 22:46 | MySQL Server: Replication | Closed (2758 days) | S3 | 5.6.22,5.5 5.6 | Any | Any | Slave's slow log has empty BEGINs for RBR events |
74607 | 2014-10-28 16:25 | 2015-09-14 15:43 | MySQL Server: Replication | Closed (3612 days) | S2 | 5.6.21 | Any | Any | slave io_thread may get stuck when using GTID and low slave_net_timeouts |
75525 | 2015-01-16 8:59 | 2015-07-01 15:11 | MySQL Server: Replication | Closed (3509 days) | S2 | 5.6.22 | Any | Any | MTS STOP SLAVE takes way too long (when worker threads are slow) |
75767 | 2015-02-04 15:33 | 2015-05-21 22:39 | MySQL Server: Replication | Closed (3551 days) | S2 | 5.7 | Any | Any | set gtid_purged should not rotate binlog |
88720 | 2017-11-30 14:52 | 2018-02-24 10:49 | MySQL Server: Replication | Verified (2625 days) | S3 | 5.6, 5.7, 8.0.3, 5.6.38, 5.7.20 | Any | Any | Inconsistent and unsafe FLUSH behavior in terms of replication |
99006 | 2020-03-20 11:45 | 2020-04-16 10:01 | MySQL Server: Replication | Verified (1760 days) | S3 | 5.7 and 8.0 | Any | Any | GTID Synchronisation speed when doing START SLAVE |
42757 | 2009-02-11 12:01 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5471 days) | S3 | Any | Any | Redundant use of LOCK_log in MYSQL_BIN_LOG::write(Log_event*) | |
43426 | 2009-03-05 16:59 | 2014-01-15 15:39 | MySQL Server: Replication | Closed (4041 days) | S5 | 5.0 | Any | Any | Simple performance changes for replication |
45108 | 2009-05-26 21:26 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5706 days) | S3 | 6.0.11 | Any | Any | Slave skip counter not working as expected on debian platform |
47972 | 2009-10-10 21:36 | 2023-02-12 20:45 | MySQL Server: Replication | Duplicate (4943 days) | S2 | 5.1.40 | Any | Any | Change in MBR algorithm causes replication performance degradation |
52224 | 2010-03-19 15:17 | 2016-10-16 20:45 | MySQL Server: Replication | Verified (5436 days) | S3 | Any | Any | replication of CREATE TEMPOARARY TABLE should be optional | |
57275 | 2010-10-06 8:53 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5147 days) | S3 | 5.5, next-mr | Any | Any | binlog_cache_size affects trx- and stmt-cache and gets twice the expected memory |
72640 | 2014-05-14 6:05 | 2014-07-21 15:34 | MySQL Server: Replication | Closed (3867 days) | S3 | 5.7 | Any | Any | rpl.rpl_circular_for_4_hosts fails with result mismatch nondeterministic results |
72680 | 2014-05-19 12:39 | 2014-05-20 8:36 | MySQL Server: Replication | Verified (3916 days) | S3 | 5.6.17 | Any | Any | Make changing MASTER_AUTO_POSITION = 0 user-friendly and document behaviour |
74278 | 2014-10-08 15:38 | 2015-08-21 9:31 | MySQL Server: Replication | Verified (3458 days) | S3 | 5.6.17, 5.6.26 | Any | Any | tĥread_id title in binary log output is wrong. Should be process(list)_id |
74328 | 2014-10-11 4:54 | 2016-12-12 4:38 | MySQL Server: Replication | Closed (3630 days) | S3 | 5.7.5 | Any | Any | serious tps decline if gtid is enabled in 5.7 |
74423 | 2014-10-16 22:36 | 2016-02-02 19:15 | MySQL Server: Replication | Closed (3529 days) | S3 | 5.7+ | Any | Any | RECEIVED_TRANSACTION_SET field on replication_connection_status shows garbage |
75299 | 2014-12-23 15:45 | 2017-03-23 12:11 | MySQL Server: Replication | Duplicate (2934 days) | S3 | 5.6 | Any | Any | group commit with GTID enabled need more optimization |
75570 | 2015-01-21 7:52 | 2016-02-20 17:43 | MySQL Server: Replication | Closed (3574 days) | S2 | 5.6.20 | Linux | Any | semi-sync replication performance degrades with a high number of threads |
76049 | 2015-02-25 15:13 | 2015-02-25 21:50 | MySQL Server: Replication | Verified | S3 | 5.6.22 | Any | Any | Filtered replication events do not reset the System lock thread state |
78264 | 2015-08-28 16:11 | 2016-04-27 15:05 | MySQL Server: Replication | Closed (3438 days) | S3 | 5.7.6 | Any | Any | DO NOT ALLOCATE MEMORY ON GR PLUGIN P_S INTERFACE IMPLEMENTATION |
81910 | 2016-06-17 16:35 | 2016-11-02 13:34 | MySQL Server: Replication | Closed (3087 days) | S3 | 5.7.14 | Any | Any | WRITE SET HASHES SHOULD HAVE A 64BITS OPTION TO REDUCE WRITE CONFLICTS |
82422 | 2016-08-03 11:27 | 2017-01-26 19:15 | MySQL Server: Replication | Closed (2975 days) | S3 | 5.7.14 | Any | Any | GTIDS REDUCE PERFORMANCE ON WORKLOADS WITH MANY SMALL TRANSACTIONS |
87249 | 2017-07-30 0:44 | 2024-07-01 18:59 | MySQL Server: Replication | Verified (2598 days) | S2 | Any | Any | Relay logs shouldn't be purged if options unrelated in CHANGE MASTER is executed | |
94360 | 2019-02-16 4:44 | 2022-02-16 18:29 | MySQL Server: Replication | Closed (1095 days) | S3 | 8.0.13 | Any | Any | Contribution by Facebook: Don't force flush relay log info |
105924 | 2021-12-16 20:40 | 2022-07-25 15:16 | MySQL Server: Replication | Closed (928 days) | S5 | 8.0.22, 8.0.27 | Any | Any | SHOW SLAVE STATUS became expensive for Replica->Slave column name conversions |
110889 | 2023-05-03 5:41 | 2023-05-03 6:07 | MySQL Server: Replication | Verified (646 days) | S5 | 8.0.32 | Any | Any | binlog rotate optimize |
113187 | 2023-11-22 16:24 | 2024-06-06 3:40 | MySQL Server: Replication | Verified (439 days) | S5 | 8.0 and above | Any | Any | replica SQL thread purge applied relay logs blocked commit on source node |
114310 | 2024-03-12 4:14 | 2024-03-19 7:24 | MySQL Server: Replication | Verified (332 days) | S3 | 8.0.33 | Any | Any | Master_compression_algorithm output is wrong |
45014 | 2009-05-21 17:57 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5728 days) | S3 | 5.1.34-log | Any | Any | log-slow-slave-statements does not work in in 5.1.34 |
45136 | 2009-05-27 15:18 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5735 days) | S3 | 5.1.34-log | Any | Any | log-slow-slave-statements doesn't work in 5.1.34 |
50620 | 2010-01-26 11:36 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5345 days) | S3 | 5.5.99, next-mr, 5.1 | Any | Any | Adding an index to a table prevents slave from logging into slow log |
57899 | 2010-11-01 15:46 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5146 days) | S3 | 5.5 | Linux (SUSE 11 64-bit) | Any | Certain reserved words should not be reserved |
40337 | 2008-10-27 3:05 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5566 days) | S5 | 5.0, 5.1, 6.0 | Any | Any | Fsyncing master and relay log to disk after every event is too slow |
77778 | 2015-07-19 5:57 | 2017-03-31 17:24 | MySQL Server: Replication | Closed (2870 days) | S3 | 5.6.25 | Any | Any | tuning the log_lock contention for IO_THREAD and SQL_THREAD in rpl_slave.cc |
23335 | 2006-10-16 14:16 | 2007-09-05 20:45 | MySQL Server: Replication | Closed (6365 days) | S2 | 5.1.12 | Linux (Linux 32 Bit) | Any | InnoDB hangs if BLOBS and BINLOG are used during new performance test |
80651 | 2016-03-08 3:45 | 2016-04-07 5:46 | MySQL Server: Replication | Duplicate (3228 days) | S3 | 5.5 5.6 | Any | Any | larget rpl_semi_sync_master_timeout will affect performance |
96985 | 2019-09-24 7:17 | 2019-10-24 18:05 | MySQL Server: Replication | Verified (1933 days) | S5 | 5.7.22;8.0.11 | Any | Any | MySQL group replication pipeline memory reuse |
98070 | 2019-12-25 12:33 | 2020-01-06 8:51 | MySQL Server: Replication | Verified (1870 days) | S5 | 8.0.18 | Any | Any | Optimize write performance when group commit |
101717 | 2020-11-23 12:03 | 2020-12-15 12:53 | MySQL Server: Replication | Verified (1519 days) | S2 | 8.0, 8.0.22 | Any | Any | Poor performance on a GTID slave when log_slave_updates is disabled |
113564 | 2024-01-05 10:49 | 2024-11-07 14:39 | MySQL Server: Replication | Verified (241 days) | S5 | 8.0 | Any (>= glibc 2.25 ) | Any | write-only mode performance decreases by 15% in heavy workload |
15132 | 2005-11-22 12:55 | 2005-11-22 14:20 | MySQL Server: Replication | Closed (7017 days) | S3 | 5.0-wl1012 | Linux (linux) | Any | RBR: memory leak when updating large rows |
16175 | 2006-01-04 7:43 | 2006-03-02 15:13 | MySQL Server: Replication | Closed (6917 days) | S3 | 5.0 | Any | memory leak in rpl_trigger.test | |
48542 | 2009-11-04 18:43 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5446 days) | S3 | 5.1.39, 5.1.40, 5.1.41 | Any | Any | Implicit drops on temporary tables aren't always replicated to slaves |
48993 | 2009-11-23 13:27 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5345 days) | S3 | 5.1.41, 5.1.44-bzr,mysql-5.5.99-m3 | Linux (32-bit, Mac OS X) | Any | valgrind errors in mysqlbinlog |
56649 | 2010-09-08 13:56 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5169 days) | S2 | trunk, 5.6 | Any | Any | Valgrind warnings for memory leak in semisync plugin (Delegate class) |
56650 | 2010-09-08 13:56 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5169 days) | S2 | trunk, 5.6 | Any | Any | Valgrind warnings for memory leak in semisync plugin (MYSQL object not freed) |
72885 | 2014-06-05 7:50 | 2018-08-26 20:45 | MySQL Server: Replication | Duplicate (3600 days) | S1 | 5.6.17 | Linux (Red Hat Enterprise Linux Server release 6.3) | Any | MySQL 5.6 memory leak |
81330 | 2016-05-05 19:41 | 2020-02-04 17:19 | MySQL Server: Replication | Verified (1968 days) | S2 | 5.6.29, 5.7.17, 8.0.16 | Any | Any | circular semisync replication fails on msr (and slow without msr) |
85251 | 2017-03-01 13:16 | 2017-10-27 8:22 | MySQL Server: Replication | Closed (2688 days) | S2 | 5.7.17, 8.0.0 | Any | Any | Memory leak in master-master GTID replication with sync_relay_log_info |
115203 | 2024-06-03 17:34 | 2024-06-10 23:09 | MySQL Server: Replication | Verified (249 days) | S3 | 8.4.0, 8.0.37 | Any | Any | Empty "use ;" on replica in slow query log file. |
67983 | 2012-12-28 16:39 | 2013-01-31 9:00 | MySQL Server: Replication | Closed (4390 days) | S1 | 5.5.25a | Any | Any | Memory leak on filtered slave |
9141 | 2005-03-12 9:11 | 2005-07-26 13:47 | MySQL Server: Replication | Closed (7136 days) | S3 | 4.1.10 | Any (any) | Any | 4.1 does not log into slow log ALTER, OPTIMIZE and ANALYZE statements |
109290 | 2022-12-06 8:28 | 2023-01-13 6:20 | MySQL Server: Replication | Verified (756 days) | S5 | 5.7.39 | Ubuntu | x86 | WRITESET causing performance issue for replication on a replica |
114361 | 2024-03-15 1:53 | 2024-08-14 9:34 | MySQL Server: Replication | Verified (326 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
26489 | 2007-02-20 6:14 | 2022-05-20 12:03 | MySQL Server: Replication | Closed (6211 days) | S2 | 5.0.27 & 5.0.37, 5.1.22 | Any (Linux, Win32) | Any | Corruption in relay logs |
71197 | 2013-12-21 8:48 | 2015-01-05 2:17 | MySQL Server: Replication | Closed (4006 days) | S2 | 5.6.15, 5.6.14, 5.6.13, 5.6.16, 5.7.3 | Linux | Any | mysql slave sql thread memory leak |
71425 | 2014-01-20 14:46 | 2014-07-14 16:32 | MySQL Server: Replication | Duplicate (4033 days) | S1 | 5.6 | Any | Any | MySQL 5.6 memory leak |
85371 | 2017-03-08 10:46 | 2018-01-18 10:36 | MySQL Server: Replication | Closed (2632 days) | S2 | 5.7.17 | Any | Any | Memory leak in multi-source replication when binlog_rows_query_log_events=1 |
87008 | 2017-07-11 9:23 | 2017-07-14 10:20 | MySQL Server: Replication | Duplicate (2765 days) | S3 | 5.7.18 | Any | Any | Becuse using "xa commit one phase" in master DB, slave have memory leak |
89596 | 2018-02-09 4:17 | 2018-02-09 12:55 | MySQL Server: Replication | Verified (2555 days) | S3 | 8.0.4 | Ubuntu (17.10) | Any | __tls_get_addr leak on Ubuntu 17.10 |
73018 | 2014-06-17 3:20 | 2015-06-22 10:02 | MySQL Server: Replication | Verified (3518 days) | S5 | 5.6 | Any | Any | improve performance when binlog_order_commits=0 and sync_binlog >1 |
83270 | 2016-10-05 14:13 | 2017-04-11 7:25 | MySQL Server: Replication | Closed (2859 days) | S5 | 5.7.15 | Any | Any | Performance degradation when the server has many gtids |
106116 | 2022-01-08 15:54 | 2022-10-18 0:12 | MySQL Server: Replication | Closed (843 days) | S5 | 8.0 | Any | Any | binlog rotation impact performance |
81630 | 2016-05-28 5:46 | 2016-08-31 6:30 | MySQL Server: Replication | Verified (3082 days) | S5 | 5.7.12 | Any | Any | MySQL 5.7 is 37-45% slower then 5.6 when using binlogging due to defaults change |
81694 | 2016-06-02 16:42 | 2016-11-02 13:31 | MySQL Server: Replication | Closed (3105 days) | S3 | Any | Any | CHANNEL SERVICE INTERFACE HAS NO FUNCTION TO GET RETRIEVED GTID SET | |
85352 | 2017-03-08 0:44 | 2017-08-14 12:36 | MySQL Server: Replication | Closed (2734 days) | S5 | 5.6, 5.7, 5.6.35 | Any | Any | Replication regression with RBR and partitioned tables |
92964 | 2018-10-26 11:57 | 2020-09-18 19:38 | MySQL Server: Replication | Closed (1603 days) | S5 | 5.7.23 | Debian (8.0, 9.0) | x86 | Slave performance degrades over time |
107991 | 2022-07-27 2:02 | 2024-10-09 6:02 | MySQL Server: Replication | Verified (473 days) | S2 | 8.0.25 | Any | Any | Clone_persist_gtid causes memory leak |
23300 | 2006-10-15 6:00 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5345 days) | S3 | 4.1+ | Any (*) | Any | Slow query log on slave does not log slow replicated statements |
27492 | 2007-03-28 9:05 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (5951 days) | S3 | 5.0.40-BK, 5.0.37 | Any | Any | Replication queries are not logged in slow query log |
34582 | 2008-02-15 10:35 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5529 days) | S2 | 5.0.46-enterprise-gpl-log | Any | Any | FLUSH LOGS does not close and reopen the binlog index file |
94994 | 2019-04-12 3:06 | 2019-07-25 11:25 | MySQL Server: Storage Engines | Closed (2024 days) | S2 | 8.0.15 | Linux | x86 | Memory leak detect on temptable storage engine |
105982 | 2021-12-27 8:11 | 2022-01-03 8:02 | MySQL Server: Storage Engines | Verified (1131 days) | S5 | all, 5.7, 8.0 | Linux | Any | hard-coded libaio API parameter may not helpful to performance |
98739 | 2020-02-25 18:27 | 2020-06-11 17:21 | MySQL Server: Storage Engines | Closed (1702 days) | S3 | 8.0.19 | Any | Any | TempTable storage engine slow if mmap is required |
90987 | 2018-05-23 10:03 | 2018-06-05 14:50 | MySQL Server: Storage Engines | Verified (2443 days) | S5 | 5.7.17 | Any | Any | partition table index next same scan ineffective |
106958 | 2022-04-08 9:35 | 2022-04-11 14:37 | MySQL Server: SYS Schema | Verified (1033 days) | S3 | 8.0.28 | CentOS (CentOS Stream release 8) | x86 (Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz) | Querying the user_summary views in sys schema is extremely slow |
81564 | 2016-05-24 8:23 | 2016-08-01 12:35 | MySQL Server: SYS Schema | Closed (3144 days) | S3 | 5.7.12 | Any | Any | ps_setup_show_enabled and ps_setup_show_disabled and company issues |
86660 | 2017-06-12 16:02 | 2017-06-12 16:35 | MySQL Server: SYS Schema | Verified (2797 days) | S3 | 1.5.1 | Any | Any | schema_redundant_indexes says longer but non-unique index is redundant |
98435 | 2020-01-30 4:03 | 2020-01-30 6:34 | MySQL Server: SYS Schema | Verified (1835 days) | S3 | 8.0.19 | Any | Any | schema_table_statistics io statistics does not work with partitioned tables |
81699 | 2016-06-03 4:35 | 2016-06-14 7:49 | MySQL Server: SYS Schema | Verified (3160 days) | S3 | 5.7.12, 5.7.13 | Any | Any | ps_statement_avg_latency_histogram often fails to draw the point of max(avg_us) |
80569 | 2016-03-01 5:03 | 2016-07-18 12:59 | MySQL Server: SYS Schema | Closed (3144 days) | S3 | 5.7.11 | Any | Any | max_latency is not correct for sys.host_summary_by_statement_latency view |
83716 | 2016-11-07 9:31 | 2016-11-08 6:46 | MySQL Server: SYS Schema | Verified (3013 days) | S2 | 5.7.14, 5.7.16 | Any | Any | MySQL performance-schema doesn't store (analyze) queries to views |
81467 | 2016-05-17 14:33 | 2016-05-18 9:43 | MySQL Server: Tests | Verified (3187 days) | S3 | 5.7, 5.7.12 | Any | Any | innodb_fts.sync_block test unstable due to slow query log nondeterminism |
89597 | 2018-02-09 4:41 | 2018-03-21 16:34 | MySQL Server: Tests | Closed (2515 days) | S3 | 8.0.4 | Any | Any | Valgrind reporting memory leak on MTR test main.validate_password_component |
28830 | 2007-06-01 10:26 | 2007-08-09 13:27 | MySQL Server: Tests | Closed (6392 days) | S3 | Any | Any | Test case log_state fails on VMWare Windows clone due to loaded system | |
82307 | 2016-07-21 13:41 | 2016-12-02 20:12 | MySQL Server: Tests | Closed (2989 days) | S3 | 5.6,5.7, 5.7.13 | Any | Any | Memory leaks in unit tests |
27634 | 2007-04-04 5:36 | 2007-06-15 13:45 | MySQL Server: Tests | Closed (6447 days) | S3 | 5.1-bk | Linux | Any | group_by test fails |
28742 | 2007-05-29 10:30 | 2007-06-22 18:42 | MySQL Server: Tests | Closed (6440 days) | S3 | 5.1-BK | Linux (Fedora Core 6) | Any | mysql-test-run is very slow on "Stopping All Servers" step |
33217 | 2007-12-13 15:23 | 2008-02-18 21:38 | MySQL Server: Tests | Closed (6199 days) | S3 | 5.1.23 | MacOS (10.5 Leopard - Intel) | Any | test suite fails on Mac OS X Leopard |
59443 | 2011-01-12 12:03 | 2011-05-31 19:23 | MySQL Server: Tests | Closed (5001 days) | S3 | 5.5+ | Any | Any | query_cache_debug.test is occasionally very slow |
68820 | 2013-03-30 20:27 | 2013-04-16 15:07 | MySQL Server: Tests | Closed (4315 days) | S3 | 5.6 | Linux | Any | incorrect value of bogomips in mysqltest |
43383 | 2009-03-04 16:43 | 2011-02-16 23:43 | MySQL Server: Tests | Closed (5756 days) | S3 | 5.0,5.1,6.0 | Any | Any | main.variables-big : Weak testing code and result |
32198 | 2007-11-08 21:03 | 2007-12-19 5:19 | MySQL Server: Data Types | Closed (6260 days) | S2 | 5.0.50, 5.0.52-BK | Linux | Any | Comparison of DATE with DATETIME still not using indexes correctly |
69023 | 2013-04-21 12:39 | 2013-04-21 12:40 | MySQL Server: Data Types | Verified | S3 | 5.6.12 | Windows | Any | "Questions" output in COM_STATISTICS wraps at 2^32 |
98305 | 2020-01-21 10:57 | 2020-08-04 12:41 | MySQL Server: Data Types | Verified (1836 days) | S5 | 5.7, 8.0 | Linux | Any | hp_rec_key_cmp suboptimal comparison |
69801 | 2013-07-20 8:38 | 2019-11-15 11:10 | MySQL Server: Data Types | Verified | S5 | 5.6.12 | Any | Any | performance regression between 5.5 and 5.6 for str_to_date function |
68827 | 2013-04-01 18:47 | 2013-04-24 8:37 | MySQL Server: Windows | Verified (4307 days) | S2 | 5.6.11 | Windows (window7 64bit) | Any | multiple connections using Shared Memory interfering |
56585 | 2010-09-06 9:38 | 2011-02-16 23:44 | MySQL Server: Windows | Closed (5182 days) | S5 | 5.5.5 | Windows | Any | Slowdown of readonly sysbench benchmarks (e.g point_select) on Windows 5.5 |
27287 | 2007-03-20 12:29 | 2018-04-03 2:35 | MySQL Server: XML functions | Closed (6282 days) | S5 | 5.1.16 | Windows (WinXP SP2) | Any | extractvalue() (and updatexml()) extremely slow for large XML |
Showing all 967 (Edit, Save, CSV, Feed) |