| Showing 1-30 of 125 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 103652 | 2021-05-11 9:53 | 2021-05-11 11:06 | MySQL Server: InnoDB storage engine | Verified (1137 days) | S2 | 8.0.24 | Any | Any | The data of dynamic metadata table lost |
| 83255 | 2016-10-04 16:02 | 2017-05-04 7:47 | MySQL Server: InnoDB storage engine | Verified (2605 days) | S2 | any, 5.7.15 | Any | Any | --innodb-force-recovery=6 possibly corrupts doublewrite buffer |
| 73571 | 2014-08-13 14:20 | 2014-12-14 2:52 | MySQL Server: InnoDB storage engine | Verified (3599 days) | S2 | 5.6.20 | Linux | Any | 'IMPORT TABLESPACE' from corrupted file leads to permanent server failure |
| 88150 | 2017-10-19 13:08 | 2023-07-05 16:19 | MySQL Server: InnoDB storage engine | Verified (2436 days) | S2 | 5.5, 5.6, 5.7, 5.5.57, 5.6.38, 5.7.20 | Any | Any | 'Undo log record is too big.' error occurring in very narrow range of str length |
| 78401 | 2015-09-10 20:56 | 2016-09-14 5:15 | MySQL Server: InnoDB storage engine | Verified (3206 days) | S2 | 5.6, 5.6.26 | Any | Any | "ANALYZE TABLE" may assign temporary values to table stats during its execution |
| 82737 | 2016-08-26 3:53 | 2016-09-02 4:29 | MySQL Server: InnoDB storage engine | Verified (2849 days) | S2 | 5.7.13, 5.7.14 | Any | Any | "SIGKILL myself" for ALTER TABLE DROP COLUMN command |
| 92556 | 2018-09-25 11:29 | 2018-09-26 14:46 | MySQL Server: InnoDB storage engine | Verified (2095 days) | S1 | 8.0.12 | Any | Any | [ERROR] [MY-011825] [InnoDB] ... the row size .. for a record on index leaf page |
| 82355 | 2016-07-27 8:45 | 2016-08-02 8:28 | MySQL Server: InnoDB storage engine | Verified (2880 days) | S1 | 5.7.13, 5.7.14 | CentOS (7) | Any | [FATAL] InnoDB: Missing MLOG_FILE_NAME or MLOG_FILE_DELETE for redo log |
| 76922 | 2015-05-04 8:08 | 2015-05-05 13:24 | MySQL Server: InnoDB storage engine | Verified (3335 days) | S2 | 5.5.43 | Linux (ubuntu 12.04.) | Any | #1030 - Got error -1 from storage engine |
| 111353 | 2023-06-11 22:04 | 2023-06-13 9:55 | MySQL Server: InnoDB storage engine | Verified (374 days) | S2 | 8.0, 8.0.33 | Any | Any | 3x Performance Regression from 5.7 to 8.0 on ALTER TABLE FORCE. |
| 84025 | 2016-12-01 4:02 | 2023-02-10 9:35 | MySQL Server: InnoDB storage engine | Verified (2713 days) | S1 | 5.7.16, 5.7.17 | Any | Any | 5.7 Shutdown and startup take a long time after creating 100k tables |
| 114838 | 2024-05-01 13:48 | 2024-05-28 20:28 | MySQL Server: InnoDB storage engine | Verified (31 days) | S1 | 8.4.0 | Ubuntu | Any | 8.4.0 requires unique constraint for FK |
| 101900 | 2020-12-08 3:21 | 2024-01-30 6:39 | MySQL Server: InnoDB storage engine | Verified (1291 days) | S2 | 8.0.21 | Linux (7.6) | Any | Add partition is slow |
| 89098 | 2018-01-03 15:07 | 2018-01-04 14:14 | MySQL Server: InnoDB storage engine | Verified (2360 days) | S1 | 5.7/8.0 | Any | Any | Adding an auto_increment column to existing table creates gaps |
| 77654 | 2015-07-08 10:55 | 2015-07-08 11:32 | MySQL Server: InnoDB storage engine | Verified (3271 days) | S2 | 5.6.27 | Any | Any | After 5.6.15 innodb_force_recovery greater or equal than 4 is useless |
| 100838 | 2020-09-14 10:55 | 2023-01-03 15:14 | MySQL Server: InnoDB storage engine | Verified (942 days) | S2 | 8.0.19 | Ubuntu | x86 | Alter table causes crash + missing tablespace after restart |
| 90903 | 2018-05-17 6:13 | 2018-05-23 14:51 | MySQL Server: InnoDB storage engine | Verified (2221 days) | S2 | 5.6/5.7/8.0 | Any | Any | ALTER TABLE doesn't prevent AUTO_INCREMENT out of range in strict mode |
| 82320 | 2016-07-22 8:33 | 2016-07-22 9:06 | MySQL Server: InnoDB storage engine | Verified (2891 days) | S2 | 5.6, 5.6.31 | Any | Any | ALTER Table failure with DUPLICATE key causes a crash |
| 82321 | 2016-07-22 9:45 | 2016-07-22 11:29 | MySQL Server: InnoDB storage engine | Verified (2891 days) | S2 | 5.6.31 | Any | Any | ALTER table failure with DUPLICATE key crash post index build crashes |
| 80183 | 2016-01-28 8:03 | 2016-06-18 21:45 | MySQL Server: InnoDB storage engine | Verified (3067 days) | S1 | 5.7.10 | CentOS (7) | Any | ALTER TABLESPACE is not crash resistant |
| 104959 | 2021-09-16 14:45 | 2021-09-16 16:39 | MySQL Server: InnoDB storage engine | Verified (1009 days) | S2 | 5.7 | Any | Any | ANALYZE InnoDB wide tables incorrectly to get zero or underestimated statistics |
| 98132 | 2020-01-06 10:55 | 2022-01-04 12:51 | MySQL Server: InnoDB storage engine | Verified (1627 days) | S2 | 5.6, 5.7, 8.0, 5.7.28, 8.0.18 | Any | Any | Analyze table leads to empty statistics during online rebuild DDL |
| 10063 | 2005-04-21 15:15 | 2017-11-13 0:25 | MySQL Server: InnoDB storage engine | Verified (3803 days) | S1 | 4.1.11 | Windows (Windows XP) | Any | ANSI standard updating multiple rows -- foreign key constraints |
| 61058 | 2011-05-04 15:53 | 2013-12-09 10:18 | MySQL Server: InnoDB storage engine | Verified (4797 days) | S2 | 5.1.37/5.5/5.6/5.7 | Linux | Any | Autoincrement exceed expected value after INSERT INTO ... SELECT |
| 96236 | 2019-07-17 14:56 | 2023-07-25 5:44 | MySQL Server: InnoDB storage engine | Verified (1800 days) | S1 | 5.7.25, 8.0.16 | Any | Any | Big intrinsic tmp InnoDB table make InnoDB engine get totally stuck |
| 105652 | 2021-11-22 4:41 | 2021-11-23 14:20 | MySQL Server: InnoDB storage engine | Verified (942 days) | S2 | 5.7, 8.0 | Any | Any | buffer pool flush_rbt could be disorded with innodb tablespace > 32TB |
| 79843 | 2016-01-05 8:38 | 2016-02-12 8:00 | MySQL Server: InnoDB storage engine | Verified (3052 days) | S2 | 5.6.27, 5.6.28, 5.7.10 | Any | Any | Buffer pool size differs if we calculate it from engine status output |
| 80268 | 2016-02-04 13:18 | 2016-02-05 7:58 | MySQL Server: InnoDB storage engine | Verified (3059 days) | S1 | 5.7.10 | CentOS (7) | Any | Can create general tablespace with same name several times after crash |
| 83557 | 2016-10-27 3:08 | 2016-10-27 9:03 | MySQL Server: InnoDB storage engine | Verified (2794 days) | S1 | 5.7.16 | CentOS | Any | Can't use LOCK=NONE to drop columns in table with virtual columns |
| 75616 | 2015-01-24 6:14 | 2018-04-24 13:15 | MySQL Server: InnoDB storage engine | Verified (3285 days) | S1 | 5.6.22, 5.6.23 | FreeBSD | Any | Cannot initialize or use raw device as InnoDB File |
| Showing 1-30 of 125 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
