Showing 1-30 of 526 (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 (7913 days) | S3 | 3.23 and 4.x | Any | A query using both auto_increment and LAST_INSERT_ID() breaks binlog | |
52 | 2003-01-31 22:53 | 2003-03-06 8:49 | MySQL Server: Replication | Closed (7876 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 (7827 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 (7879 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 (7879 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 (7865 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 (7871 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 (7879 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 (7890 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 (5844 days) | S3 | 5.0 | Any (all) | Any | Some SET commands should be written to the binlog as they affect next updates |
90 | 2003-02-21 15:59 | 2019-04-05 13:29 | MySQL Server: Command-line Clients | Closed (7870 days) | S3 | 4.1 | Any (at least Linux) | Any | In 4.0 the mysql client prints "Unknown database ¬(;Ðpöÿ¿(öÿ¿h_@'" at connect |
95 | 2003-02-24 13:44 | 2003-03-03 5:58 | MySQL Server | Closed (7879 days) | S3 | 4.0.11 | Any (all) | Any | DROP TABLE returns wrong error when the database does not exist |
104 | 2003-02-26 13:33 | 2003-03-06 14:03 | MySQL Server | Closed (7876 days) | S3 | 4.0 | Any (all) | Any | INSERT DELAYED does not care about SQL_LOG_BIN=0 |
136 | 2003-03-09 15:55 | 2003-03-11 16:26 | MySQL Server: Replication | Closed (7871 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 (7863 days) | S3 | 3.23, 4.0 | Any (all) | Any | mysqldump --first-slave or --master-data silently purges master's binlogs |
169 | 2003-03-19 14:22 | 2003-03-24 13:38 | MySQL Server | Closed (7858 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 |
174 | 2003-03-21 6:35 | 2003-03-21 12:27 | MySQL Server | Closed (7861 days) | S2 | 4.1 | Any (all) | Any | SHOW BINLOG EVENTS crashes (SEGV) the server if it is the first command |
177 | 2003-03-21 13:09 | 2003-05-13 14:17 | MySQL Server: Replication | Closed (7808 days) | S3 | 4.0 | Any (all) | Any | CONNECTION_ID() is badly replicated |
178 | 2003-03-21 13:12 | 2020-09-13 20:45 | MySQL Server: Replication | Duplicate (7739 days) | S3 | 4.0 | Any (all) | Any | USER() is badly replicated (is replicated to "") |
180 | 2003-03-21 14:58 | 2003-04-08 9:50 | MySQL Server: Replication | Closed (7843 days) | S3 | 4.0 | Any (all) | Any | GRANT/REVOKE is replicated even if --replicate-wild-ignore-table=mysql.% |
186 | 2003-03-24 5:54 | 2003-03-25 8:09 | MySQL Server: Replication | Closed (7857 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 (7833 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 (7769 days) | S3 | 3.23, 4.0 | Any (all) | Any | Replication between a 4.0.12 master and 3.23.52 slave does not work |
218 | 2003-04-01 8:09 | 2003-04-09 14:29 | MySQL Server | Closed (7842 days) | S3 | 3.23, 4.0 | Any (all) | Any | LOAD DATA INFILE IGNORE is well logged, but read as LOAD DATA INFILE REPLACE |
221 | 2003-04-02 2:10 | 2011-02-16 23:40 | MySQL Server: Replication | Won't fix (5666 days) | S3 | 4.0, 4.1, 5.1 | Any (all) | Any | LOAD_FILE is not replicated |
222 | 2003-04-02 5:11 | 2003-04-03 1:39 | MySQL Server: Replication | Closed (7848 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 (7784 days) | S2 | Any (all) | Any | 3.23 master, 4.0 slave. Slave loss temp tables everytime FLUSH LOGS on master | |
258 | 2003-04-09 5:23 | 2003-04-09 5:24 | MySQL Server: Replication | Not a Bug (7842 days) | S3 | Any | This is a test, I'm sure I assigned #254 to me while creating so why is it open | ||
311 | 2003-04-21 15:04 | 2019-05-14 14:22 | MySQL Server | Closed (7829 days) | S3 | 4.0 | Linux (linux) | Any | When selecting an unknow system variable, one can get Packets out of order |
315 | 2003-04-23 5:47 | 2003-04-26 5:15 | MySQL Server: Command-line Clients | Closed (7825 days) | S3 | 4.1 | Linux (linux at least) | Any | Ctrl-U/Ctrl-R/Home/End/PgUp/PgDn are broken in 'mysql' client |
Showing 1-30 of 526 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |