Showing 1-30 of 201 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
47330 | 2009-09-15 15:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5775 days) | S5 | 5.0.77, 5.1.34, 5.1.37 | Linux (Debian x64) | Any | Slow query with left join and having. |
37264 | 2008-06-07 22:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6117 days) | S5 | 5.1.24-rc 5.1.29-rc 5.1.30 | Any | Any | MySQL wrongly uses filesort |
69219 | 2013-05-13 20:14 | 2013-05-13 20:32 | MySQL Server: Optimizer | Verified (4447 days) | S5 | 5.6.12 | Any | Any | CREATE TEMPORARY TABLE ... SELECT is slower on 5.6 than on 5.1 |
75981 | 2015-02-20 13:56 | 2017-11-05 7:12 | MySQL Server: InnoDB storage engine | Verified (3751 days) | S5 | 5.7.6 | Any | Any | MySQL 5.7.5 30% slower than 5.6.23 for 1 thread write |
89149 | 2018-01-08 23:41 | 2018-01-16 17:07 | MySQL Server: Optimizer | Verified (2738 days) | S5 | 5.7.20 | Red Hat (7.4) | Any | SELECT DISTINCT on multiple TEXT columns is slow |
68979 | 2013-04-17 3:47 | 2018-07-11 15:11 | MySQL Server: Optimizer | Verified (4438 days) | S5 | 5.6.10 | Linux | Any | performance regression of MySQL 5.6.10? |
101459 | 2020-11-04 13:05 | 2022-02-28 15:34 | MySQL Server: Optimizer | Verified (1250 days) | S5 | 5.6.50,5.7.32 | Any | Any | With more than one value in IN() clause, query skip index use. |
110998 | 2023-05-11 15:33 | 2023-12-01 6:49 | MySQL Server: Optimizer | Verified (791 days) | S5 | 8.0.20+, 8.0.33 | Linux | Any | Performance regression with SELECT query when sorting on limited fields |
113303 | 2023-12-01 7:29 | 2023-12-05 4:54 | MySQL Server: Optimizer | Verified (593 days) | S5 | 8.0.35 | Any | Any | Explain plan takes forever when there are more joins |
113800 | 2024-01-30 5:30 | 2024-01-31 8:28 | MySQL Server: DML | Verified (532 days) | S5 | 8.0.22, 8.0.36, 8.0.11 | Linux | x86 | Performance degradation of Blob operations comparing with MySQL 5.7 |
114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (510 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
115122 | 2024-05-25 11:17 | 2024-06-16 9:10 | MySQL Server: Optimizer | Verified (395 days) | S5 | 8.4 (Latest), 8.0.37 | Ubuntu (22.04 LTS) | ARM | Unneeded full table scan, although there is an index and condition |
115988 | 2024-09-03 15:03 | 2024-09-12 2:11 | MySQL Server: InnoDB storage engine | Verified (315 days) | S5 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | Too Much Disk Read on Startup, penalizing deployments with many tables (1M+). |
116803 | 2024-11-27 11:29 | 2025-03-22 0:37 | MySQL Server: Optimizer | Verified (219 days) | S5 | 8.0.40 | Any | Any | MySQL 8.0.33 is slower than MySQL 8.0.28 with queries using JOINS |
117867 | 2025-04-03 8:32 | 2025-04-09 10:19 | MySQL Server: Optimizer | Verified (98 days) | S5 | 8.0.41 | Any | Any | use distinct+left join, MySQL 8.0 excute long time than MySQL 5.7 |
118009 | 2025-04-18 7:13 | 2025-05-20 12:12 | MySQL Server: Optimizer | Verified (89 days) | S5 | 8.4.5, 9.3.0 | Debian (12) | x86 (amd64) | SELECT query on primary key column deteriorates to full table scan when filter involves too long string |
116612 | 2024-11-11 11:46 | 2025-05-07 7:17 | MySQL Server: Optimizer | Verified (247 days) | S5 | 8.0.40, 8.0.41, 8.4.4 | Any | Any | Performance degradation of distinct operator from 5.7 to 8.0 |
118144 | 2025-05-08 23:35 | 2025-05-14 10:18 | MySQL Server: Optimizer | Verified (63 days) | S5 | 8.0.40, 8.0.42 | Red Hat (RHEL9) | x86 | Performance regression at 8.0.40 related to record buffer usage |
25891 | 2007-01-27 14:17 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Verified (6398 days) | S3 | 5.0.36-BK, 5.0.27 | Linux (Linux) | Any | Creation of temporary table with key causing error 124 |
26284 | 2007-02-12 12:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6457 days) | S3 | 5.0.bk | Linux (Linux) | Any | bug #26273 / optimize, not executed for index, if datafile is gap-free |
30302 | 2007-08-08 12:41 | 2022-09-04 20:45 | MySQL Server: Optimizer | Verified (5539 days) | S3 | 5.0.40, 5.1, 5.2, 5.0 BK | Any | Any | Query from EXPLAIN EXTENDED .. SHOW WARNINGS returns different result |
36211 | 2008-04-18 22:09 | 2016-02-25 12:24 | MySQL Server: Command-line Clients | Verified | S3 | 5.0.56 | Any | Any | mysql client rejects "--" comments that server accepts |
38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6197 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
38257 | 2008-07-21 12:45 | 2011-02-16 23:43 | MySQL Server: User-defined functions ( UDF ) | Verified (6189 days) | S3 | 5.0, 5.1 | Any | Any | Documentation for initid->max_length not correct |
38570 | 2008-08-05 12:13 | 2011-02-16 23:43 | MySQL Server: User-defined functions ( UDF ) | Verified (6186 days) | S3 | 5.0, 5.1 | Any | Any | calling UDF causes a server crash |
41785 | 2008-12-29 16:41 | 2012-05-18 20:19 | MySQL Server: C API (client library) | Verified (6043 days) | S3 | 5.0, 5.1, 6.0 bzr | Any | Any | C API doesn't know about change in server status after COM_CHANGE_USER |
43451 | 2009-03-06 10:28 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified (5976 days) | S3 | 5.0, 5.1, 6.0 bzr | Linux | Any | Wrong varchar to decimal conversion |
44009 | 2009-04-01 8:27 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified (5901 days) | S3 | 5.1.33, 5.1, 6.0 bzr | Any | Any | Weird error while querying `TABLES` against not existing `TABLE_SCHEMA` |
45876 | 2009-07-01 13:14 | 2017-12-16 9:57 | MySQL Server: Storage Engine API | Verified | S3 | 5.1.35 | Any | Any | SHOW ENGINES output is inaccurate |
48779 | 2009-11-15 11:28 | 2011-02-16 23:44 | MySQL Server: DDL | Verified (5721 days) | S3 | 5.1.40 | Windows (XP64) | Any | bogus 'unknown database' error when encoding long table names on windows |
Showing 1-30 of 201 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |