Showing 1-30 of 38 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
69444 | 2013-06-11 21:25 | 2014-07-11 4:57 | MySQL Server: Replication | Verified (3968 days) | S3 | 5.6.12 | Any | Any | Replication is not crash safe with DDL statements |
71959 | 2014-03-06 22:30 | 2014-03-12 9:58 | MySQL Server: Replication | Verified (3695 days) | S2 | 5.7.2 | Any | Any | non blocking SHOW MASTER STATUS / SHOW BINARY LOGS |
71216 | 2013-12-23 11:22 | 2013-12-23 12:56 | MySQL Server: Locking | Verified (3774 days) | S3 | 5.6.16-bzr | Any | Any | WITH CONSISTENT SNAPSHOT doesn't isolate from concurrent DDL on stored programs |
71215 | 2013-12-23 10:57 | 2013-12-23 12:52 | MySQL Server: Locking | Verified (3774 days) | S3 | 5.6.16-bzr | Any | Any | WITH CONSISTENT SNAPSHOT doesn't isolate from some concurrent ALTER TABLEs |
71214 | 2013-12-23 10:47 | 2013-12-23 12:48 | MySQL Server: Locking | Verified (3774 days) | S3 | 5.6.16 | Any | Any | WITH CONSISTENT SNAPSHOT doesn't isolate from concurrent RENAME TABLE |
71164 | 2013-12-17 16:38 | 2014-09-05 2:44 | MySQL Server: InnoDB storage engine | Verified (3771 days) | S3 | 5.6.15 | Any | Any | an autocommit SELECT was not treated as autocommit non-lock trx |
71130 | 2013-12-11 20:43 | 2013-12-17 17:35 | MySQL Server: Replication | Verified (3780 days) | S5 | 5.6.15 | Any | Any | 5.6 SQL thread is much slower than 5.1/5.5 |
71027 | 2013-11-27 19:50 | 2013-11-28 13:31 | MySQL Server: Optimizer | Verified (3799 days) | S3 | 5.6.11, 5.6.14 | Any | Any | Full-scan UPDATE is EXPLAINED confusingly |
70778 | 2013-10-30 22:41 | 2015-01-25 16:11 | MySQL Server: DDL | Verified (3827 days) | S3 | mysql-5.6.14 | Any | Any | SHOW CREATE TABLE doesn't put STATS_PERSISTENT into version specific comments |
70629 | 2013-10-16 8:27 | 2017-05-14 20:45 | MySQL Server: InnoDB storage engine | Verified (3798 days) | S2 | 5.6.14 | Any | Any | InnoDB updated rec_per_key[] statis not published to the optimizer enough often |
70342 | 2013-09-13 22:18 | 2013-09-21 15:44 | MySQL Server: Replication | Verified (3867 days) | S5 | 5.6.13 | Any | Any | master_info_repository=FILE calls my_b_printf too often |
70296 | 2013-09-11 9:04 | 2013-09-11 11:50 | MySQL Server: Logging | Verified (3877 days) | S3 | 5.6.13 | Any | Any | replication errors are reported inconsistently |
70287 | 2013-09-10 18:20 | 2013-09-11 11:15 | MySQL Server: Command-line Clients | Verified (3877 days) | S3 | 5.5 | Any | Any | mysqlbinlog does nog recognize incompatible binlog format |
69454 | 2013-06-12 18:46 | 2013-06-12 21:07 | MySQL Server: Replication | Verified (3968 days) | S3 | 5.x | Any | Any | there are better ways to sync server clocks than MySQL query |
49456 | 2009-12-04 12:04 | 2018-04-08 20:45 | MySQL Server | Analyzing (5254 days) | S3 | mysql-5.1-rep+3 | Any | Any | replication out of sync |
69236 | 2013-05-14 22:12 | 2016-03-31 12:22 | MySQL Server: InnoDB storage engine | Verified (3157 days) | S5 | 5.6.11 | Any | Any | performance regressions for single-threaded workloads, part 2 |
68555 | 2013-03-03 21:34 | 2013-11-11 15:53 | MySQL Server: InnoDB storage engine | Verified (3816 days) | S5 | 5.6.10 | Any | Any | thread convoys from log_checkpoint_margin with innodb_buffer_pool_instances > 1 |
68351 | 2013-02-12 18:44 | 2013-02-13 8:11 | MySQL Server: Replication | Verified (4087 days) | S3 | 5.6.10 | Any | Any | Out of range updates/deletes are not written to binlog |
68413 | 2013-02-18 2:45 | 2013-09-25 2:58 | MySQL Server: Performance Schema | Verified (3863 days) | S5 | 5.6.10, 5.6.13 | Any | Any | performance_schema overhead is at least 10% |
68481 | 2013-02-25 2:58 | 2014-11-04 11:47 | MySQL Server: InnoDB storage engine | Verified (4075 days) | S3 | 5.6.10 | Any | Any | InnoDB LRU flushing for MySQL 5.6 needs work |
68544 | 2013-03-01 19:52 | 2013-03-02 14:36 | MySQL Server: InnoDB storage engine | Verified (4070 days) | S3 | 5.5 | Any | Any | Ability to support multiple buffer pools with per-table assignment |
68207 | 2013-01-28 17:01 | 2013-01-31 13:41 | MySQL Server: InnoDB storage engine | Verified (4100 days) | S3 | 5.6 | Any | Any | too much contention on "os_mutex" |
68023 | 2013-01-03 19:42 | 2015-06-03 10:58 | MySQL Server: InnoDB storage engine | Verified (4109 days) | S3 | All | Any | Any | InnoDB reserves an excessive amount of disk space for write operations |
68545 | 2013-03-01 19:56 | 2013-05-27 9:41 | MySQL Server: InnoDB storage engine | Verified (3984 days) | S3 | 5.5 | Any | Any | InnoDB should check left/right pages when target page is full to avoid splitting |
68546 | 2013-03-01 19:58 | 2013-08-19 17:15 | MySQL Server: InnoDB storage engine | Verified (3900 days) | S3 | 5.5 | Any | Any | InnoDB stores PRIMARY KEY fields in unique secondary index non-leaf pages |
64673 | 2012-03-16 23:14 | 2012-03-18 17:15 | MySQL Server: InnoDB Plugin storage engine | Verified (4420 days) | S5 | 5.1 | Any | Any | InnoDB allocates too many empty pages in ibd files |
64181 | 2012-01-31 14:41 | 2012-02-09 12:20 | MySQL Server: InnoDB Plugin storage engine | Verified (4462 days) | S5 | 5.1.52, 5.1.61 | Any | Any | unzip_LRU length management might need to be updated for SSD |
60593 | 2011-03-22 20:12 | 2018-03-09 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2238 days) | S5 | 5.5.8 | Any | Any | Excessive number of fsync() calls when populating a small table with a large row |
68659 | 2013-03-13 7:47 | 2013-03-13 9:01 | MySQL Server: InnoDB storage engine | Analyzing (4059 days) | S5 | 5.6.10 | Any | Any | InnoDB Linux native aio should submit more i/o requests at once |
68775 | 2013-03-26 9:22 | 2014-04-29 12:01 | MySQL Server: Command-line Clients | Verified (4046 days) | S3 | 5.6.10 | Any (linux) | Any | GTID_PURGED variable makes mysql dump non backward compatible |
Showing 1-30 of 38 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |