Showing 1-30 of 328 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
36 | 2003-01-24 0:25 | 2003-01-28 16:49 | MySQL Server | Closed (7730 days) | S3 | 3.23 and 4.x | Any | A query using both auto_increment and LAST_INSERT_ID() breaks binlog | |
86 | 2003-02-20 13:17 | 2003-02-20 13:31 | MySQL Server: Replication | Closed (7707 days) | S3 | 3.23, 4.0 | Any (all) | Any | LOAD DATA INFILE is not replicated by slave if replicate_*_table is set |
102 | 2003-02-26 6:48 | 2003-02-28 2:30 | MySQL Server: Replication | Closed (7699 days) | S2 | 4.1.0 | Linux (Linux/alpha) | Any | Test failure in test "rpl000015" |
82 | 2003-02-18 14:07 | 2003-03-03 5:52 | MySQL Server: Replication | Closed (7696 days) | S2 | 4.0 | Any (all) | Any | LOAD DATA *LOCAL* INFILE is not properly written to the binary log |
69 | 2003-02-13 8:22 | 2003-03-03 6:45 | MySQL Server: Replication | Closed (7696 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 (7696 days) | S3 | 4.0 | Any (all) | Any | On 4.0.10, RESET SLAVE fails to reset the master's binlog coordinates |
52 | 2003-01-31 22:53 | 2003-03-06 8:49 | MySQL Server: Replication | Closed (7693 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 |
80 | 2003-02-17 9:51 | 2003-03-11 5:54 | MySQL Server: Replication | Closed (7688 days) | S3 | 4.0 | Any (all) | Any | Obscure error message in replication (Error updating slave list: Query error) |
136 | 2003-03-09 15:55 | 2003-03-11 16:26 | MySQL Server: Replication | Closed (7688 days) | S2 | 4.0 | Linux (Linux at least) | Any | INSERT SELECT does not write the same num of rows on master and slave |
79 | 2003-02-16 10:44 | 2003-03-17 14:08 | MySQL Server: Replication | Closed (7682 days) | S3 | 4.0 | Any (all) | Any | relay_log_space_limit can cause deadlock if we have a big transaction |
159 | 2003-03-17 7:39 | 2003-03-19 7:13 | MySQL Server: Replication | Closed (7680 days) | S3 | 3.23, 4.0 | Any (all) | Any | mysqldump --first-slave or --master-data silently purges master's binlogs |
174 | 2003-03-21 6:35 | 2003-03-21 12:27 | MySQL Server | Closed (7678 days) | S2 | 4.1 | Any (all) | Any | SHOW BINLOG EVENTS crashes (SEGV) the server if it is the first command |
181 | 2003-03-22 8:28 | 2003-03-22 13:43 | MySQL Server: Replication | Closed (7677 days) | S1 | 4.0.12 | FreeBSD (Freebsd 4.5/4.7) | Any | Error replicating LOAD DATA INFILE in 4.0.12 |
169 | 2003-03-19 14:22 | 2003-03-24 13:38 | MySQL Server | Closed (7675 days) | S2 | 3.23.56 and below (not in 4.0) | Any (all) | Any | DELETE FROM t; does not lock 't' enough, causes bad order in binlog |
186 | 2003-03-24 5:54 | 2003-03-25 8:09 | MySQL Server: Replication | Closed (7674 days) | S3 | 4.0 | Any (all) | Any | If a connection has temporary tables and does RESET MASTER, this breaks replic. |
180 | 2003-03-21 14:58 | 2003-04-08 9:50 | MySQL Server: Replication | Closed (7660 days) | S3 | 4.0 | Any (all) | Any | GRANT/REVOKE is replicated even if --replicate-wild-ignore-table=mysql.% |
218 | 2003-04-01 8:09 | 2003-04-09 14:29 | MySQL Server | Closed (7659 days) | S3 | 3.23, 4.0 | Any (all) | Any | LOAD DATA INFILE IGNORE is well logged, but read as LOAD DATA INFILE REPLACE |
191 | 2003-03-25 14:24 | 2003-04-18 13:56 | MySQL Server: Replication | Closed (7650 days) | S3 | 3.23 | Linux (Linux at least) | Any | Many connections from the slave to the master cause "alarm queue is full" |
53 | 2003-01-31 22:56 | 2003-04-24 14:02 | MySQL Server: Replication | Closed (7644 days) | S3 | 4.0, 4.1.0 | Any (all) | Any | In some cases, the slave deletes relay logs while he still may need them |
177 | 2003-03-21 13:09 | 2003-05-13 14:17 | MySQL Server: Replication | Closed (7625 days) | S3 | 4.0 | Any (all) | Any | CONNECTION_ID() is badly replicated |
344 | 2003-04-29 7:42 | 2003-05-13 14:17 | MySQL Server: Replication | Closed (7625 days) | S3 | 4.1 | Any (all) | Any | New password function in 4.1 has randomness => does not replicate well |
468 | 2003-05-21 1:48 | 2003-05-23 7:44 | MySQL Server | Closed (7615 days) | S3 | 3.23.57 | Any (any) | Any | SHOW VARIABLES trims innodb_data_file_path |
576 | 2003-06-03 13:25 | 2003-06-03 14:16 | MySQL Server: Replication | Closed (7604 days) | S3 | 4.0 | Any (all) | Any | slave compiled with --debug dies (DBUG_ASSERT) with CHANGE MASTER |
578 | 2003-06-03 19:21 | 2003-06-05 6:49 | MySQL Server | Closed (7602 days) | S2 | mysqld Ver 4.0.12 | Linux (Linux) | Any | mysqlimport -l silently fails when binlog-ignore-db is set |
254 | 2003-04-08 15:04 | 2003-06-06 7:52 | MySQL Server: Replication | Closed (7601 days) | S2 | Any (all) | Any | 3.23 master, 4.0 slave. Slave loss temp tables everytime FLUSH LOGS on master | |
651 | 2003-06-13 8:03 | 2003-06-14 7:44 | MySQL Server: Replication | Closed (7593 days) | S3 | 4.0 | Any (all) | Any | If MASTER_POS_WAIT() is waiting, it does not stop if someone does STOP SLAVE |
691 | 2003-06-20 6:47 | 2003-06-20 7:00 | MySQL Server: Replication | Closed (7587 days) | S3 | 4.0 | Any (all) | Any | mysqlbinlog from 4.0 can't read a binlog produced by a 3.23 mysqld |
198 | 2003-03-27 6:31 | 2003-06-21 7:31 | MySQL Server: Replication | Closed (7586 days) | S3 | 3.23, 4.0 | Any (all) | Any | Replication between a 4.0.12 master and 3.23.52 slave does not work |
491 | 2003-05-24 7:40 | 2003-07-01 5:38 | MySQL Server: Replication | Closed (7576 days) | S3 | 4.0.13 | Any (all) | Any | If INSERT SELECT fails in a MyISAM table but has changed row, nothing in binlog |
490 | 2003-05-24 7:09 | 2003-07-01 6:14 | MySQL Server: Replication | Closed (7576 days) | S2 | 4.0.13 | Any (all) | Any | Accidental introduction of a bug with auto_increment and INSERT SELECT |
Showing 1-30 of 328 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |