| « Show Previous 30 Entries | Showing 31-60 of 131 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 85977 | 2017-04-18 2:02 | 2018-11-02 15:03 | MySQL Server: Documentation | Verified (2564 days) | S3 | 5.7 and 8.0 | Any | Any | The doc. of slave-parallel-type=LOGICAL_CLOCK wrongly reference Group Commit. |
| 86060 | 2017-04-24 21:35 | 2018-02-12 7:41 | MySQL Server: Replication | Verified (2264 days) | S4 | 8.0.1 | Any | Any | Expose counters for monitoring Write Set barriers. |
| 86063 | 2017-04-24 21:59 | 2017-09-22 13:52 | MySQL Server: Replication | Closed (2407 days) | S2 | 8.0.1 | Any | Any | The function reset_connection does not reset Write Set in WRITESET_SESSION. |
| 86078 | 2017-04-25 19:14 | 2018-04-12 7:51 | MySQL Server: Replication | Closed (2205 days) | S2 | 8.0.1 | Any | Any | Bad Write Set tracking with UNIQUE KEY on a DELETE followed by an INSERT. |
| 86079 | 2017-04-25 19:28 | 2018-02-27 17:32 | MySQL Server: Replication | Closed (2249 days) | S2 | 8.0.1 | Any | Any | Deadlock with slave_preserve_commit_order=ON with Bug#86078. |
| 86926 | 2017-07-04 11:24 | 2018-06-29 11:49 | MySQL Server: Partitions | Closed (2127 days) | S2 | 5.7.17-log | Any | Any | The field table_name (varchar(64)) from mysql.innodb_table_stats can overflow. |
| 86927 | 2017-07-04 11:46 | 2017-10-10 13:46 | MySQL Server: InnoDB storage engine | Closed (2389 days) | S3 | 5.7.17-log | Any | Any | Renaming a partitioned table does not update mysql.innodb_table_stats. |
| 88673 | 2017-11-28 6:11 | 2017-11-28 9:46 | MySQL Server: InnoDB storage engine | Verified (2340 days) | S3 | 5.7.20 | Any | Any | Regression CREATE TBL from 5.7.17 to 20 (part #1: innodb_file_per_table = ON). |
| 88674 | 2017-11-28 6:17 | 2017-11-28 9:37 | MySQL Server: InnoDB storage engine | Verified (2340 days) | S3 | 5.7.20 | Any | Any | Regression CREATE TBL from 5.7.17 to 20 (part #2: innodb_file_per_table = OFF). |
| 89141 | 2018-01-08 22:07 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2206 days) | S2 | 5.7.20,8.0.3 | Any | Any | Error in Group Replication caused by bad Write Set tracking. |
| 89142 | 2018-01-08 22:09 | 2019-04-30 15:41 | MySQL Server: Group Replication | Closed (1822 days) | S4 | 5.7.20, 8.0.3 | Any | Any | Make FLUSH RELAY LOGS work for Group Replication. |
| 89143 | 2018-01-08 22:10 | 2018-07-02 14:06 | MySQL Server: Replication | Closed (2191 days) | S2 | 5.7.20 | Any | Any | Commit order deadlock + retry logic is not considering trx error cases |
| 89145 | 2018-01-08 22:15 | 2018-01-11 9:47 | MySQL Server: Group Replication | Verified (2296 days) | S4 | 5.7.20,8.0.3 | Any | Any | Provide relay log details in case of Group Replication applier failure. |
| 89146 | 2018-01-08 22:16 | 2018-06-20 16:45 | MySQL Server: Group Replication | Closed (2136 days) | S3 | 5.7.20, 8.0.3 | Any | Any | Binlog name and Pos are wrong in group_replication_applier channel's error msgs |
| 89147 | 2018-01-08 22:18 | 2018-01-11 9:52 | MySQL Server: Group Replication | Verified (2296 days) | S4 | 5.7.20,8.0.3 | Any | Any | The field end_log_pos in Group Replication error messages is ambiguous. |
| 89148 | 2018-01-08 22:23 | 2019-06-04 1:24 | MySQL Server: Group Replication | Verified (2264 days) | S4 | 5.7.20 and 8.0.3 | Any | Any | The timestamp of the GITD events in the GR relay log look wrong. |
| 89194 | 2018-01-11 19:14 | 2018-04-11 16:23 | MySQL Server: Group Replication | Duplicate (2206 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Wrong certification lead to data inconsistency and GR breakage. |
| 89195 | 2018-01-11 19:15 | 2019-07-25 14:45 | MySQL Server: Group Replication | Closed (1736 days) | S2 | 5.7.20, 8.0.3 | Any | Any | Total ordering of transactions is not respected in Group Replication. |
| 89196 | 2018-01-11 19:16 | 2018-01-19 9:50 | MySQL Server: Replication | Verified (2288 days) | S4 | 5.7.20, 8.0.3 | Any | Any | Please add GTID in applier error messages. |
| 89197 | 2018-01-11 19:16 | 2018-01-15 13:42 | MySQL Server: Replication | Verified (2292 days) | S3 | 5.7.20, 8.0.3 | Any | Any | When GR fails, the error message says to "START SLAVE". |
| 89247 | 2018-01-15 14:39 | 2021-09-01 13:10 | MySQL Server: Replication | Duplicate (967 days) | S2 | 8.0.3, 5.7.20 | Any | Any | Deadlock with MTS when slave_preserve_commit_order = ON. |
| 91737 | 2018-07-20 11:40 | 2018-07-24 13:35 | MySQL Server: Replication | Verified (2102 days) | S4 | 5.7.22 | Any | Any | Please log GTID_EXECUTED when running RESET MASTER. |
| 91741 | 2018-07-20 14:06 | 2018-07-24 20:32 | MySQL Server: Replication | Verified (2102 days) | S4 | 5.7.22 | Any | Any | Improve Start binlog_dump log on master. |
| 91744 | 2018-07-20 15:27 | 2021-07-12 13:23 | MySQL Server: Replication | Verified (2038 days) | S2 | 5.7.22, 5.7.23 | Any | Any | START SLAVE UNTIL going further than it should. |
| 91766 | 2018-07-23 14:59 | 2018-07-24 13:24 | MySQL Server: Replication | Verified (2102 days) | S2 | 5.7.22 | Any | Any | Log of replication position when running CHANGE MASTER TO is wrong. |
| 92012 | 2018-08-14 14:47 | 2018-08-15 21:59 | MySQL Server: Documentation | Closed (2080 days) | S3 | 8.0, 5.7, 5.6 | Any | Any | Wrong default for thread_cache_size in "How MySQL Uses Threads for Client Cnx". |
| 92024 | 2018-08-15 17:48 | 2018-11-02 17:53 | MySQL Server: Connection Handling | Closed (2001 days) | S3 | 5.7.23, 8.0.12, 5.6.41 | Any | Any | Setting thread_cache_size to 0 does not empty the Thread Cache. |
| 92064 | 2018-08-18 18:39 | 2018-08-31 12:09 | MySQL Server: Documentation | Closed (2064 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | Information for the recovery of the IO thread is NOT in mysql.slave_master_info. |
| 92093 | 2018-08-20 21:24 | 2019-09-04 15:15 | MySQL Server: Documentation | Closed (1695 days) | S2 | 5.7.23 | Any | Any | Replication crash safety needs relay_log_recovery even with GTID. |
| 92109 | 2018-08-21 17:53 | 2021-06-15 7:48 | MySQL Server: Replication | Verified (1084 days) | S2 | 5.7, 8.0 | Any | Any | Please make replication crash safe with GITD and less durable setting (bis). |
| « Show Previous 30 Entries | Showing 31-60 of 131 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
