« Show Previous 30 Entries | Showing 31-60 of 103 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
69588 | 2013-06-26 15:45 | 2014-07-22 18:49 | MySQL Server: InnoDB storage engine | Verified (4011 days) | S3 | 5.5.31, 5.6.21 | Linux (RHEL 6.4) | Any | MyISAM to InnoDB compressed slower than MyISAM to InnoDB, Then InnoDB to Compres |
58060 | 2010-11-08 19:06 | 2011-02-16 23:44 | MySQL Server: Information schema | Verified (5352 days) | S3 | 5.5.7-rc-debug | Any | Any | Inconsistency in row format reported through I_S |
69332 | 2013-05-28 3:22 | 2013-05-28 7:12 | MySQL Server: InnoDB storage engine | Verified (4430 days) | S2 | 5.5+ | Any | Any | InnoDB will overwrite the sam row_id rows in the same table |
86460 | 2017-05-25 14:19 | 2017-06-14 3:38 | MySQL Server: InnoDB storage engine | Verified (2966 days) | S3 | 5.6 5.7 | Any | Any | Deleted DOCID are not maintained during OPTIMIZE of InnoDB FULLTEXT tables |
75519 | 2015-01-15 17:05 | 2023-09-27 11:59 | MySQL Server: InnoDB storage engine | Verified (3693 days) | S2 | 5.6, 5.6.25 | Any | Any | Potential InnoDB data loss when binary logging is enabled |
82798 | 2016-08-30 9:54 | 2016-08-30 12:04 | MySQL Server: InnoDB storage engine | Verified (3240 days) | S2 | 5.6, 5.6.32 | Any | Any | Small buffer pools might be too small for rseg init during crash recovery |
95122 | 2019-04-25 7:03 | 2019-04-25 13:54 | MySQL Server: InnoDB storage engine | Verified (2272 days) | S3 | 5.6, 5.7 | Any | Any | No need to get log_sys->log_flush_order_mutex during InnoDB crash recovery |
68987 | 2013-04-17 21:48 | 2018-04-13 8:25 | MySQL Server: InnoDB storage engine | Verified (3161 days) | S3 | 5.6.10 | Linux (CentOS 6.4) | Any | MySQL crash with InnoDB assertion failure in file pars0pars.cc |
72303 | 2014-04-10 10:31 | 2014-04-15 23:44 | MySQL Server: InnoDB storage engine | Verified (4108 days) | S3 | 5.6.15 | Any | Any | Improve tablespace import logging, documentation (and speed) |
71747 | 2014-02-17 9:42 | 2014-02-17 10:29 | MySQL Server: InnoDB storage engine | Verified (4165 days) | S3 | 5.6.15, 5.6.16 | Any | Any | Remove innodb_io_capacity setting depending on setting of innodb_io_capacity_max |
71060 | 2013-12-03 14:08 | 2013-12-05 13:31 | MySQL Server: Locking | Verified (4241 days) | S2 | 5.6.15, 5.6.16, 5.5.35, 5.1.74 | Any | Any | INSERT-SELECT statement takes shared locks in trigger and causes deadlock |
71551 | 2014-02-01 16:02 | 2021-05-25 13:04 | MySQL Server: FULLTEXT search | Verified (4008 days) | S2 | 5.6.15, 5.6.21, 8.0.24 | Windows | Any | ft_boolean_syntax has no impact on InnoDB FTS |
78423 | 2015-09-14 2:27 | 2022-10-26 12:05 | MySQL Server: InnoDB storage engine | Verified (3565 days) | S3 | 5.6.16, 5.6.26 | Linux | Any | fts: Duplicate FTS_DOC_ID value on table / Cannot find index FTS_DOC_ID_INDEX |
73571 | 2014-08-13 14:20 | 2014-12-14 2:52 | MySQL Server: InnoDB storage engine | Verified (3987 days) | S2 | 5.6.20 | Linux | Any | 'IMPORT TABLESPACE' from corrupted file leads to permanent server failure |
75763 | 2015-02-04 13:29 | 2015-02-05 8:19 | MySQL Server: FULLTEXT search | Verified (3812 days) | S2 | 5.6.21, 5.6.24 | Any | Any | InnoDB FULLTEXT index reduces insert performance by up to 6x on JSON docs |
75616 | 2015-01-24 6:14 | 2018-04-24 13:15 | MySQL Server: InnoDB storage engine | Verified (3673 days) | S1 | 5.6.22, 5.6.23 | FreeBSD | Any | Cannot initialize or use raw device as InnoDB File |
76210 | 2015-03-07 21:58 | 2015-03-09 9:07 | MySQL Server: FULLTEXT search | Verified (3780 days) | S2 | 5.6.22, 5.6.25, 5.7.7 | Any | Any | InnoDB FULLTEXT index returns wrong results for key/value pair documents |
80723 | 2016-03-14 8:40 | 2022-11-03 12:29 | MySQL Server: FULLTEXT search | Verified (3385 days) | S3 | 5.6.23, 5.6.29, 5.7.11 | Any | Any | @ Distance operator does not bring expected results when used in with wildcards |
78255 | 2015-08-28 8:37 | 2015-08-28 14:35 | MySQL Server: InnoDB storage engine | Verified (3608 days) | S3 | 5.6.24 (and earlier, too) | Any | Any | Foreign key allowed between InnoDB and MyISAM if "set foreign_key_checks=0" |
75962 | 2015-02-19 3:14 | 2015-03-03 20:46 | MySQL Server: InnoDB storage engine | Verified (3786 days) | S3 | 5.6.24, 5.7.6 | Any | Any | Innodb calls fsync when freeing a LRU page to fulfill page request |
78164 | 2015-08-21 10:11 | 2015-11-25 18:23 | MySQL Server: Partitions | Verified (3615 days) | S2 | 5.6.26 , 5.6.27, 5.7.9 | Ubuntu (14.04.2 64bit) | Any | alter table command affect partitioned table data directory |
78066 | 2015-08-14 8:11 | 2017-03-08 7:53 | MySQL Server: InnoDB storage engine | Verified (3622 days) | S2 | 5.6.26, 5.6.27 | Any | Any | Wrong cardinality for InnoDB table in MySQL |
62018 | 2011-07-28 15:15 | 2018-02-11 20:45 | MySQL Server: InnoDB storage engine | Verified (4562 days) | S5 | 5.6.3 | Any | Any | innodb adaptive hash index mutex contention |
85970 | 2017-04-17 7:44 | 2017-04-17 13:54 | MySQL Server: InnoDB storage engine | Verified (3010 days) | S3 | 5.6.36 | Linux | Any | Memory leak with transactions greater than 10% of the total redo log size |
78485 | 2015-09-19 10:12 | 2019-10-30 17:31 | MySQL Server: FULLTEXT search | Verified (3586 days) | S3 | 5.6/5.7 | Ubuntu | Any | Fulltext search with char * produces a syntax error with InnoDB |
83776 | 2016-11-10 20:42 | 2016-11-11 18:51 | MySQL Server: FULLTEXT search | Verified (3167 days) | S3 | 5.6/5.7/8.0 | Any | Any | InnoDB FULLTEXT search returns incorrect result for operators on ignored words |
59710 | 2011-01-25 10:11 | 2022-04-10 20:45 | MySQL Server: InnoDB storage engine | Verified | S3 | 5.6+ | Any | Any | InnoDB mutex_t size should be trimmed |
84366 | 2016-12-29 6:39 | 2018-06-13 12:19 | MySQL Server: InnoDB storage engine | Verified (2720 days) | S3 | 5.6+ | Any | Any | InnoDB index dives do not detect concurrent tree changes, return bogus estimates |
77396 | 2015-06-18 4:55 | 2015-06-18 6:10 | MySQL Server: InnoDB storage engine | Verified (3679 days) | S3 | 5.7 | Any | Any | Remove most srv_was_started uses now that InnoDB is mandatory |
90604 | 2018-04-24 13:50 | 2018-04-25 4:41 | MySQL Server: InnoDB storage engine | Verified (2637 days) | S5 | 5.7 | CentOS | Any | ut_rnd_ulint_counter () : Default delay for spin wait gives better performance |
« Show Previous 30 Entries | Showing 31-60 of 103 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |