| Showing 1-30 of 192 (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 (5054 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 |
| 115988 | 2024-09-03 15:03 | 2024-09-12 2:11 | MySQL Server: InnoDB storage engine | Verified (30 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 (39 days) | S3 | 8.0.39, 8.4.0 | Any | Any | MySQL hangs on installing plugin with innodb_thread_concurrency=1 |
| 115842 | 2024-08-15 8:21 | 2024-08-20 7:37 | MySQL Server: DML | Verified (50 days) | S2 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | The count distinct aggregation funciton of UUID returned an error value |
| 115519 | 2024-07-05 4:24 | 2024-07-16 13:34 | MySQL Server: Optimizer | Verified (80 days) | S2 | 8.2, 8.4.1 | Any | Any | INTERSECT within correlated subquery results in incorrect result |
| 101828 | 2020-12-02 2:37 | 2024-06-25 7:48 | MySQL Server: Replication | Verified (101 days) | S2 | 8.0.37 | CentOS | x86 | Hash scan incorrectly applied the log resulting in HA_ERR_END_OF_FILE |
| 115353 | 2024-06-17 7:22 | 2024-06-21 6:40 | MySQL Server: Optimizer | Verified (109 days) | S2 | 8.0.37, 8.4.0 LTS | Any | Any | Setting index_merge_union leads to incorrect results. |
| 115122 | 2024-05-25 11:17 | 2024-06-16 9:10 | MySQL Server: Optimizer | Verified (110 days) | S5 | 8.4 (Latest), 8.0.37 | Ubuntu (22.04 LTS) | ARM | Unneeded full table scan, although there is an index and condition |
| 114924 | 2024-05-08 14:01 | 2024-07-02 9:48 | MySQL Server: InnoDB storage engine | Verified (134 days) | S5 | 8.0.37 | Any | Any | Significant regression between 8.0.25 and 8.0.37 in a simple OLTP workload |
| 115017 | 2024-05-15 14:44 | 2024-07-01 11:21 | MySQL Server: Optimizer | Verified (142 days) | S2 | 8.0 | Any | Any | Wrong row estimate for range scan |
| 114568 | 2024-04-07 13:43 | 2024-04-08 7:28 | MySQL Server: Optimizer | Verified (179 days) | S1 | 8.0.36 | Any | Any | Different join orders cause inconsistent results |
| 114581 | 2024-04-08 11:24 | 2024-04-08 12:37 | MySQL Server: Optimizer | Verified (179 days) | S2 | 8.0.36 | Any | Any | Constant-Folding optimization negative constant truncate gives wrong operator |
| 114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (225 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
| 113892 | 2024-02-05 10:39 | 2024-02-05 14:13 | MySQL Server: Optimizer | Verified (242 days) | S3 | 8.0 | Any | Any | FORCE INDEX reports wrong number of rows |
| 113800 | 2024-01-30 5:30 | 2024-01-31 8:28 | MySQL Server: DML | Verified (247 days) | S5 | 8.0.22, 8.0.36, 8.0.11 | Linux | x86 | Performance degradation of Blob operations comparing with MySQL 5.7 |
| 113768 | 2024-01-26 2:40 | 2024-01-26 8:53 | MySQL Server: DML | Verified (252 days) | S3 | 8.0.35 | Linux | Any | return error with cast |
| 113464 | 2023-12-19 17:40 | 2024-03-12 11:05 | MySQL Server: Optimizer | Verified (289 days) | S2 | 8.0.27 | Any | Any | >= 8.0.27 Error 1048 when updating row with empty_sql mode |
| 113303 | 2023-12-01 7:29 | 2023-12-05 4:54 | MySQL Server: Optimizer | Verified (308 days) | S5 | 8.0.35 | Any | Any | Explain plan takes forever when there are more joins |
| 113301 | 2023-12-01 7:22 | 2023-12-01 8:53 | MySQL Server: Prepared statements | Verified (308 days) | S2 | 8.0.35, 8.0.31 | Any | Any | using preparation statement to query the time type data, some data is not found |
| 112362 | 2023-09-15 20:19 | 2024-06-10 7:46 | MySQL Server: Optimizer | Verified (375 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 |
| Showing 1-30 of 192 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
