Showing 1–30 of 1255
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 52 | 2003-01-31 22:53 | 2003-03-06 8:49 | MySQL Server: Replication | Closed (8650 days) | S3 | 4.0, 4.1 | Any (all) | Any | 4.0 If only transactions are run on the master then the slave shows wrong info |
| 53 | 2003-01-31 22:56 | 2003-04-24 14:02 | MySQL Server: Replication | Closed (8601 days) | S3 | 4.0, 4.1.0 | Any (all) | Any | In some cases, the slave deletes relay logs while he still may need them |
| 69 | 2003-02-13 8:22 | 2003-03-03 6:45 | MySQL Server: Replication | Closed (8653 days) | S3 | 4.0 | Windows (Windows) | Any | 4.0.9 Windows slave hangs on STOP SLAVE |
| 70 | 2003-02-13 8:25 | 2003-03-03 6:49 | MySQL Server: Replication | Closed (8653 days) | S3 | 4.0 | Any (all) | Any | On 4.0.10, RESET SLAVE fails to reset the master's binlog coordinates |
| 79 | 2003-02-16 10:44 | 2003-03-17 14:08 | MySQL Server: Replication | Closed (8639 days) | S3 | 4.0 | Any (all) | Any | relay_log_space_limit can cause deadlock if we have a big transaction |
| 80 | 2003-02-17 9:51 | 2003-03-11 5:54 | MySQL Server: Replication | Closed (8645 days) | S3 | 4.0 | Any (all) | Any | Obscure error message in replication (Error updating slave list: Query error) |
| 82 | 2003-02-18 14:07 | 2003-03-03 5:52 | MySQL Server: Replication | Closed (8653 days) | S2 | 4.0 | Any (all) | Any | LOAD DATA *LOCAL* INFILE is not properly written to the binary log |
| 86 | 2003-02-20 13:17 | 2003-02-20 13:31 | MySQL Server: Replication | Closed (8664 days) | S3 | 3.23, 4.0 | Any (all) | Any | LOAD DATA INFILE is not replicated by slave if replicate_*_table is set |
| 88 | 2003-02-21 6:41 | 2008-09-27 8:44 | MySQL Server: Replication | Closed (6618 days) | S3 | 5.0 | Any (all) | Any | Some SET commands should be written to the binlog as they affect next updates |
| 102 | 2003-02-26 6:48 | 2003-02-28 2:30 | MySQL Server: Replication | Closed (8656 days) | S2 | 4.1.0 | Linux (Linux/alpha) | Any | Test failure in test "rpl000015" |
| 136 | 2003-03-09 15:55 | 2003-03-11 16:26 | MySQL Server: Replication | Closed (8645 days) | S2 | 4.0 | Linux (Linux at least) | Any | INSERT SELECT does not write the same num of rows on master and slave |
| 159 | 2003-03-17 7:39 | 2003-03-19 7:13 | MySQL Server: Replication | Closed (8637 days) | S3 | 3.23, 4.0 | Any (all) | Any | mysqldump --first-slave or --master-data silently purges master's binlogs |
| 175 | 2003-03-21 8:29 | 2003-05-16 14:43 | MySQL Server: Replication | Closed (8579 days) | S2 | 4.0.12-standard-log | Linux (Linux 2.4.18-686-smp) | Any | RENAME TABLE breaks on replication slave when involved in a MERGE table |
| 177 | 2003-03-21 13:09 | 2003-05-13 14:17 | MySQL Server: Replication | Closed (8582 days) | S3 | 4.0 | Any (all) | Any | CONNECTION_ID() is badly replicated |
| 180 | 2003-03-21 14:58 | 2003-04-08 9:50 | MySQL Server: Replication | Closed (8617 days) | S3 | 4.0 | Any (all) | Any | GRANT/REVOKE is replicated even if --replicate-wild-ignore-table=mysql.% |
| 181 | 2003-03-22 8:28 | 2003-03-22 13:43 | MySQL Server: Replication | Closed (8634 days) | S1 | 4.0.12 | FreeBSD (Freebsd 4.5/4.7) | Any | Error replicating LOAD DATA INFILE in 4.0.12 |
| 183 | 2003-03-23 8:36 | 2003-04-03 1:38 | MySQL Server: Replication | Closed (8622 days) | S1 | 4.0.12 | FreeBSD (FreeBSD 4.5/4.7) | Any | Replication of temporary tables not working |
| 186 | 2003-03-24 5:54 | 2003-03-25 8:09 | MySQL Server: Replication | Closed (8631 days) | S3 | 4.0 | Any (all) | Any | If a connection has temporary tables and does RESET MASTER, this breaks replic. |
| 191 | 2003-03-25 14:24 | 2003-04-18 13:56 | MySQL Server: Replication | Closed (8607 days) | S3 | 3.23 | Linux (Linux at least) | Any | Many connections from the slave to the master cause "alarm queue is full" |
| 198 | 2003-03-27 6:31 | 2003-06-21 7:31 | MySQL Server: Replication | Closed (8543 days) | S3 | 3.23, 4.0 | Any (all) | Any | Replication between a 4.0.12 master and 3.23.52 slave does not work |
| 222 | 2003-04-02 5:11 | 2003-04-03 1:39 | MySQL Server: Replication | Closed (8622 days) | S3 | 4.0 | Any (all) | Any | Options of LOAD DATA lost in replication (FIELDS TERMINATED BY etc) |
| 254 | 2003-04-08 15:04 | 2003-06-06 7:52 | MySQL Server: Replication | Closed (8558 days) | S2 | Any (all) | Any | 3.23 master, 4.0 slave. Slave loss temp tables everytime FLUSH LOGS on master | |
| 269 | 2003-04-10 8:51 | 2003-04-10 14:27 | MySQL Server: Replication | Closed (8615 days) | S3 | 3.23.52 | Linux (Linux/Suse) | Any | Replication fails on interrupted temporary table processes |
| 319 | 2003-04-23 14:32 | 2011-02-16 23:40 | MySQL Server: Replication | Closed (6397 days) | S3 | 4.0, 4.1, 5.1 | Any (all) | Any | if while a non-transactional slave is replicating a transaction, possiblproblem |
| 328 | 2003-04-26 6:31 | 2003-04-26 6:31 | MySQL Server: Replication | Closed (8599 days) | S3 | 4.0 | Any (all) | Any | Replication stops if on the master we got "table is full" doing LOAD DATA inodb |
| 329 | 2003-04-26 6:35 | 2003-04-26 6:36 | MySQL Server: Replication | Closed (8599 days) | S3 | 4.0 | Any (all) | Any | 'Event too big' when using a small max_binlog_size |
| 330 | 2003-04-26 6:41 | 2003-04-26 6:42 | MySQL Server: Replication | Closed (8599 days) | S3 | 4.0 | Any (all) | Any | If STOP SLAVE while slave is executing a transaction, position lost |
| 331 | 2003-04-26 6:45 | 2003-04-26 6:46 | MySQL Server: Replication | Closed (8599 days) | S3 | 4.0 | Any (all) | Any | Bad replication of a LOAD DATA iNFILE that loaded NULL in auto_inc columns |
| 343 | 2003-04-29 7:24 | 2003-11-05 14:46 | MySQL Server: Replication | Closed (8406 days) | S3 | 4.0 | Any (all) | Any | mysqld never uses the REPLICATION CLIENT privilege |
| 344 | 2003-04-29 7:42 | 2003-05-13 14:17 | MySQL Server: Replication | Closed (8582 days) | S3 | 4.1 | Any (all) | Any | New password function in 4.1 has randomness => does not replicate well |
Showing 1–30 of 1255
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.