Showing all 16 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
37182 | 2008-06-04 5:50 | 2018-07-01 18:08 | MySQL Server: Archive storage engine | Verified (5777 days) | S3 | 5.1.24, 5.1.30 | Any (RH Linux 64, WinXP) | Any | Dumped Archive table with AUTO_INCRMENET PRIMARY KEY won't restore from dump |
37648 | 2008-06-26 0:48 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified (5729 days) | S2 | 5.1.25 | Linux (CentOS 5) | Any | Changing storage engine to ARCHIVE in 5.1 loses data if disk fills up |
37871 | 2008-07-04 13:42 | 2016-03-04 9:34 | MySQL Server: Archive storage engine | Verified (2947 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Linux | Any | ALTER TABLE ENGINE=ARCHIVE fails on tables with auto_increment field |
39892 | 2008-10-06 21:13 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified (5650 days) | S3 | 5.1+ | Any | Any | Wrong usage of hander::info call in archive |
40216 | 2008-10-21 16:32 | 2017-01-23 4:27 | MySQL Server: Archive storage engine | Verified (5630 days) | S2 | 5.1, 5.7.17 | Any | Any | optimize table resets auto_increment value on archive tables |
44516 | 2009-04-28 13:23 | 2012-05-18 20:19 | MySQL Server: Archive storage engine | Verified (5421 days) | S3 | 6.0 | Any | Any | Invalid Archive table handler if opened from cached share. |
47660 | 2009-09-27 20:41 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified | S3 | 6.0 | Any | Any | main.archive fails sporadically |
48339 | 2009-10-27 7:17 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified (5267 days) | S3 | 5.1.41-bzr, 5.5.0-bzr, 6.0.14-bzr | Any | Any | Delayed inserts into archive table lead to warnings in error log on debug server |
48343 | 2009-10-27 9:09 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified (5267 days) | S3 | 5.1.41-bzr | Any | Any | Wrong locking for Archive tables leads to broken statement replication. |
57188 | 2010-10-01 21:58 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified (4928 days) | S3 | 5.1.51, 5.5.6 | Any | Any | checksum table gives 0 until 'show table status' is run against the table |
62054 | 2011-08-02 8:51 | 2011-08-08 4:00 | MySQL Server: Archive storage engine | Verified (4623 days) | S3 | 5.5, any? | Any | Any | archive_reader tool silently ignores repair and for force options |
69086 | 2013-04-26 19:17 | 2013-04-26 20:29 | MySQL Server: Archive storage engine | Verified (3990 days) | S3 | 5.1-debug, 5.5-debug, 5.6-debug | Any | Any | Assertion `fd != -1' fails in my_seek on REPAIR of a corrupted ARCHIVE table |
71211 | 2013-12-23 9:21 | 2013-12-23 9:31 | MySQL Server: Archive storage engine | Verified (3749 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | ARCHIVE engine does not guarantee UNIQUE and PRIMARY KEY constraints |
82580 | 2016-08-15 8:56 | 2016-08-16 6:13 | MySQL Server: Archive storage engine | Verified (2782 days) | S3 | 5.7.12, 5.6.19, 5.7.14 | Linux | Any | MySQL Docu does not reflect that archive SE support partitioning |
91996 | 2018-08-13 17:37 | 2018-08-13 18:27 | MySQL Server: Archive storage engine | Verified (2055 days) | S3 | Any | Any | Contribution: Configurable compression level for archive storage engine | |
113305 | 2023-12-01 8:13 | 2023-12-11 10:31 | MySQL Server: Archive storage engine | Verified (119 days) | S3 | 8.0 | Linux | Any | Ambiguous error messages 'Unknown error -1' from storage engine |
Showing all 16 (Edit, Save, CSV, Feed) |