| Showing 1-30 of 205 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 36541 | 2008-05-06 17:01 | 2016-10-16 20:45 | MySQL Server: Replication | In progress (5281 days) | S2 | 5.0.51a-log, 5.1 | Linux | Any | Query event with BEGIN has different size on master and slave |
| 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 |
| 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 |
| 48103 | 2009-10-16 0:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1, 6.0 | Any | Any | Using STRAIGHT_JOIN with Innodb tables can produce duplicate results |
| 48190 | 2009-10-20 14:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1,6.0 | Any | Any | Error processing ALL subqueries on empty sets - different than JavaDB/Postgres |
| 53216 | 2010-04-27 17:39 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified | S3 | 5.5.3-m3, 5.5.4-m3 | Any | Any | Unrelated DDL causes repreparation of a prepared statement |
| 48049 | 2009-10-14 16:46 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1.37, 5.5.7 | Any | Any | SELECT MIN(1) reports differently for MERGE tables in 5.0 and 5.1 |
| 54562 | 2010-06-16 19:18 | 2023-02-12 20:45 | MySQL Server: Replication | Verified | S3 | 5.5.3-m3, 5.5.5-m3 | Any | Any | SBR mistakes SAVEPOINT statement for accessing a transactional table |
| 59999 | 2011-02-07 21:11 | 2022-12-04 20:45 | MySQL Server: Locking | Verified | S3 | 5.5, 5.6.2 | Any | Any | mysqlhotcopy returns error and crashes debug server |
| 69891 | 2013-08-01 6:33 | 2014-09-18 21:25 | MySQL Server: Optimizer | Verified | S3 | 5.1.31 | Any | Any | since 5.1.31 REPLACE() function concats it's results under certain conditions |
| 45680 | 2009-06-23 14:15 | 2020-04-01 13:16 | MySQL Server: Optimizer | Verified | S3 | 5.0.54, 5.0.82, 5.1.35, 6.0.12 | Any | Any | wrong results when using index for lookup with implicitly casted values |
| 118144 | 2025-05-08 23:35 | 2025-05-14 10:18 | MySQL Server: Optimizer | Verified (5 days) | S5 | 8.0.40, 8.0.42 | Red Hat (RHEL9) | x86 | Performance regression at 8.0.40 related to record buffer usage |
| 118033 | 2025-04-22 14:51 | 2025-04-23 8:09 | MySQL Server: Optimizer | Verified (26 days) | S2 | 9.3.0 | Any | Any | Wrong Result of an and expression |
| 109339 | 2022-12-12 12:44 | 2025-04-22 5:11 | Connector / J | Verified (27 days) | S3 | 8.0.22, 8.0.31 | Any | Any | Failed to insert bignums due to overflow |
| 118025 | 2025-04-21 13:38 | 2025-04-22 7:58 | Connector / Python | Verified (27 days) | S1 | 9.3.0 | Any | Any | mysql/connector python version 9.3.0 has a regression which cannot persist binary data with percent signs in it |
| 118024 | 2025-04-21 12:46 | 2025-04-23 8:07 | MySQL Server: Optimizer | Verified (28 days) | S1 | 9.3.0 | Any | Any | Wrong Right Join involving a predicate containing IFNULL and IN |
| 118009 | 2025-04-18 7:13 | 2025-04-18 11:33 | MySQL Server: Optimizer | Verified (31 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 |
| 117959 | 2025-04-13 0:31 | 2025-04-13 16:37 | MySQL Server: Optimizer | Verified (36 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | PRIMARY KEY leads to incorrect INTERSECT result |
| 117867 | 2025-04-03 8:32 | 2025-04-09 10:19 | MySQL Server: Optimizer | Verified (40 days) | S5 | 8.0.41 | Any | Any | use distinct+left join, MySQL 8.0 excute long time than MySQL 5.7 |
| 117911 | 2025-04-08 12:06 | 2025-04-08 14:45 | MySQL Server: Optimizer | Verified (41 days) | S2 | 9.2.0 | Ubuntu (22.04) | Any | INTERSECT operation return wrong result |
| 117691 | 2025-03-12 19:12 | 2025-03-28 9:54 | MySQL Server: InnoDB storage engine | Verified (54 days) | S2 | 8.4.0, 8.4.4, 9.2.0 | Linux | Any | MySQL 8.4 and 9 are not taking advantage of the Linux Page Cache (contrarily to 8.0). |
| 117765 | 2025-03-21 3:09 | 2025-03-21 9:01 | MySQL Server: Optimizer | Verified (59 days) | S2 | 9.2.0, 8.0.41, 8.4.4 | Any | Any | Query result may be wrong if using compound order by inside GROUP_CONCAT |
| 117618 | 2025-03-04 14:31 | 2025-03-05 6:29 | MySQL Server: Replication | Verified (75 days) | S3 | 9.1, 9.2.0 | Any | Any | Erroneous warning "Combining the storage engines InnoDB and MyISAM is deprecated" |
| 117598 | 2025-02-28 3:28 | 2025-04-01 5:09 | MySQL Server: Optimizer | Verified (80 days) | S2 | 8.0.35, 8.0.41, 8.4.4 | Any | Any | Wrong sort order for queries with ORDER BY DESC when using range comparison with LIMIT |
| 116803 | 2024-11-27 11:29 | 2025-03-22 0:37 | MySQL Server: Optimizer | Verified (161 days) | S5 | 8.0.40 | Any | Any | MySQL 8.0.33 is slower than MySQL 8.0.28 with queries using JOINS |
| 116895 | 2024-12-06 11:45 | 2024-12-25 3:09 | MySQL Server: Optimizer | Verified (164 days) | S2 | 9.0,8.0, 8.0.40, 8.4.3 | Any | Any | View using IN(SELECT LIMIT) has wrong result |
| 116715 | 2024-11-19 17:03 | 2024-11-20 17:23 | MySQL Server: InnoDB storage engine | Verified (180 days) | S2 | 9, 8.4, 8.0 | Any | Any | Optimize Normal Startup with Many Tables. |
| 116612 | 2024-11-11 11:46 | 2025-05-07 7:17 | MySQL Server: Optimizer | Verified (189 days) | S5 | 8.0.40, 8.0.41, 8.4.4 | Any | Any | Performance degradation of distinct operator from 5.7 to 8.0 |
| 115988 | 2024-09-03 15:03 | 2024-09-12 2:11 | MySQL Server: InnoDB storage engine | Verified (257 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+). |
| 115931 | 2024-08-26 12:32 | 2024-08-26 14:32 | MySQL Server: InnoDB storage engine | Verified (266 days) | S3 | 8.0.39, 8.4.0 | Any | Any | MySQL hangs on installing plugin with innodb_thread_concurrency=1 |
| Showing 1-30 of 205 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
