Showing 1-30 of 138 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
1569 | 2003-10-16 6:25 | 2011-02-16 23:42 | Tools | Can't repeat (5892 days) | S3 | 4.0.15 | HP/UX (hpux11.11-parisc20, Linux ia64) | Any | Crash-me crashes on HPUX, Linux ia64 |
12123 | 2005-07-22 20:39 | 2005-10-31 19:46 | MySQL Server: Replication | Closed (7197 days) | S3 | 4.1 | Any (all) | Any | mysqldump --tab results in text file which can't be imported |
15475 | 2005-12-05 4:43 | 2007-11-07 9:59 | MySQL Server: Replication | Won't fix (6460 days) | S2 | 4.1.17-BK, 4.1.15 | Linux (Linux) | Any | Replication of GET_LOCK() |
18116 | 2006-03-09 20:49 | 2006-04-06 0:17 | MySQL Server: Replication | Closed (7040 days) | S2 | 5.0.18 | Linux (linux) | Any | MySQL 5.0 deadlocks while writing binary log |
18872 | 2006-04-07 2:10 | 2006-05-10 11:01 | MySQL Server: Replication | No Feedback (7006 days) | S3 | 4.1.15 | Any (all) | Any | GRANT statement fails to replicate |
27492 | 2007-03-28 9:05 | 2017-05-21 20:45 | MySQL Server: Replication | Duplicate (6109 days) | S3 | 5.0.40-BK, 5.0.37 | Any | Any | Replication queries are not logged in slow query log |
37211 | 2008-06-05 2:55 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (6237 days) | S3 | 5.0, 5.1 | Any | Any | Unclear error in MySQL Replication |
59899 | 2011-02-02 17:37 | 2011-06-24 23:00 | MySQL Server: Row Based Replication ( RBR ) | No Feedback (5135 days) | S3 | 5.1.36, 5.1.54 | Any | Any | Wrong status in processlist when using ROW level replication |
52455 | 2010-03-30 1:54 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5388 days) | S3 | 5.1 | Any | Any | Subpar INSERT ON DUPLICATE KEY UPDATE performance with many partitions |
52517 | 2010-04-01 3:10 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5388 days) | S3 | 5.1.45 | Any | Any | Regression in ROW level replication performance with partitions |
43 | 2003-01-27 18:54 | 2008-10-03 9:47 | MySQL Server: Optimizer | Can't repeat (6129 days) | S3 | 3.23, 4.0 | Any (all) | Any | Join does not use indexes in case there is no cardinarity data |
1973 | 2003-11-27 9:16 | 2003-12-13 18:57 | MySQL Server: Optimizer | Won't fix (7885 days) | S3 | 4.0 | Any (all) | Any | TPC-C query does not uses indexes efficently |
4402 | 2004-07-04 8:21 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6129 days) | S4 | 4.1, 5.1.28, 6.0.6 | Any (all) | Any | Equivalence is not considered in group by and order by |
6072 | 2004-10-13 19:22 | 2004-11-23 16:42 | MySQL Server: Optimizer | Won't fix (7539 days) | S2 | 4.1.6 (bk) | Any (all) | Any | MySQL 4.1 performance regression while comparing text fields |
11700 | 2005-07-02 4:13 | 2005-07-14 16:10 | MySQL Server: Optimizer | Closed (7306 days) | S1 | 4.1.13-bk | Any (all) | Any | Wrong query result when table is used firsts time |
16555 | 2006-01-16 23:48 | 2012-08-30 11:47 | MySQL Server: Optimizer | Closed (4702 days) | S4 | 4.1 | Linux (linux) | Any | Comparison of constant which is out of range leads to key lookup |
16590 | 2006-01-18 0:16 | 2007-02-13 19:07 | MySQL Server: Optimizer | Closed (6727 days) | S3 | 4.1 | Any (all) | Any | Optimized does not do right "const" table pre-read |
22950 | 2006-10-03 16:54 | 2012-05-18 20:19 | MySQL Server: Optimizer | Duplicate (6131 days) | S4 | 5.0, 5.1 BK, 4.1 BK | Linux (Linux) | Any | Innodb does not use primary key for order by |
35819 | 2008-04-04 2:32 | 2022-09-04 20:45 | MySQL Server: Optimizer | Duplicate (5746 days) | S3 | 5.0.54, 5.0.56 | Any | Any | Multi column IN does not use index |
35922 | 2008-04-09 5:23 | 2008-04-11 13:08 | MySQL Server: Optimizer | Not a Bug (6304 days) | S3 | 5.0.54, 5.0.60 | Any | Any | Equity propagation does not work properly w functions |
42677 | 2009-02-08 3:26 | 2022-09-01 6:54 | MySQL Server: Optimizer | Can't repeat (1048 days) | S3 | 5.0 and 5.1 | Any | Any | MySQL Optimizer does not work right with truncation |
338 | 2003-04-28 3:18 | 2003-04-28 15:31 | MySQL Server: MyISAM storage engine | Not a Bug (8114 days) | S1 | 4.0.13 | Linux (Linux) | Any | REPAIR table USE_FRM results in data loss if killed. |
342 | 2003-04-29 3:38 | 2003-05-13 9:24 | MySQL Server: MyISAM storage engine | Closed (8099 days) | S3 | 4.0.12 | Linux (Linux) | Any | myisam_max_sort_file_size is not handled if set online |
506 | 2003-05-26 8:55 | 2003-06-16 10:07 | MySQL Server: MyISAM storage engine | Closed (8065 days) | S3 | 4.0.13 | Any (all) | Any | MySQL 4.0.13 files to access the table MySQL 4.0.12, 3.23.57 opens file |
2714 | 2004-02-11 13:40 | 2004-03-05 0:08 | MySQL Server: MyISAM storage engine | Closed (7802 days) | S3 | 4.0 | Any (all) | Any | DELAY_KEY_WITE=1 does not work with --enable-locking |
2715 | 2004-02-11 13:49 | 2004-03-29 8:05 | MySQL Server: MyISAM storage engine | Not a Bug (7778 days) | S3 | Any | key_blocks_used are not counted properly with --enable-locking | ||
2831 | 2004-02-16 15:06 | 2008-09-27 9:51 | MySQL Server: MyISAM storage engine | Won't fix (6135 days) | S3 | 4.0 | Any (all) | Any | --external-locking does not fully work with --myisam-recover |
4369 | 2004-07-02 6:01 | 2004-08-09 23:16 | MySQL Server: MyISAM storage engine | Closed (7645 days) | S2 | 4.1 | Linux (linux) | Any | MySQL 4.1 regression in Alter table/tmp table from hash |
11023 | 2005-06-01 21:18 | 2005-08-05 10:07 | MySQL Server: MyISAM storage engine | Not a Bug (7284 days) | S3 | 4.1.12 | Any (all) | Any | Compressed table cardinality is not set |
14155 | 2005-10-19 22:19 | 2005-12-09 0:18 | MySQL Server: MyISAM storage engine | Closed (7158 days) | S3 | 4.1.14, 5.0.13-rc | Linux (Linux 64bit) | Any | MAX_ROWS is wrong on 64bit platform |
Showing 1-30 of 138 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |