| « Show Previous 30 Entries | Showing 31-56 of 56 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 46376 | 2009-07-24 17:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5382 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 |
| 71140 | 2013-12-13 9:16 | 2015-07-31 8:59 | MySQL Server: Optimizer | Verified (3189 days) | S2 | 5.1, 5.5, 5.6.15, 5.7.7 | Any | Any | Optimizer does NOT use range checks in typical self-join for InnoDB tables |
| 112902 | 2023-10-31 14:39 | 2024-02-26 11:07 | MySQL Server: Optimizer | Verified (57 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 |
| 60087 | 2011-02-10 13:14 | 2016-12-04 20:45 | MySQL Server: InnoDB storage engine | Verified (4821 days) | S3 | 5.5 | Any | Any | Patch: Minimize InnoDB I/O load by adding a prefetch stage |
| 89926 | 2018-03-06 10:20 | 2018-03-12 12:21 | MySQL Server: C API (client library) | Verified (2234 days) | S5 | 5.7 | Linux | x86 | Performance degradation in libmysqlclient 20 |
| 114056 | 2024-02-19 23:03 | 2024-02-22 10:56 | MySQL Server: Prepared statements | Verified (61 days) | S5 | 8.0.32, 8.0.22+ | Any | Any | Performance degredation using REGEXP in statement with parameters vs query |
| 98771 | 2020-02-28 6:29 | 2020-03-02 18:39 | MySQL Server: Optimizer | Verified (1516 days) | S2 | 5.7, 5.7.29 | Any | Any | Performance impact while selecting data from a JSON type column |
| 44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5061 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
| 64340 | 2012-02-15 14:07 | 2013-06-14 15:35 | MySQL Server: InnoDB Plugin storage engine | Verified (3966 days) | S5 | 5.1.52, 5.1.61 | Any | Any | race on no_flush event during buf_flush_free_margin |
| 42705 | 2009-02-09 16:37 | 2011-02-16 23:43 | MySQL Server: General | Verified (5510 days) | S3 | 5.1.30 | Any | Any | Reduce malloc/free during query lifecycle. |
| 66563 | 2012-08-28 5:37 | 2012-08-28 6:55 | MySQL Server: InnoDB Plugin storage engine | Verified (4256 days) | S5 | 5.1,5.6 | Any | Any | reduce the number of redundant calls to btr_cur_optimistic_insert() |
| 50367 | 2010-01-15 14:12 | 2011-02-16 23:44 | MySQL Server: General | Verified (5150 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) |
| 38397 | 2008-07-27 20:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5748 days) | S3 | 5.1.26, 5.0.62 | Any | Any | select distinct + order by desc is executed inefficiently |
| 40367 | 2008-10-28 8:55 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified (5570 days) | S3 | 5.1.28, 5.1.29, 5.0, 5.1 bzr | Any | Any | SHOW on a broad view is taking too long |
| 81376 | 2016-05-11 6:48 | 2018-07-16 8:12 | MySQL Server: InnoDB storage engine | Verified (2903 days) | S5 | 5.7 | Any | Any | Single page flushing should be removed |
| 46648 | 2009-08-11 11:41 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5363 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 |
| 74408 | 2014-10-15 19:52 | 2018-07-04 15:16 | MySQL Server: InnoDB storage engine | Verified (2120 days) | S5 | 5.6, 5.7, 8.0 | Any | Any | srv_conc_enter_innodb() is not optimal |
| 100119 | 2020-07-06 7:07 | 2020-08-14 13:55 | MySQL Server: InnoDB storage engine | Verified (1348 days) | S5 | 8.0.20 | Any | ARM | Switch to use relaxed memory barrier for redo-log counters |
| 60349 | 2011-03-04 21:20 | 2013-01-15 15:25 | MySQL Server | Verified (4116 days) | S5 | 5.1.55 | Any | Any | trim beginning spaces processes data only byte wise (continue of bug14637 (3)) |
| 60351 | 2011-03-04 22:15 | 2013-01-15 15:27 | MySQL Server | Verified (4116 days) | S5 | 5.1.55 | Any | Any | trim same character processes data only byte wise (continue of bug14637 (4)) |
| 60348 | 2011-03-04 20:14 | 2013-01-15 15:25 | MySQL Server | Verified (4116 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 (4116 days) | S5 | 5.1.55 6.0.11 | Any | Any | trim trailing spaces processes data only byte wise (the continue of bug14637) |
| 104615 | 2021-08-13 10:26 | 2021-08-13 11:36 | MySQL Server: Logging | Verified (984 days) | S5 | 8.0 | Any (rhel7.4) | Any (intel-x86) | trx commit slow if there are too many binlog files to purge while rotating |
| 45424 | 2009-06-10 6:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5431 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 ? |
| 69118 | 2013-05-02 2:28 | 2013-05-02 14:00 | MySQL Server: Command-line Clients | Verified (4009 days) | S5 | 5.6, 5.7 | Any | Any | Wasted work in method get_table_structure() |
| 58008 | 2010-11-05 9:38 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4918 days) | S3 | 5.1, 5.0 | Any | Any | wrong datatype (blob) in the resultset if the string is larger than 512 bytes |
| « Show Previous 30 Entries | Showing 31-56 of 56 (Edit, Save, CSV, Feed) |
