| « Show Previous 30 Entries | Showing 31-56 of 56 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 91585 | 2018-07-10 1:16 | 2018-08-27 11:06 | MySQL Server: Stored Routines | Verified (2110 days) | S5 | 5.7, 8.0, 8.0.11, 5.7.23 | Any | Any | “dead” code inside the stored proc or function can significantly slow it down |
| 27452 | 2007-03-26 17:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5632 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 |
| 58928 | 2010-12-14 20:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4875 days) | S3 | 5.1-bugteam | Any | Any | "not exists" optimization not applied if relevant table is not single inner one |
| 59557 | 2011-01-17 15:26 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4841 days) | S2 | 5.1, 5.5 | Any | Any | MySQL uses order of fields in GROUP BY when ORDER BY NULL is specified |
| 38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5744 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
| 44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5057 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 (5427 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 (5378 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 |
| 46648 | 2009-08-11 11:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5359 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 |
| 47884 | 2009-10-07 3:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5194 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 |
| 55979 | 2010-08-13 22:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4995 days) | S5 | 5.1.39 | Linux | Any | Key not used if IN() list contains mix of strings and integers |
| 58008 | 2010-11-05 9:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4914 days) | S3 | 5.1, 5.0 | Any | Any | wrong datatype (blob) in the resultset if the string is larger than 512 bytes |
| 95080 | 2019-04-23 7:24 | 2019-04-30 14:09 | MySQL Router | Verified (1816 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 |
| 98771 | 2020-02-28 6:29 | 2020-03-02 18:39 | MySQL Server: Optimizer | Verified (1512 days) | S2 | 5.7, 5.7.29 | Any | Any | Performance impact while selecting data from a JSON type column |
| 99432 | 2020-05-04 8:09 | 2020-05-05 12:04 | MySQL Server: InnoDB storage engine | Verified (1446 days) | S5 | 8.0.20 | Any | ARM | Improving memory barrier during rseg allocation |
| 100091 | 2020-07-02 12:23 | 2020-07-03 8:48 | Connector / Python | Verified (1386 days) | S5 | 8.0.18, 8.0.20 | Any | Any | mysqlx interface is a lot slower than the connector.python interface |
| 100432 | 2020-08-05 7:55 | 2020-08-05 14:03 | MySQL Server: Performance Schema | Verified (1353 days) | S5 | 8.0.21 | Any | ARM | Optimal memory-barrier for performance-schema counter |
| 100119 | 2020-07-06 7:07 | 2020-08-14 13:55 | MySQL Server: InnoDB storage engine | Verified (1344 days) | S5 | 8.0.20 | Any | ARM | Switch to use relaxed memory barrier for redo-log counters |
| 104615 | 2021-08-13 10:26 | 2021-08-13 11:36 | MySQL Server: Logging | Verified (980 days) | S5 | 8.0 | Any (rhel7.4) | Any (intel-x86) | trx commit slow if there are too many binlog files to purge while rotating |
| 83151 | 2016-09-26 14:27 | 2021-09-14 10:08 | MySQL Server: Connection Handling | Verified (1913 days) | S2 | 5.6.33 | CentOS | Any | high number of SHOW WARNINGS can stall server if compressed protocol in use |
| 105982 | 2021-12-27 8:11 | 2022-01-03 8:02 | MySQL Server: Storage Engines | Verified (837 days) | S5 | all, 5.7, 8.0 | Linux | Any | hard-coded libaio API parameter may not helpful to performance |
| 35165 | 2008-03-08 17:48 | 2022-12-04 20:45 | MySQL Server: CSV | Verified (5882 days) | S5 | 5.1 | Any | Any | Logging to table is slow for large queries |
| 110779 | 2023-04-24 11:32 | 2023-05-12 5:49 | MySQL Server: Optimizer | Verified (343 days) | S5 | 8.0.33, 5.7.42 | Any | Any | IN clause cause pick bad performan index |
| 114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (57 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
| 112902 | 2023-10-31 14:39 | 2024-02-26 11:07 | MySQL Server: Optimizer | Verified (53 days) | S5 | 8.0.31, 8.0.35 | Linux (n.a.) | x86 (x86_64) | Optimizer in MySQL 8 is significantly slower on dependent subqueries than 5.7 |
| 114331 | 2024-03-12 21:53 | 2024-03-19 9:48 | MySQL Server: InnoDB storage engine | Verified (31 days) | S5 | 8.0.*, 8.0.36 | Linux | x86 | MySQL get high insert latency in low concurrency |
| « Show Previous 30 Entries | Showing 31-56 of 56 (Edit, Save, CSV, Feed) |
