Showing 1-30 of 56 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
89926 | 2018-03-06 10:20 | 2018-03-12 12:21 | MySQL Server: C API (client library) | Verified (2209 days) | S5 | 5.7 | Linux | x86 | Performance degradation in libmysqlclient 20 |
69118 | 2013-05-02 2:28 | 2013-05-02 14:00 | MySQL Server: Command-line Clients | Verified (3984 days) | S5 | 5.6, 5.7 | Any | Any | Wasted work in method get_table_structure() |
56965 | 2010-09-23 9:22 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4930 days) | S3 | 5.1.44 | Linux (2.6.18-164.6.1.el5 #1 SMP, CentOS 5.5) | Any | mysqldump poor performance with large number of tables |
67913 | 2012-12-16 2:31 | 2017-07-18 5:39 | Connector / ODBC | Verified (4085 days) | S5 | 5.2.2, 5.1.11 | Windows (Windows 7 and 8 64-bit) | Any | ODBC connector performance problem |
100091 | 2020-07-02 12:23 | 2020-07-03 8:48 | Connector / Python | Verified (1365 days) | S5 | 8.0.18, 8.0.20 | Any | Any | mysqlx interface is a lot slower than the connector.python interface |
56924 | 2010-09-22 11:26 | 2018-06-24 20:45 | MySQL Workbench: SQL Editor | Verified (4501 days) | S2 | 5.2.28 | Linux (Ubuntu 10.04) | Any | Memory leak? Possibly not a bug. |
95080 | 2019-04-23 7:24 | 2019-04-30 14:09 | MySQL Router | Verified (1795 days) | S5 | 8.0.15, 8.0.16 | Oracle Linux (Oracle Linux Server 7.5, Linux 4.1.12-124.18.6.el7uek.x86_64 ) | x86 (Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz) | MySQL Router consuming mor CPU resources than it should |
60351 | 2011-03-04 22:15 | 2013-01-15 15:27 | MySQL Server | Verified (4091 days) | S5 | 5.1.55 | Any | Any | trim same character processes data only byte wise (continue of bug14637 (4)) |
60349 | 2011-03-04 21:20 | 2013-01-15 15:25 | MySQL Server | Verified (4091 days) | S5 | 5.1.55 | Any | Any | trim beginning spaces processes data only byte wise (continue of bug14637 (3)) |
60348 | 2011-03-04 20:14 | 2013-01-15 15:25 | MySQL Server | Verified (4091 days) | S5 | 5.1.55 | Any | Any | trim trailing spaces processes data only byte wise (continue of bug14637 (2)) |
60345 | 2011-03-04 17:11 | 2013-01-15 15:25 | MySQL Server | Verified (4091 days) | S5 | 5.1.55 6.0.11 | Any | Any | trim trailing spaces processes data only byte wise (the continue of bug14637) |
48359 | 2009-10-27 19:24 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | In progress (5027 days) | S3 | mysql-5.1-telco-7.1 | Linux (RHEL 4) | Any | ALTER TABLE xx COMMENT - locks large tables |
60261 | 2011-02-26 0:59 | 2016-11-12 22:57 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2694 days) | S5 | mysql-cluster-gpl-7.1.9a | Any | Any | Are transaction hints needed in these situation? |
83151 | 2016-09-26 14:27 | 2021-09-14 10:08 | MySQL Server: Connection Handling | Verified (1892 days) | S2 | 5.6.33 | CentOS | Any | high number of SHOW WARNINGS can stall server if compressed protocol in use |
35165 | 2008-03-08 17:48 | 2022-12-04 20:45 | MySQL Server: CSV | Verified (5861 days) | S5 | 5.1 | Any | Any | Logging to table is slow for large queries |
68572 | 2013-03-05 10:57 | 2014-02-19 16:19 | MySQL Server: Federated storage engine | Verified (4041 days) | S3 | 5.5.25a, 5.5.31 | Any | Any | FEDERATED using SHOW TABLE STATUS causes performance problems for InnoDB tables |
50367 | 2010-01-15 14:12 | 2011-02-16 23:44 | MySQL Server: General | Verified (5125 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) |
42705 | 2009-02-09 16:37 | 2011-02-16 23:43 | MySQL Server: General | Verified (5485 days) | S3 | 5.1.30 | Any | Any | Reduce malloc/free during query lifecycle. |
40367 | 2008-10-28 8:55 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified (5545 days) | S3 | 5.1.28, 5.1.29, 5.0, 5.1 bzr | Any | Any | SHOW on a broad view is taking too long |
75981 | 2015-02-20 13:56 | 2017-11-05 7:12 | MySQL Server: InnoDB storage engine | Verified (3277 days) | S5 | 5.7.6 | Any | Any | MySQL 5.7.5 30% slower than 5.6.23 for 1 thread write |
74408 | 2014-10-15 19:52 | 2018-07-04 15:16 | MySQL Server: InnoDB storage engine | Verified (2095 days) | S5 | 5.6, 5.7, 8.0 | Any | Any | srv_conc_enter_innodb() is not optimal |
81376 | 2016-05-11 6:48 | 2018-07-16 8:12 | MySQL Server: InnoDB storage engine | Verified (2878 days) | S5 | 5.7 | Any | Any | Single page flushing should be removed |
75962 | 2015-02-19 3:14 | 2015-03-03 20:46 | MySQL Server: InnoDB storage engine | Verified (3314 days) | S3 | 5.6.24, 5.7.6 | Any | Any | Innodb calls fsync when freeing a LRU page to fulfill page request |
62018 | 2011-07-28 15:15 | 2018-02-11 20:45 | MySQL Server: InnoDB storage engine | Verified (4090 days) | S5 | 5.6.3 | Any | Any | innodb adaptive hash index mutex contention |
99432 | 2020-05-04 8:09 | 2020-05-05 12:04 | MySQL Server: InnoDB storage engine | Verified (1425 days) | S5 | 8.0.20 | Any | ARM | Improving memory barrier during rseg allocation |
100119 | 2020-07-06 7:07 | 2020-08-14 13:55 | MySQL Server: InnoDB storage engine | Verified (1323 days) | S5 | 8.0.20 | Any | ARM | Switch to use relaxed memory barrier for redo-log counters |
75504 | 2015-01-14 12:52 | 2015-01-22 14:51 | MySQL Server: InnoDB storage engine | Verified (3354 days) | S5 | Any | Any | btr_search_guess_on_hash makes found block young twice? | |
114331 | 2024-03-12 21:53 | 2024-03-19 9:48 | MySQL Server: InnoDB storage engine | Verified (10 days) | S5 | 8.0.*, 8.0.36 | Linux | x86 | MySQL get high insert latency in low concurrency |
60087 | 2011-02-10 13:14 | 2016-12-04 20:45 | MySQL Server: InnoDB storage engine | Verified (4796 days) | S3 | 5.5 | Any | Any | Patch: Minimize InnoDB I/O load by adding a prefetch stage |
59727 | 2011-01-25 21:36 | 2016-12-04 20:45 | MySQL Server: InnoDB storage engine | Verified | S5 | 5.1 plugin, 5.5, 5.6 | Any | Any | LRU search can be inefficient with compression |
Showing 1-30 of 56 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |