| Showing 1-30 of 50 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 106493 | 2022-02-17 14:38 | 2022-04-11 12:28 | MySQL Server: Replication | Verified (355 days) | S3 | 8.0.28, 5.7.37 | Any | Any | Replication crash when updating a table with a stored generated field in the pri |
| 106536 | 2022-02-22 8:30 | 2022-02-23 20:21 | MySQL Server: Replication | Duplicate (350 days) | S2 | 8.0.25 | Any (rhel-7.4) | Any (x86-64) | io_thread of slave db reports error when a big trx in binlog needs to be skipped |
| 106671 | 2022-03-08 12:12 | 2022-03-11 8:00 | MySQL Server: Replication | Verified (334 days) | S3 | 5.7.35, 5.7.37 | Any | Any | Contribution by Tencent: mark insert select with autoinc column unsafe |
| 106727 | 2022-03-15 2:22 | 2022-03-15 13:47 | MySQL Server: Replication | Verified (330 days) | S3 | 8.0.28, 5.7.37 | Any | Any | Report ERROR when logging big binlog events |
| 106818 | 2022-03-24 11:23 | 2022-06-07 2:29 | MySQL Server: Replication | Verified (246 days) | S2 | 5.7,8.0, 5.7.37 | Any | Any | Replication may fail when XA transactions use replace into statements |
| 106845 | 2022-03-26 13:23 | 2022-04-06 1:46 | MySQL Server: Replication | Verified (308 days) | S2 | 8.0.25 | CentOS (7.6) | ARM | Parallel replication not working with slave_preserve_commit_order=1 |
| 106875 | 2022-03-30 14:43 | 2022-04-05 14:13 | MySQL Server: Replication | Verified (309 days) | S3 | 8.0.28 | Any | Any | Contribution by Tencent: writeset can not be used when binlog_format is mixed |
| 106942 | 2022-04-07 10:44 | 2022-04-19 9:40 | MySQL Server: Replication | Not a Bug (295 days) | S3 | 8.0.28 | Any | Any | alter user may lead replication broken with error 1396 |
| 106970 | 2022-04-08 16:55 | 2022-04-21 0:16 | MySQL Server: Replication | Verified (299 days) | S3 | 8.0.21 | Linux | x86 | Replicate_Wild_Do_Table don't take effect |
| 106999 | 2022-04-13 8:44 | 2022-04-14 12:02 | MySQL Server: Replication | Can't repeat (300 days) | S2 | 5.7.37 | Any | Any | contributed by Tencent: shutdown hang due to binlog dump stick at wait_new_event |
| 107008 | 2022-04-13 11:44 | 2022-05-05 7:11 | MySQL Server: Replication | Verified (279 days) | S2 | 5.7.37 | Any | Any | Contribution by Tencent:Shutdown hang due to work thread wait for ack |
| 107113 | 2022-04-24 10:53 | 2022-04-26 4:17 | MySQL Server: Replication | Verified (290 days) | S3 | 5.7,8.0, 8.0.28 | Any | Any | Got fatal error 1236 from master when reading data from binary log |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (263 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 107366 | 2022-05-23 1:53 | 2023-01-03 13:10 | MySQL Server: Replication | Closed (36 days) | S2 | 8.0.18 and prior, 8.0.29 | Any | Any | Contribution by Tencent: Invalid JSON value, Error_code: 3903 |
| 107371 | 2022-05-23 11:12 | 2022-05-23 12:29 | MySQL Server: Replication | Verified (261 days) | S3 | Ver 8.0, 5.7 | Any | Any | slave error: Slave I/O for channel '': Unexpected master's heartbeat data |
| 107438 | 2022-05-31 19:57 | 2022-06-07 9:38 | MySQL Server: Replication | Verified (252 days) | S2 | 5.7.38 | CentOS (8) | Any | JSON STORED generated column values are inserted as NULL on replica |
| 107574 | 2022-06-15 21:07 | 2022-12-28 16:00 | MySQL Server: Replication | Closed (42 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 (225 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 (176 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 (202 days) | S2 | 8.0 | Any | Any | MySQL 8.0 Replication breaks when tmpdir space is filled |
| 107996 | 2022-07-27 6:38 | 2022-07-27 7:45 | MySQL Server: Replication | Verified (196 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 (188 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 (182 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 (128 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 (154 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 (67 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 (145 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 (145 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 (142 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 (125 days) | S2 | 5.7.39 | Any | Any | Read-Committed Isolation, UPDATES wrapped in DROP TEMPORARY TABLE IF EXISTS |
| Showing 1-30 of 50 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
