Showing all 8 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
19456 | 2006-05-01 16:17 | 2012-05-18 20:19 | MySQL Server: Archive storage engine | Duplicate (6563 days) | S1 | 5.1 | Windows (Windows) | Any | Moving an open file on windows now creates an error (earlier change in mysys) |
26773 | 2007-03-01 22:16 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Duplicate (5118 days) | S1 | 5.0.27-max | Linux (Debian 3.1 (kernel 2.6.14.2)) | Any | Possible Memory Leak with Archive Tables |
29249 | 2007-06-20 21:01 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Duplicate (6141 days) | S1 | 5.0.44 | Any | Any | thread hang with concurrent insert/optimize of archive tables |
29986 | 2007-07-23 20:05 | 2007-07-25 19:15 | MySQL Server: Archive storage engine | Duplicate (6113 days) | S2 | 6.0.0 alpha | Linux (Kernel 2.6.23-rc1) | Any | Table OK on MySQL 5 not read correctly by MySQL6 |
50632 | 2010-01-26 17:16 | 2011-04-22 17:08 | MySQL Server: Archive storage engine | Duplicate (4746 days) | S1 | 5.1.41 | Linux | Any | Purging records from large partitioned INNODB table into ARCHIVE memory error |
65450 | 2012-05-29 13:31 | 2012-05-29 19:56 | MySQL Server: Archive storage engine | Duplicate (4343 days) | S2 | 5.1.60 - 5.5.22 | Linux (Debian/Ubuntu) | Any | Archive AUTO_INCREMENT must not go backwards, but replication does |
84598 | 2017-01-21 20:08 | 2017-01-23 4:26 | MySQL Server: Archive storage engine | Duplicate (2643 days) | S2 | 5.7.15 | Any | Any | ARCHIVE auto_increment field reset on OPTIMIZE TABLE |
38055 | 2008-07-11 18:43 | 2012-05-18 20:19 | MySQL Server: Archive storage engine | Duplicate (5673 days) | S2 | 5.1.23-rc, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | falcon bug 30210 reproduces in archive storage engine |
Showing all 8 (Edit, Save, CSV, Feed) |