Showing 1–30 of 51
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 54605 | 2010-06-18 6:22 | 2011-02-16 23:44 | MySQL Server: Replication | Won't fix (5862 days) | S3 | 5.0, 5.1, 5.5 | Any | Any | Xid_log_event::do_apply_event() should update future_group_master_log_pos |
| 58157 | 2010-11-12 9:21 | 2012-07-16 23:40 | MySQL Server: InnoDB Plugin storage engine | Closed (5240 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 (5424 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 (5811 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 (5051 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 (5650 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 (5450 days) | S3 | 5.1.59, 5.5.15 | Any | Any | Race condition in check_temp_dir() from multiple mysqld instances |
| 66567 | 2012-08-28 7:57 | 2012-11-13 18:32 | MySQL Server: Security: Privileges | Closed (5120 days) | S5 | 5.6.6, 5.6.7 | Any | Any | my_rnd_ssl() is very expensive for authentication |
| 67044 | 2012-10-02 0:21 | 2012-12-29 16:37 | MySQL Server: InnoDB Plugin storage engine | Closed (5074 days) | S5 | 5.1, 5.5, 5.6 | Any | Any | Secondary index updates make consistent reads do O(N^2) undo page lookups |
| 67643 | 2012-11-20 1:22 | 2013-04-03 9:58 | MySQL Server: Command-line Clients | Closed (4979 days) | S4 | 5.6 | Any | Any | Increase mysqlbinlog version (3.4 or something higher than 3.3) in MySQL 5.6 |
| 67879 | 2012-12-11 22:59 | 2014-12-19 4:59 | MySQL Server: Replication | Closed (5021 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | Slave deadlock caused by stop slave, show slave status and global read lock |
| 68077 | 2013-01-14 3:37 | 2013-04-03 11:33 | MySQL Server: InnoDB storage engine | Closed (4979 days) | S5 | 5.6 | Any | Any | Mixing 4K/16K blocks increases 8K free blocks and holds buf pool mutex longer |
| 68220 | 2013-01-29 18:59 | 2020-03-09 18:32 | MySQL Server: Replication | Verified (5042 days) | S3 | 5.6.9, 5.7.1 | Any | Any | innodb_rows_updated is misleading on slave when *info_repository = TABLE |
| 68229 | 2013-01-31 1:34 | 2013-01-31 14:03 | MySQL Server: Replication | Closed (5041 days) | S2 | 5.6.9 | Any | Any | MTS may get SIGSEGV because of partial deletes on rli->curr_group_da |
| 68250 | 2013-02-02 0:35 | 2013-04-23 13:10 | MySQL Server: Replication | Not a Bug (4959 days) | S3 | 5.6.9 | Any | Any | Current semi-synchronous replication may cause deadlock |
| 68251 | 2013-02-02 1:09 | 2013-05-28 6:58 | MySQL Server: Replication | Closed (4924 days) | S3 | 5.6.9 | Any | Any | 3-way deadlock on semisync replication and binlog rotate |
| 68281 | 2013-02-05 23:19 | 2013-03-07 15:01 | MySQL Server: Documentation | Not a Bug (5006 days) | S5 | 5.6.10 | Any | Any | sync_master_info=1 kills slave MTS concurrency |
| 68351 | 2013-02-12 18:44 | 2013-02-13 8:11 | MySQL Server: Replication | Verified (5028 days) | S3 | 5.6.10 | Any | Any | Out of range updates/deletes are not written to binlog |
| 68465 | 2013-02-22 18:57 | 2014-09-25 10:26 | MySQL Server: Documentation | Closed (4911 days) | S2 | 5.6.10 | Any | Any | Make slave_transaction_retries work with MTS |
| 68506 | 2013-02-27 7:23 | 2015-05-08 15:06 | MySQL Server: Replication | Closed (4936 days) | S2 | 5.6.10 | Any | Any | Got SIGSEGV on MTS recovery + SQL thread error |
| 68566 | 2013-03-05 0:50 | 2022-03-06 15:12 | MySQL Server: Command-line Clients | Verified (4993 days) | S4 | 5.6.10, 8.0 | Any | Any | mysqlbinlog should be more friendly with GTID |
| 68659 | 2013-03-13 7:47 | 2013-03-13 9:01 | MySQL Server: InnoDB storage engine | Analyzing (5000 days) | S5 | 5.6.10 | Any | Any | InnoDB Linux native aio should submit more i/o requests at once |
| 69096 | 2013-04-29 20:52 | 2013-07-09 10:01 | MySQL Server: Replication | Closed (4882 days) | S2 | 5.6.11 | Any | Any | GTID_NEXT_LIST session variable is not visible |
| 69097 | 2013-04-29 22:51 | 2022-05-05 9:01 | MySQL Server: Replication | Closed (4438 days) | S2 | 5.6.11 | Any | Any | mysqld scans all binary logs on crash recovery |
| 69316 | 2013-05-24 23:50 | 2013-07-05 15:56 | MySQL Server: InnoDB storage engine | Closed (4886 days) | S5 | 5.6.11 | Any | Any | Drop/Alter table takes much longer time in 5.6 than 5.5 |
| 69341 | 2013-05-29 0:55 | 2016-04-07 5:46 | MySQL Server: Replication | Closed (4886 days) | S5 | 5.6.11 | Any | Any | semi-sync replication is very slow with many clients |
| 69493 | 2013-06-17 17:53 | 2018-09-25 21:51 | Tests: Replication | Duplicate (4903 days) | S7 | 5.6.12 | Any | Any | Slave deadlock by show slave status, global read lock and slave_master_info |
| 69943 | 2013-08-07 0:46 | 2014-02-03 10:12 | MySQL Server: Replication | Closed (4769 days) | S1 | 5.6.13 | Any | Any | Transactions skipped on slave after "stop/start slave" using GTID replication |
| 70026 | 2013-08-14 7:26 | 2014-11-18 21:23 | MySQL Server: C API (client library) | Closed (4547 days) | S2 | 5.6.13 | Any | Any | Auto reconnect does not work with 5.6 libmysqlclient |
| 70172 | 2013-08-28 4:37 | 2013-10-29 11:50 | MySQL Server: InnoDB storage engine | Closed (4770 days) | S5 | 5.6.13 | Any | Any | trx_create() and trx_free() are called at every memcached get request |
Showing 1–30 of 51
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.232 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.