Showing 1-30 of 131 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
71523 | 2014-01-30 11:23 | 2016-01-23 12:04 | MySQL Server: Replication | Closed (2988 days) | S4 | 5.7.3 | Any | Any | mysqlbinlog does not show commit_seq_no used for parallel slaves |
71527 | 2014-01-30 15:19 | 2014-02-06 11:51 | MySQL Server | Closed (3704 days) | S2 | 5.6.15 & 5.7.3 | Any | Any | With GTID_MODE=ON, anonymous transactions are assigned local GTIDs on slaves. |
71529 | 2014-01-30 15:25 | 2014-02-06 12:25 | MySQL Server: Replication | Verified (3704 days) | S2 | 5.6.15 & 5.7.3 | Any | Any | GTID automatic positioning skips anonymous transactions. |
71543 | 2014-01-31 14:08 | 2015-11-16 12:48 | MySQL Server: Replication | Verified (3059 days) | S4 | 5.6.15 & 5.7.3 | Any | Any | A new GTID_MODE is needed to evaluate/migrate to GTID: ANONYMOUS_IN-GTID_OUT. |
72610 | 2014-05-11 8:03 | 2014-11-04 14:35 | MySQL Server: Replication | Closed (3542 days) | S2 | 5.6.19 | Linux | Any | Out of memory replicating using RBR and slave having different data types. |
73038 | 2014-06-18 14:14 | 2014-07-08 11:52 | MySQL Server: Documentation | Closed (3552 days) | S3 | 5.6.19 | Any | Any | Better document (or fix) relay_log_recovery. |
73039 | 2014-06-18 14:15 | 2014-12-10 14:43 | MySQL Server: Replication | Closed (3439 days) | S3 | 5.6.19, 5.6.20, 5.6.22 | Any | Any | relay_log_recovery KO when CHANGE MASTER without FILE and SQL_THREAD not started |
74089 | 2014-09-25 21:21 | 2015-09-01 13:57 | MySQL Server: Replication | Closed (3132 days) | S4 | 5.6.21 | Any | Any | Report Relay_Log_File and Relay_Log_Pos on relay-log-recovery. |
74111 | 2014-09-26 16:01 | 2014-12-03 15:20 | MySQL Server: Errors | Closed (3440 days) | S3 | 5.7.5/5.6 | Linux (CentOS 6.5) | Any | When the socket option is relative, mysqld startup script fails on CentOS 6. |
74321 | 2014-10-10 13:34 | 2020-03-02 10:27 | MySQL Server: Replication | Verified (1488 days) | S4 | 5.6.21 | Any | Any | Execute relay-log-recovery only when needed. |
74323 | 2014-10-10 13:38 | 2020-03-02 10:27 | MySQL Server: Replication | Verified (1488 days) | S4 | 5.6.21 | Any | Any | Avoid overloading the master NIC on relay-log-recovery of a lagging slave. |
74324 | 2014-10-10 13:41 | 2020-03-02 10:28 | MySQL Server: Replication | Verified (1488 days) | S4 | 5.6.21 | Any | Any | Make keeping relay logs (relay_log_purge=0) crash safe. |
75393 | 2015-01-02 14:45 | 2018-08-21 17:54 | MySQL Server: Replication | Open (2047 days) | S4 | 5.7.5 | Any | Any | Clarify the way the table mysql.gtid_executed is updated. |
75394 | 2015-01-02 14:45 | 2019-01-24 10:53 | MySQL Server: Documentation | Closed (1891 days) | S4 | 5.6 and 5.7 | Any | Any | Improve documentation of binlog_order_commits. |
75395 | 2015-01-02 14:46 | 2018-07-25 17:16 | MySQL Server: Documentation | Closed (2074 days) | S4 | 5.7.5 | Any | Any | Explain relation between slave_preserve_commit_order and binlog_order_commit. |
75396 | 2015-01-02 14:46 | 2020-03-02 10:14 | MySQL Server: Replication | Closed (1488 days) | S4 | 5.7.5 | Any | Any | Allow slave_preserve_commit_order without log-slave-updates. |
77438 | 2015-06-22 15:46 | 2018-02-12 7:36 | MySQL Server: Replication | Duplicate (2237 days) | S4 | 5.7 | Any | Any | Extend RESET MASTER to allow specifying next binary log. |
78262 | 2015-08-28 15:19 | 2015-12-07 18:51 | MySQL Server: InnoDB storage engine | Closed (3035 days) | S5 | 5.6.26 | Any (CentOS release 6.6) | Any | Adding indexes on empty table is slow with large innodb_sort_buffer_size. |
78270 | 2015-08-29 22:50 | 2016-01-13 20:44 | MySQL Server: InnoDB storage engine | Closed (2998 days) | S3 | MySQL 5.6.26. | Any (CentOS release 6.6) | Any | Unexpected Memory Consumption for Bulk Index Creation in InnoDB. |
80102 | 2016-01-21 20:08 | 2017-07-17 8:05 | MySQL Server: Replication | Closed (2853 days) | S3 | 5.6.28, 5.7.10, 5.7.12 | Any | Any | Message in log after MTS crash misleading. |
80103 | 2016-01-21 20:45 | 2018-01-04 8:51 | MySQL Server: Replication | Closed (2538 days) | S2 | 5.7.10, 5.7.12 | Any | Any | MTS LOGICAL_CLOCK with slave_preserve_commit_order=1 not replication crash safe. |
82667 | 2016-08-20 11:19 | 2018-08-31 10:53 | MySQL Server: Documentation | Closed (2050 days) | S3 | 5.6 and 5.7 documentations | Any | Any | Please clarify resiliency introduced by master_info_repository to TABLE. |
84038 | 2016-12-02 10:01 | 2017-03-21 17:08 | MySQL Server: InnoDB storage engine | Closed (2565 days) | S3 | 5.7.15-log, 5.7.16 | CentOS (CentOS release 6.8 (Final)) | Any | Errors when restarting MySQL after FLUSH TABLES FOR EXPORT, RENAME and DROP. |
84439 | 2017-01-07 10:40 | 2017-01-09 5:21 | MySQL Server: InnoDB storage engine | Verified (2636 days) | S3 | 5.7.17-log | Any | Any | Table of row size of ~800 bytes does not compress with KEY_BLOCK_SIZE=1. |
84467 | 2017-01-11 8:22 | 2019-06-28 19:53 | MySQL Server: InnoDB storage engine | Verified (2074 days) | S3 | 5.7.17-log | Any | Any | ALTERing KEY_BLOCK_SIZE keeps the old kbs in KEYs. |
84557 | 2017-01-18 16:50 | 2017-01-19 19:07 | MySQL Server: Errors | Verified (2626 days) | S4 | 5.6 and 5.7 | Any | Any | Hide specific warnings from SHOW WARNINGS. |
84578 | 2017-01-20 9:53 | 2017-01-21 8:01 | MySQL Server: Errors | Verified (2624 days) | S4 | 5.6 and 5.7 | Any | Any | Add a SHOW WARNINGS SUMMARY function. |
84747 | 2017-01-31 16:40 | 2020-05-14 4:38 | MySQL Server: Replication | Verified (2608 days) | S4 | 5.7 | Any | Any | Expose last transaction GTID in a session variable. |
84748 | 2017-01-31 16:57 | 2017-02-06 7:29 | MySQL Server: Replication | Verified (2608 days) | S4 | 5.7 | Any | Any | Request transaction GTID in OK packet on COMMIT(without needing a round-trip). |
84779 | 2017-02-01 18:54 | 2017-02-06 7:29 | MySQL Server: Replication | Verified (2608 days) | S4 | 5.7 | Any | Any | Expose binlog file and position of last transaction. |
Showing 1-30 of 131 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |