Showing 1-90 of 654 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
10063 | 2005-04-21 15:15 | 2017-11-13 0:25 | MySQL Server: InnoDB storage engine | Verified (3719 days) | S1 | 4.1.11 | Windows (Windows XP) | Any | ANSI standard updating multiple rows -- foreign key constraints |
10132 | 2005-04-25 3:00 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | Verified (3718 days) | S1 | 5.1, 6.0 | Linux (Linux) | Any | Crashing the server on corrupt InnoDB page is unhelpful |
62740 | 2011-10-14 15:34 | 2022-08-17 12:11 | MySQL Server: InnoDB storage engine | Verified (3942 days) | S1 | 5.5.15 | MacOS (10.6.8) | Any | Crashes during startup in crash recovery InnoDB |
68895 | 2013-04-09 7:35 | 2013-04-10 15:36 | MySQL Server: InnoDB storage engine | Verified (4006 days) | S1 | 5.6 | Any | Any | Various assertions and crashes when running out of space |
69100 | 2013-04-30 9:53 | 2015-03-15 20:45 | MySQL Server: InnoDB storage engine | Verified (3980 days) | S1 | 5.5.31-0, 5.5.30-1, 5.5.29-0, 5.5.25-1, 5.5.16, 5.5.30-1.1, 5.6.10, 5.0.97, 5.1.70, 5.5.29, 5.7.2 | Linux (Debian 6 / Debian 7 / Ubuntu 12.10 / Windows 8) | Any | CAST in IF function fails in some case |
74842 | 2014-11-13 19:31 | 2015-07-01 3:59 | MySQL Server: InnoDB storage engine | Verified (3194 days) | S1 | 5.6 | Any | Any | Incorrect attribute((nonnull)) for btr_cur_ins_lock_and_undo callees |
75616 | 2015-01-24 6:14 | 2018-04-24 13:15 | MySQL Server: InnoDB storage engine | Verified (3201 days) | S1 | 5.6.22, 5.6.23 | FreeBSD | Any | Cannot initialize or use raw device as InnoDB File |
75910 | 2015-02-15 21:00 | 2015-02-27 23:00 | MySQL Server: InnoDB storage engine | Verified (3318 days) | S1 | 5.7.5-m15, 5.6.23 | Any | Any | Odd tablespace discard messages in error log |
76551 | 2015-03-31 22:31 | 2016-01-16 20:31 | MySQL Server: InnoDB storage engine | Verified (3285 days) | S1 | 5.6 | Linux (centos) | Any | Query hangs on INSERT INTO...SELECT... ON DUPLICATE KEY UPDATE |
80183 | 2016-01-28 8:03 | 2016-06-18 21:45 | MySQL Server: InnoDB storage engine | Verified (2983 days) | S1 | 5.7.10 | CentOS (7) | Any | ALTER TABLESPACE is not crash resistant |
80268 | 2016-02-04 13:18 | 2016-02-05 7:58 | MySQL Server: InnoDB storage engine | Verified (2975 days) | S1 | 5.7.10 | CentOS (7) | Any | Can create general tablespace with same name several times after crash |
80625 | 2016-03-06 9:26 | 2016-03-08 13:10 | MySQL Server: InnoDB storage engine | Verified (2943 days) | S1 | 5.6.29 | Any | Any | InnoDB: Failing assertion: table->data_dir_path while dropping table |
82060 | 2016-06-30 2:55 | 2019-05-08 4:17 | MySQL Server: InnoDB storage engine | Verified (2829 days) | S1 | 5.7.12, 5.7.13 | CentOS (CentOS release 6.5 (Final)) | Any | mysqld will read dropped table when it start |
82355 | 2016-07-27 8:45 | 2016-08-02 8:28 | MySQL Server: InnoDB storage engine | Verified (2796 days) | S1 | 5.7.13, 5.7.14 | CentOS (7) | Any | [FATAL] InnoDB: Missing MLOG_FILE_NAME or MLOG_FILE_DELETE for redo log |
83557 | 2016-10-27 3:08 | 2016-10-27 9:03 | MySQL Server: InnoDB storage engine | Verified (2710 days) | S1 | 5.7.16 | CentOS | Any | Can't use LOCK=NONE to drop columns in table with virtual columns |
84025 | 2016-12-01 4:02 | 2023-02-10 9:35 | MySQL Server: InnoDB storage engine | Verified (2629 days) | S1 | 5.7.16, 5.7.17 | Any | Any | 5.7 Shutdown and startup take a long time after creating 100k tables |
85585 | 2017-03-22 21:36 | 2023-06-01 12:05 | MySQL Server: InnoDB storage engine | In progress (1220 days) | S1 | 5.6.35-80.0-debug-log | Any | Any | InnoDB: Failing assertion: UT_LIST_GET_LEN(buf_pool->flush_list) == 0 |
86257 | 2017-05-10 5:53 | 2023-07-21 16:54 | MySQL Server: InnoDB storage engine | Verified (2515 days) | S1 | 5.7.17, 5.7.18 | Any | Any | Error log: Got error 155 when reading table |
86809 | 2017-06-23 8:47 | 2018-12-13 3:52 | MySQL Server: InnoDB storage engine | Verified (2471 days) | S1 | 5.7.18 | Any | Any | Failed to drop tablespace after unsuccessful attempt to create partitioned table |
88808 | 2017-12-07 10:03 | 2018-01-01 22:23 | MySQL Server: InnoDB storage engine | Verified (2279 days) | S1 | 5.7.20 | Any | Any | InnoDB errors on mysql db tables when using innodb-force-recovery |
89098 | 2018-01-03 15:07 | 2018-01-04 14:14 | MySQL Server: InnoDB storage engine | Verified (2276 days) | S1 | 5.7/8.0 | Any | Any | Adding an auto_increment column to existing table creates gaps |
89534 | 2018-02-05 13:06 | 2020-02-05 10:17 | MySQL Server: InnoDB storage engine | Verified (2243 days) | S1 | 5.7.21 | Any | Any | Crash during innodb recovery when working with encryption |
92556 | 2018-09-25 11:29 | 2018-09-26 14:46 | MySQL Server: InnoDB storage engine | Verified (2011 days) | S1 | 8.0.12 | Any | Any | [ERROR] [MY-011825] [InnoDB] ... the row size .. for a record on index leaf page |
96236 | 2019-07-17 14:56 | 2023-07-25 5:44 | MySQL Server: InnoDB storage engine | Verified (1716 days) | S1 | 5.7.25, 8.0.16 | Any | Any | Big intrinsic tmp InnoDB table make InnoDB engine get totally stuck |
103478 | 2021-04-26 8:40 | 2021-04-26 10:54 | MySQL Server: InnoDB storage engine | Verified (1068 days) | S1 | 5.7.26, 5.7.32, 5.7.33. 5.7.34 | Windows (10 Pro) | Any | Internal Temp Tables used under heavy load cause the system to hang |
108087 | 2022-08-08 10:23 | 2022-08-11 15:12 | MySQL Server: InnoDB storage engine | Verified (596 days) | S1 | 5.6, 5.7 | Any | Any | InnoDB:crash because of failure to rename file in DDL |
108314 | 2022-08-29 7:55 | 2022-09-01 7:31 | MySQL Server: InnoDB storage engine | Verified (575 days) | S1 | 8.0.30 | Any | Any | Modifications of uncommitted transactions are seen by other sessions |
114138 | 2024-02-27 9:44 | 2024-02-27 10:36 | MySQL Server: InnoDB storage engine | Verified (31 days) | S1 | 8.0.36, 8.3.0 | Any | Any | MVCC is broken for small partial update of blob |
28913 | 2007-06-06 4:54 | 2019-08-24 6:02 | MySQL Server: InnoDB storage engine | Verified (4830 days) | S2 | 5.0.45, 5.1 | Windows | Any | Running MySQL data on a GPT drive? |
47436 | 2009-09-18 10:27 | 2011-11-02 9:21 | MySQL Server: InnoDB storage engine | Verified (4531 days) | S2 | 5.1.38 | Linux | Any | Transaction isolation level SERIALIZABLE becomes REPEATABLE-READ in autocommit |
53825 | 2010-05-19 20:17 | 2022-04-10 20:45 | MySQL Server: InnoDB storage engine | Verified (5063 days) | S2 | 5.0, 5.1, plugin | Any | Any | Removing locks from queue is very CPU intensive with many locks |
61058 | 2011-05-04 15:53 | 2013-12-09 10:18 | MySQL Server: InnoDB storage engine | Verified (4713 days) | S2 | 5.1.37/5.5/5.6/5.7 | Linux | Any | Autoincrement exceed expected value after INSERT INTO ... SELECT |
65579 | 2012-06-11 7:07 | 2012-06-18 6:38 | MySQL Server: InnoDB storage engine | Verified (4309 days) | S2 | 5.5.24 | Any | Any | InnoDB: Page dump in ascii and hex - filled drive in minutes |
67600 | 2012-11-15 21:40 | 2016-02-25 12:24 | MySQL Server: InnoDB storage engine | Verified | S2 | 5.6.8-rc | Any | Any | Server crashes when opening InnoDB table on read-only media |
67745 | 2012-11-28 17:15 | 2016-07-27 15:46 | MySQL Server: InnoDB storage engine | Verified (4139 days) | S2 | 5.5.28, 5.5.30, 5.7.1 | Linux (RHEL 6.2) | Any | Too much row locks when using SELECT for UPDATE, LIMIT and ORDER BY |
67808 | 2012-12-05 2:45 | 2012-12-26 2:34 | MySQL Server: InnoDB storage engine | Verified (4111 days) | S2 | 5.5.* | Any | Any | in innodb engine, double write and multi-buffer pool instance reduce concurrency |
68876 | 2013-04-05 21:53 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | Verified (4007 days) | S2 | 5.5.30 | Any | Any | Disabling innodb_thread_concurrency might cause queries to hang |
69332 | 2013-05-28 3:22 | 2013-05-28 7:12 | MySQL Server: InnoDB storage engine | Verified (3958 days) | S2 | 5.5+ | Any | Any | InnoDB will overwrite the sam row_id rows in the same table |
70629 | 2013-10-16 8:27 | 2017-05-14 20:45 | MySQL Server: InnoDB storage engine | Verified (3773 days) | S2 | 5.6.14 | Any | Any | InnoDB updated rec_per_key[] statis not published to the optimizer enough often |
71521 | 2014-01-30 8:43 | 2017-04-05 11:45 | MySQL Server: InnoDB storage engine | Verified (3711 days) | S2 | 5.6 | Any | Any | Manual does not list all valid values for innodb_flush_method |
73571 | 2014-08-13 14:20 | 2014-12-14 2:52 | MySQL Server: InnoDB storage engine | Verified (3515 days) | S2 | 5.6.20 | Linux | Any | 'IMPORT TABLESPACE' from corrupted file leads to permanent server failure |
75428 | 2015-01-07 1:24 | 2015-02-26 22:00 | MySQL Server: InnoDB storage engine | Verified (3362 days) | S2 | 5.6 | Any | Any | InnoDB persistent statistics not persistent enough |
75519 | 2015-01-15 17:05 | 2023-09-27 11:59 | MySQL Server: InnoDB storage engine | Verified (3221 days) | S2 | 5.6, 5.6.25 | Any | Any | Potential InnoDB data loss when binary logging is enabled |
76252 | 2015-03-11 1:02 | 2017-04-28 21:13 | MySQL Server: InnoDB storage engine | Verified | S2 | 5.6.23 | Any | Any | InnoDB ROW event handling too zelous for large transactions on table without PK |
76922 | 2015-05-04 8:08 | 2015-05-05 13:24 | MySQL Server: InnoDB storage engine | Verified (3251 days) | S2 | 5.5.43 | Linux (ubuntu 12.04.) | Any | #1030 - Got error -1 from storage engine |
77654 | 2015-07-08 10:55 | 2015-07-08 11:32 | MySQL Server: InnoDB storage engine | Verified (3187 days) | S2 | 5.6.27 | Any | Any | After 5.6.15 innodb_force_recovery greater or equal than 4 is useless |
78066 | 2015-08-14 8:11 | 2017-03-08 7:53 | MySQL Server: InnoDB storage engine | Verified (3150 days) | S2 | 5.6.26, 5.6.27 | Any | Any | Wrong cardinality for InnoDB table in MySQL |
78401 | 2015-09-10 20:56 | 2016-09-14 5:15 | MySQL Server: InnoDB storage engine | Verified (3122 days) | S2 | 5.6, 5.6.26 | Any | Any | "ANALYZE TABLE" may assign temporary values to table stats during its execution |
79469 | 2015-12-01 5:43 | 2017-06-27 5:15 | MySQL Server: InnoDB storage engine | Verified (3041 days) | S2 | 5.7, 5.7.9 | Any | Any | Getting inappropriate error while transport table from MySQL 5.6 to MySQL 5.7 |
79843 | 2016-01-05 8:38 | 2016-02-12 8:00 | MySQL Server: InnoDB storage engine | Verified (2968 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 |
79932 | 2016-01-12 9:27 | 2016-07-21 7:37 | MySQL Server: InnoDB storage engine | Verified (2808 days) | S2 | 5.7.10 | CentOS (7) | Any | Unclear error message while altering compressed table with page compression |
79941 | 2016-01-12 22:06 | 2023-05-02 12:40 | MySQL Server: InnoDB storage engine | Verified (2818 days) | S2 | 5.7.10, 5.7.13 | MacOS | Any | Row size too large new ROW_FORMAT=DYNAMIC |
80739 | 2016-03-15 10:01 | 2018-03-09 8:51 | MySQL Server: InnoDB storage engine | Verified (2212 days) | S2 | 5.7.11 | Any | Any | Table '#sql-1a90_5' uses an extension that doesn't exist in this MySQL version |
81145 | 2016-04-19 19:46 | 2016-05-06 8:10 | MySQL Server: InnoDB storage engine | Verified (2884 days) | S2 | 5.7.11, 5.7.12 | Windows | Any | Sparse file and punch hole compression not working on Windows |
81615 | 2016-05-26 13:56 | 2019-05-19 9:36 | MySQL Server: InnoDB storage engine | Verified (2821 days) | S2 | 5.7.12, 5.7.13 | Any | Any | oltp run will hang while resizing innodb buffer pool size online |
81678 | 2016-06-01 13:32 | 2016-06-02 8:34 | MySQL Server: InnoDB storage engine | Verified (2857 days) | S2 | 5.7.12 | Linux | Any | Transparent page compression is missing from generic binary package |
81804 | 2016-06-10 12:35 | 2019-07-02 10:59 | MySQL Server: InnoDB storage engine | Verified (2846 days) | S2 | 5.7.13 | Any | Any | Memory leak or bug in P_S instrumentation for InnoDB threads |
82298 | 2016-07-20 22:30 | 2016-07-21 6:43 | MySQL Server: InnoDB storage engine | Verified (2808 days) | S2 | 5.5.50, 5.6.31, 5.7.13 | Any | Any | RENAME TABLE fails with "Table ... already exists" error with not existent table |
82320 | 2016-07-22 8:33 | 2016-07-22 9:06 | MySQL Server: InnoDB storage engine | Verified (2807 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 (2807 days) | S2 | 5.6.31 | Any | Any | ALTER table failure with DUPLICATE key crash post index build crashes |
82737 | 2016-08-26 3:53 | 2016-09-02 4:29 | MySQL Server: InnoDB storage engine | Verified (2765 days) | S2 | 5.7.13, 5.7.14 | Any | Any | "SIGKILL myself" for ALTER TABLE DROP COLUMN command |
82798 | 2016-08-30 9:54 | 2016-08-30 12:04 | MySQL Server: InnoDB storage engine | Verified (2768 days) | S2 | 5.6, 5.6.32 | Any | Any | Small buffer pools might be too small for rseg init during crash recovery |
83047 | 2016-09-20 7:40 | 2023-08-15 10:35 | MySQL Server: InnoDB storage engine | Verified (2375 days) | S2 | 5.7 | Ubuntu | Any | Memory usage gradually increases and brings server to halt |
83255 | 2016-10-04 16:02 | 2017-05-04 7:47 | MySQL Server: InnoDB storage engine | Verified (2521 days) | S2 | any, 5.7.15 | Any | Any | --innodb-force-recovery=6 possibly corrupts doublewrite buffer |
83263 | 2016-10-05 8:18 | 2021-06-30 7:40 | MySQL Server: InnoDB storage engine | Verified (2710 days) | S2 | 5.7.15 | Any | Any | ON DELETE constraints are not applied if multiple constraints exist |
84356 | 2016-12-28 11:05 | 2017-01-02 15:35 | MySQL Server: InnoDB storage engine | Verified (2648 days) | S2 | 5.7, 5.7.17 | Ubuntu (16.04) | Any | General tablespace table encryption. |
85605 | 2017-03-24 9:56 | 2019-06-25 15:28 | MySQL Server: InnoDB storage engine | Verified (2562 days) | S2 | 5.7, 8.0 | Any | Any | Corrupted index for ON DELETE CASCADE with self-referential ON DELETE SET NULL |
86234 | 2017-05-09 5:27 | 2017-05-09 6:15 | MySQL Server: InnoDB storage engine | Verified (2516 days) | S2 | 5.5.54, 5.6.35, 5.7.17, 5.6.36, 5.7.18 | Any | Any | InnoDB: Failing assertion: heap->magic_n == MEM_BLOCK_MAGIC_N |
86485 | 2017-05-27 11:15 | 2021-06-30 16:50 | MySQL Server: InnoDB storage engine | Verified | S2 | 5.7.17, 8.0.1 | Any | Any | InnoDB: tried to purge non-delete-marked record |
86705 | 2017-06-15 2:25 | 2018-08-30 11:04 | MySQL Server: InnoDB storage engine | Verified (2472 days) | S2 | 5.5.45, 5.5.56 | Linux (MySQL OOM because of memory leak) | Any | Memory leak of Innodb |
86774 | 2017-06-21 10:26 | 2017-06-21 17:43 | MySQL Server: InnoDB storage engine | Verified (2473 days) | S2 | 5.7/8.0 | Any | Any | DELETE CASCADE on record with another DELETE SET NULL results in corrrupt tables |
87293 | 2017-08-03 5:49 | 2018-02-18 18:29 | MySQL Server: InnoDB storage engine | Verified (2362 days) | S2 | 5.7, 8.0 | Linux | ARM | TTASFutex Lock release barrier (aarch64) |
87933 | 2017-10-02 4:06 | 2018-12-12 21:04 | MySQL Server: InnoDB storage engine | Verified (1934 days) | S2 | 5.7.19 | CentOS | ARM | Scalibility issue on Arm platform with the current UT_RELAX_CPU () code. |
88150 | 2017-10-19 13:08 | 2023-07-05 16:19 | MySQL Server: InnoDB storage engine | Verified (2352 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 |
88422 | 2017-11-09 12:20 | 2017-11-14 14:42 | MySQL Server: InnoDB storage engine | Verified (2327 days) | S2 | 5.7.19 | Any | Any | MySQL 5.7 innodb purge thread get oldest readview could block other transaction |
88757 | 2017-12-05 10:43 | 2020-09-14 6:16 | MySQL Server: InnoDB storage engine | Verified (1702 days) | S2 | 5.7.26, 5.7.30 | Any | Any | convert trx_search_latch_release_if_reserved to a debug assertion/log message |
88783 | 2017-12-06 11:39 | 2017-12-06 12:05 | MySQL Server: InnoDB storage engine | Verified (2305 days) | S2 | 5.7.20, 5.6.38 | CentOS (7) | Any | Incorrect table name error for given empty path with DATA DIRECTORY option |
88863 | 2017-12-11 17:24 | 2020-09-07 7:24 | MySQL Server: InnoDB storage engine | Verified (2299 days) | S2 | 5.6.38, 5.7.20 | Any | Any | COUNT(*) can sometimes return bogus value |
90903 | 2018-05-17 6:13 | 2018-05-23 14:51 | MySQL Server: InnoDB storage engine | Verified (2137 days) | S2 | 5.6/5.7/8.0 | Any | Any | ALTER TABLE doesn't prevent AUTO_INCREMENT out of range in strict mode |
91630 | 2018-07-13 14:47 | 2018-07-15 6:02 | MySQL Server: InnoDB storage engine | Verified (2084 days) | S2 | 5.6.40 | Any | Any | stack-use-after-scope in innobase_convert_identifier() detected by ASan |
91725 | 2018-07-20 9:25 | 2018-07-23 17:26 | MySQL Server: InnoDB storage engine | Verified (2079 days) | S2 | 8.0 | Any | Any | mysql hangs if find corrupt page during crash recovery |
91977 | 2018-08-11 3:57 | 2023-12-09 19:04 | MySQL Server: InnoDB storage engine | Verified | S2 | 5.7.17 | Any | Any | Dropping Large Table Causes Semaphore Waits; No Other Work Possible |
94338 | 2019-02-15 4:58 | 2021-02-25 7:04 | MySQL Server: InnoDB storage engine | Verified (1866 days) | S2 | 5.7.25, 5.6.43 | Linux | Any | Dirty read-like behavior in READ COMMITTED transaction |
95272 | 2019-05-07 9:05 | 2019-05-07 12:14 | MySQL Server: InnoDB storage engine | Verified (1788 days) | S2 | 5.7, 5.7.26 | Any | Any | Potential InnoDB SPATIAL INDEX corruption during root page split |
95898 | 2019-06-20 14:02 | 2023-10-18 11:58 | MySQL Server: InnoDB storage engine | Verified (163 days) | S2 | 5.7, 5.7.26, 8.0.17, 5.7.27 | Any | Any | InnoDB releases memory of table only on shutdown if table has FK constraint |
98132 | 2020-01-06 10:55 | 2022-01-04 12:51 | MySQL Server: InnoDB storage engine | Verified (1543 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 |
98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (1458 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
98427 | 2020-01-29 11:59 | 2020-08-19 7:50 | MySQL Server: InnoDB storage engine | Verified (1318 days) | S2 | 8.0, 8.0.19 | Any | Any | InnoDB FullText AUX Tables are broken in 8.0 |
99295 | 2020-04-18 7:56 | 2020-04-20 10:04 | MySQL Server: InnoDB storage engine | Verified (1439 days) | S2 | 8.0.19 | Any | Any | InnoDB in-memory estimate is wrong after an index is created |
99763 | 2020-06-03 6:28 | 2020-06-03 6:44 | MySQL Server: InnoDB storage engine | Verified (1395 days) | S2 | 8.0, 8.0.20 | Any | Any | error log reports Invalid (old?) table or database name |
Showing 1-90 of 654 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |