| Showing 1-30 of 50 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 107574 | 2022-06-15 21:07 | 2022-12-28 16:00 | MySQL Server: Replication | Closed (163 days) | S2 | 5.7.38, 5.7.40 | Any | Any | MTR deadlocks when preserving commit order and changing read_only. |
| 107677 | 2022-06-28 7:41 | 2022-06-28 8:18 | MySQL Server: Replication | Verified (346 days) | S2 | 8.0.29, 5.7.38 | Any | Any | Contribution by Tencent: create table like temporary table missing charset info |
| 107884 | 2022-07-14 17:16 | 2022-08-17 1:00 | MySQL Server: Replication | No Feedback (297 days) | S3 | 8.0.29 | Any | Any | Error message after stop semi sync replication |
| 107928 | 2022-07-20 23:09 | 2022-07-26 2:17 | MySQL Server: Replication | Verified (323 days) | S2 | 8.0 | Any | Any | MySQL 8.0 Replication breaks when tmpdir space is filled |
| 107996 | 2022-07-27 6:38 | 2023-02-22 18:29 | MySQL Server: Replication | Closed (107 days) | S3 | 8.0.29 | Any | Any | Contribution by Tencent: wrong default value of geometry column |
| 108061 | 2022-08-03 11:33 | 2022-08-04 2:01 | MySQL Server: Replication | Verified (309 days) | S3 | 5.7.39 | Any | Any | Contribution by Tencent: Generated column calculate error without base column |
| 108104 | 2022-08-10 3:06 | 2022-08-10 12:39 | MySQL Server: Replication | Not a Bug (303 days) | S5 | MySQL5.7.26 | Any | Any | LOCK_status affect transaction performance when do a "show status" command |
| 108234 | 2022-08-23 7:00 | 2022-10-03 12:29 | MySQL Server: Replication | Can't repeat (249 days) | S3 | mysql 8.0.28 | Any | Any | A Document incorrect regarding Replication with Differing Table Definitions |
| 108405 | 2022-09-06 16:22 | 2022-09-07 4:56 | MySQL Server: Replication | Verified (275 days) | S3 | 8.0 | Any | Any | Contribution: Implement logic to be able to get a consistent GTID |
| 108422 | 2022-09-08 8:42 | 2022-12-03 10:50 | MySQL Server: Replication | Closed (188 days) | S3 | 8.0.30 | Any | Any | Old terminology "START SLAVE" is still in Error/Warning messages. |
| 108510 | 2022-09-16 0:31 | 2022-09-16 5:36 | MySQL Server: Replication | Verified (266 days) | S2 | 8.0.21 | Any | Any | Return value of rotate() not get checked |
| 108514 | 2022-09-16 1:10 | 2022-09-16 5:53 | MySQL Server: Replication | Verified (266 days) | S2 | 8.0.21 | Any | Any | Return value of Gtid_set::ensure_sidno(int) not get checked |
| 108537 | 2022-09-19 13:29 | 2022-09-20 15:46 | MySQL Server: Replication | Verified (263 days) | S2 | 5.7 | Any | Any | gtid_subset should reset null_value to false |
| 108682 | 2022-10-04 19:32 | 2022-10-09 12:48 | MySQL Server: Replication | Verified (246 days) | S2 | 5.7.39 | Any | Any | Read-Committed Isolation, UPDATES wrapped in DROP TEMPORARY TABLE IF EXISTS |
| 108760 | 2022-10-13 7:12 | 2022-11-14 1:00 | MySQL Server: Replication | No Feedback (208 days) | S3 | 8.0.16 | CentOS | Any | show slave status hang |
| 108834 | 2022-10-20 11:05 | 2022-11-04 14:14 | MySQL Server: Replication | Not a Bug (217 days) | S3 | all version | Any | Any | MySQL Online DDL add AUTO_INCREMENT |
| 108876 | 2022-10-25 23:00 | 2022-10-27 17:22 | MySQL Server: Replication | Can't repeat (225 days) | S2 | 8.0.28 | CentOS ( 7.9.2009) | x86 | CLONE operation results in mysqld server hang on startup |
| 108892 | 2022-10-27 1:47 | 2022-10-31 3:32 | MySQL Server: Replication | Can't repeat (221 days) | S3 | 8.0.26 | CentOS (CentOS Linux release 7.6.1810) | Any | MGR Sencondary node don`t appling relay logs |
| 108948 | 2022-11-01 7:50 | 2022-11-21 11:16 | MySQL Server: Replication | Unsupported (200 days) | S3 | 5.6 | Windows | Any | Getting mislead error message after successful replication set |
| 109016 | 2022-11-07 11:51 | 2022-11-08 15:57 | MySQL Server: Replication | Verified (213 days) | S3 | 5.7.38 | Any | Any | Slave crashed when master restart |
| 109023 | 2022-11-08 4:24 | 2022-11-08 7:51 | MySQL Server: Replication | Verified (213 days) | S3 | 5.7,8.0.31 | Any | Any | Leak REPL_SLAVE_ACL privilege error is ambiguous |
| 109031 | 2022-11-09 2:47 | 2022-11-30 9:00 | MySQL Server: Replication | Verified (192 days) | S3 | 5.7.38 | Any | Any | 'start slave' reports error after stopping slave during IO thd reconnecting |
| 109154 | 2022-11-21 14:52 | 2023-04-21 8:34 | MySQL Server: Replication | Closed (133 days) | S3 | 8.0 | Any | Any | Contribution: Fix incorrect suggested commands to start slave in error logs ... |
| 109217 | 2022-11-28 9:51 | 2022-12-12 3:19 | MySQL Server: Replication | Verified (179 days) | S2 | 5.7.40 | Any | Any | The datas of master and standby are inconsistent for Spatial Data Formats |
| 109268 | 2022-12-02 6:00 | 2022-12-06 4:45 | MySQL Server: Replication | Verified (185 days) | S3 | 8.0 | Any | Any | binlog file record unused "use `database`" along with actually query |
| 109290 | 2022-12-06 8:28 | 2023-01-13 6:20 | MySQL Server: Replication | Verified (147 days) | S5 | 5.7.39 | Ubuntu | x86 | WRITESET causing performance issue for replication on a replica |
| 109397 | 2022-12-15 15:20 | 2022-12-16 5:47 | MySQL Server: Replication | Verified (175 days) | S3 | 8.0 | Any | Any | Contribution: Fix typo in a comment: timestamps => sequences |
| 109485 | 2022-12-27 0:34 | 2023-04-21 8:37 | MySQL Server: Replication | Closed (135 days) | S2 | 5.7.40 | Any | Any | Contribution by Tencent: Previous_gtids miss gtid when binlog_order_commits off |
| 109530 | 2023-01-04 9:42 | 2023-01-05 11:02 | MySQL Server: Replication | Verified (155 days) | S3 | 8.0.30, 8.0.31 | Any | Any | Fail to write drop temp table binlog event in semi sync mode |
| 109620 | 2023-01-13 10:11 | 2023-01-19 15:19 | MySQL Server: Replication | Duplicate (141 days) | S3 | 5.7.38, 5.7.39, 5.7.40 | Red Hat | Any | Slave_skip_errors not skipping the error 1399 on MySQL 5.7.38,5.7.39,5.7.40 |
| Showing 1-30 of 50 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
