Showing 1-30 of 51 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
69943 | 2013-08-07 0:46 | 2014-02-03 10:12 | MySQL Server: Replication | Closed (3966 days) | S1 | 5.6.13 | Any | Any | Transactions skipped on slave after "stop/start slave" using GTID replication |
68465 | 2013-02-22 18:57 | 2014-09-25 10:26 | MySQL Server: Documentation | Closed (4108 days) | S2 | 5.6.10 | Any | Any | Make slave_transaction_retries work with MTS |
89272 | 2018-01-16 22:52 | 2018-06-19 10:29 | MySQL Server: Replication | Closed (2306 days) | S2 | 5.6.39 | Any | Any | Binlog and Engine become inconsistent when binlog cache file gets out of space |
70669 | 2013-10-20 4:25 | 2014-03-29 8:25 | MySQL Server: Replication | Closed (3846 days) | S2 | 5.6.14 | Any | Any | Slave can't continue replication after master's crash recovery |
70327 | 2013-09-13 8:05 | 2014-09-30 13:47 | MySQL Server: Replication | Closed (3658 days) | S2 | 5.6.13 | Any | Any | Assersion error when setting future binlog file/pos with semisync |
70307 | 2013-09-12 0:33 | 2015-02-12 12:37 | MySQL Server: Replication | Closed (3559 days) | S2 | 5.6.13 | Any | Any | Another deadlock on FLUSH TABLES WITH READ LOCK + SHOW SLAVE STATUS |
68506 | 2013-02-27 7:23 | 2015-05-08 15:06 | MySQL Server: Replication | Closed (4133 days) | S2 | 5.6.10 | Any | Any | Got SIGSEGV on MTS recovery + SQL thread error |
70026 | 2013-08-14 7:26 | 2014-11-18 21:23 | MySQL Server: C API (client library) | Closed (3744 days) | S2 | 5.6.13 | Any | Any | Auto reconnect does not work with 5.6 libmysqlclient |
69096 | 2013-04-29 20:52 | 2013-07-09 10:01 | MySQL Server: Replication | Closed (4079 days) | S2 | 5.6.11 | Any | Any | GTID_NEXT_LIST session variable is not visible |
67879 | 2012-12-11 22:59 | 2014-12-19 4:59 | MySQL Server: Replication | Closed (4218 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | Slave deadlock caused by stop slave, show slave status and global read lock |
68229 | 2013-01-31 1:34 | 2013-01-31 14:03 | MySQL Server: Replication | Closed (4238 days) | S2 | 5.6.9 | Any | Any | MTS may get SIGSEGV because of partial deletes on rli->curr_group_da |
69097 | 2013-04-29 22:51 | 2022-05-05 9:01 | MySQL Server: Replication | Closed (3635 days) | S2 | 5.6.11 | Any | Any | mysqld scans all binary logs on crash recovery |
72662 | 2014-05-16 0:34 | 2014-05-16 18:06 | MySQL Server: InnoDB storage engine | Not a Bug (3768 days) | S3 | 5.6.18 | Any | Any | Extending VARCHAR can't be done online in InnoDB |
75019 | 2014-11-27 6:52 | 2022-04-10 20:45 | MySQL Server: InnoDB storage engine | Verified (3572 days) | S3 | 5.7.5 lab | Any | Any | Assertion error on punch hole + 64k page size + low buffer pool size |
70659 | 2013-10-18 18:31 | 2021-05-07 12:42 | MySQL Server: Replication | Verified (3975 days) | S3 | 5.6.14 | Any | Any | Make crash safe slave work with gtid + less durable settings |
70711 | 2013-10-23 18:21 | 2015-06-24 4:30 | MySQL Server: Replication | Closed (3427 days) | S3 | 5.6.14 | Any | Any | mysqlbinlog prints invalid SQL from relay logs when GTID is enabled |
70577 | 2013-10-09 21:47 | 2013-10-15 18:19 | MySQL Server: Performance Schema | Closed (3981 days) | S3 | 5.6.14 | Any | Any | Read/Write mutexes on Binlog delegate classes are not counted on perf schema |
70641 | 2013-10-16 23:56 | 2014-09-25 11:46 | MySQL Server: Partitions | Closed (3694 days) | S3 | 5.6.14 | Any | Any | 5.6 partitions use much more memory than 5.1 |
68251 | 2013-02-02 1:09 | 2013-05-28 6:58 | MySQL Server: Replication | Closed (4121 days) | S3 | 5.6.9 | Any | Any | 3-way deadlock on semisync replication and binlog rotate |
58157 | 2010-11-12 9:21 | 2012-07-16 23:40 | MySQL Server: InnoDB Plugin storage engine | Closed (4437 days) | S3 | 5.1.51, 5.0, 5.6.1 | Any | Any | InnoDB locks an unmatched row even though using RBR and RC |
58966 | 2010-12-16 8:48 | 2012-01-15 19:13 | MySQL Server: InnoDB storage engine | Verified (4621 days) | S3 | 5.5 | Any | Any | Too less agressive dirty page flushing in 5.5 |
59131 | 2010-12-23 13:47 | 2011-02-16 23:44 | MySQL Server: Optimizer | Duplicate (5008 days) | S3 | 5.1, 5.5 | Any | Any | Calculating optimizer cost to skip filesort is wrong |
60964 | 2011-04-24 7:51 | 2024-07-16 3:47 | MySQL Server: Row Based Replication ( RBR ) | Not a Bug (4248 days) | S3 | 5.1.56, 5.6.3 | Any | Any | row based relay log events are lost from mysqlbinlog output |
61384 | 2011-06-02 11:55 | 2011-06-02 12:01 | MySQL Server: Security: Privileges | Duplicate (4847 days) | S3 | 5.1.57 | Any | Any | Can't connect MySQL 5.1.57 from old(4.0) clients |
62055 | 2011-08-02 10:24 | 2011-12-19 1:29 | MySQL Server: Replication | Closed (4647 days) | S3 | 5.1.59, 5.5.15 | Any | Any | Race condition in check_temp_dir() from multiple mysqld instances |
54605 | 2010-06-18 6:22 | 2011-02-16 23:44 | MySQL Server: Replication | Won't fix (5059 days) | S3 | 5.0, 5.1, 5.5 | Any | Any | Xid_log_event::do_apply_event() should update future_group_master_log_pos |
96827 | 2019-09-11 0:24 | 2019-09-11 7:43 | MySQL Server: Command-line Clients | Verified (1824 days) | S3 | 5.6, 8.0.17, 5.6.45, 5.7.27 | Any | Any | mysqlbinlog needs options to abort if invalid events are found on in-use binlogs |
68220 | 2013-01-29 18:59 | 2020-03-09 18:32 | MySQL Server: Replication | Verified (4239 days) | S3 | 5.6.9, 5.7.1 | Any | Any | innodb_rows_updated is misleading on slave when *info_repository = TABLE |
68250 | 2013-02-02 0:35 | 2013-04-23 13:10 | MySQL Server: Replication | Not a Bug (4156 days) | S3 | 5.6.9 | Any | Any | Current semi-synchronous replication may cause deadlock |
68351 | 2013-02-12 18:44 | 2013-02-13 8:11 | MySQL Server: Replication | Verified (4225 days) | S3 | 5.6.10 | Any | Any | Out of range updates/deletes are not written to binlog |
Showing 1-30 of 51 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |