| « Show Previous 30 Entries | Showing 61-90 of 233 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 42207 | 2009-01-20 7:51 | 2009-01-20 11:12 | MySQL Server: Replication | Not a Bug (5574 days) | S1 | 5.1.29 | Linux (CentOS 4.6) | Any | insert into error |
| 55807 | 2010-08-06 18:14 | 2010-08-17 18:23 | MySQL Server: Replication | Not a Bug (5000 days) | S1 | 4.1.22, 5.1.40 | Windows | Any | Last_IO_Errno: 1236 and mysqlbinlog unable to read log with --start-position=N |
| 40510 | 2008-11-04 18:44 | 2008-12-10 16:57 | MySQL Server: Replication | Not a Bug (5615 days) | S2 | 5.0, 5.1, 6.0 | Any | Any | LOAD DATA INFILE statement may span multiple binlogs |
| 108104 | 2022-08-10 3:06 | 2022-08-10 12:39 | MySQL Server: Replication | Not a Bug (624 days) | S5 | MySQL5.7.26 | Any | Any | LOCK_status affect transaction performance when do a "show status" command |
| 47634 | 2009-09-24 19:49 | 2009-09-25 3:33 | MySQL Server: Replication | Not a Bug (5326 days) | S5 | 5.1.39 | Linux (CentOS 5.3) | Any | log-bin does not support explicit path anymore |
| 10830 | 2005-05-24 15:22 | 2005-05-26 13:22 | MySQL Server: Replication | Not a Bug (6909 days) | S3 | 4.1.12-standard-log | Linux (Linux i686) | Any | Lost of binlog-record during update from not pointed at binlog-do-db database |
| 45150 | 2009-05-28 8:09 | 2009-08-20 7:43 | MySQL Server: Replication | Not a Bug (5362 days) | S3 | all (?) | Any | Any | LOST_EVENTS not documented |
| 66260 | 2012-08-08 13:03 | 2013-05-14 19:12 | MySQL Server: Replication | Not a Bug (3999 days) | S2 | 5.5.27 | Linux (Ubuntu 12.04) | Any | Massive data loss when changing master_port in a master/master setup |
| 16682 | 2006-01-20 18:46 | 2006-01-23 21:49 | MySQL Server: Replication | Not a Bug (6667 days) | S2 | 5.0.17a-cert | Windows (Win2003) | Any | Master and slave are not in sync state after execution of rpl_sys test on Win |
| 31309 | 2007-10-01 8:36 | 2008-01-15 10:36 | MySQL Server: Replication | Not a Bug (5945 days) | S1 | 5.0.45 | Linux (Debian Etch 2.6.22-2-amd64) | Any | Master binary log for replication fails with event too small message |
| 4865 | 2004-08-03 10:24 | 2004-08-04 4:47 | MySQL Server: Replication | Not a Bug (7204 days) | S2 | 4.0.20 | Linux (Redhat Linux SE 3) | Any | Master Updates not Executing |
| 77020 | 2015-05-13 9:55 | 2019-04-11 19:40 | MySQL Server: Replication | Not a Bug (1841 days) | S3 | >= 5.5 | Any | Any | MASTER_CONNECT_RETRY should be a global variable |
| 72035 | 2014-03-13 20:19 | 2014-03-17 19:01 | MySQL Server: Replication | Not a Bug (3692 days) | S3 | MySQL 5.5.35 -and- 5.5.24 | Any | Any | MASTER_LOG_POS changes |
| 52185 | 2010-03-18 15:40 | 2010-03-29 6:33 | MySQL Server: Replication | Not a Bug (5141 days) | S2 | 5.1.44 | Linux | Any | master-master-slave replication recovery |
| 35737 | 2008-04-01 10:32 | 2008-05-15 13:47 | MySQL Server: Replication | Not a Bug (5824 days) | S1 | 5.0.45, for pc-linux-gnu (i686) | Linux (RHEL 5.5) | Any | master.info gets corrupted at the time of sude reboot |
| 50581 | 2010-01-25 9:10 | 2010-09-12 6:29 | MySQL Server: Replication | Not a Bug (4974 days) | S2 | 5.0.84 | Any | Any | max_allowed_packet is exceeded on slave with same settings than master |
| 68070 | 2013-01-11 3:01 | 2014-02-03 10:41 | MySQL Server: Replication | Not a Bug (3748 days) | S2 | 5.6.9 | Any | Any | Maybe there existed memory leak in code |
| 74204 | 2014-10-03 7:38 | 2014-10-03 9:14 | MySQL Server: Replication | Not a Bug (3492 days) | S1 | 5.6.21 | FreeBSD (9.3-amd64) | Any | Missing / duplicated records after master crash |
| 88019 | 2017-10-07 8:03 | 2017-10-09 21:29 | MySQL Server: Replication | Not a Bug (2390 days) | S1 | 5.7.19 | Windows | Any | multi source replication Adding Multiple Databases to replication,binlog |
| 72982 | 2014-06-12 8:05 | 2014-06-12 10:23 | MySQL Server: Replication | Not a Bug (3605 days) | S1 | 5.7.4 | Linux (ubutu12.04) | Any | Multi-source replication with MySQL 5.7.4 |
| 32913 | 2007-12-02 20:23 | 2008-08-18 7:32 | MySQL Server: Replication | Not a Bug (5729 days) | S2 | 5.0.45 | Linux | Any | Multiple errors on a slave |
| 2930 | 2004-02-23 17:34 | 2004-02-26 15:10 | MySQL Server: Replication | Not a Bug (7364 days) | S2 | 4.0.18 | Linux (Linux x86) | Any | multitable update does not replicate |
| 79272 | 2015-11-13 14:08 | 2016-10-17 14:59 | MySQL Server: Replication | Not a Bug (3086 days) | S2 | Linux | Any | MySQl 5.5 master fails to replicate to MySQL 5.7.9 | |
| 91940 | 2018-08-09 2:31 | 2018-08-16 12:27 | MySQL Server: Replication | Not a Bug (2079 days) | S3 | 5.7.17 | CentOS (Linux 3.10.0-229.el7.x86_64) | Any | MySQL 5.7.17 abnormal crash |
| 1706 | 2003-10-29 20:14 | 2003-10-30 9:39 | MySQL Server: Replication | Not a Bug (7483 days) | S3 | 4.0.16 | Windows (XP to Solaris) | Any | MySQL and mysqldump mis-handle mixed case table names |
| 44129 | 2009-04-07 9:31 | 2009-04-07 10:19 | MySQL Server: Replication | Not a Bug (5497 days) | S2 | 5.1.33 | Linux (Red Hat Enterprise Linux Server release 5.2 (Tikanga)) | Any | MySQL don't write query in binlog |
| 59832 | 2011-01-31 7:58 | 2011-01-31 8:22 | MySQL Server: Replication | Not a Bug (4833 days) | S5 | uduntu | Any | Any | mysql error |
| 69324 | 2013-05-27 8:46 | 2014-07-21 19:43 | MySQL Server: Replication | Not a Bug (3566 days) | S3 | 5.5.22 | Linux | Any | mysql issues delete statement in log for memory table when executing query |
| 112727 | 2023-10-15 4:17 | 2023-10-19 14:46 | MySQL Server: Replication | Not a Bug (189 days) | S3 | MySQL8.0.22, 8.0.23 | Any | Any | MySQL may couldn't solve the error when flush thread caches to binary logs |
| 108834 | 2022-10-20 11:05 | 2022-11-04 14:14 | MySQL Server: Replication | Not a Bug (538 days) | S3 | all version | Any | Any | MySQL Online DDL add AUTO_INCREMENT |
| « Show Previous 30 Entries | Showing 61-90 of 233 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
