Showing 1-30 of 526 (Edit, Save, CSV, Feed) Show Next 30 Entries »
ID# Date Updated Type Status Sev Version OS CPU Summary
362003-01-24
0:25
2003-01-28
16:49
MySQL ServerClosed
(6880 days)
S33.23 and 4.x AnyA query using both auto_increment and LAST_INSERT_ID() breaks binlog
522003-01-31
22:53
2003-03-06
8:49
MySQL Server: ReplicationClosed
(6843 days)
S34.0, 4.1Any (all)Any4.0 If only transactions are run on the master then the slave shows wrong info
532003-01-31
22:56
2003-04-24
14:02
MySQL Server: ReplicationClosed
(6794 days)
S34.0, 4.1.0Any (all)AnyIn some cases, the slave deletes relay logs while he still may need them
692003-02-13
8:22
2003-03-03
6:45
MySQL Server: ReplicationClosed
(6846 days)
S34.0Microsoft Windows (Windows)Any4.0.9 Windows slave hangs on STOP SLAVE
702003-02-13
8:25
2003-03-03
6:49
MySQL Server: ReplicationClosed
(6846 days)
S34.0Any (all)AnyOn 4.0.10, RESET SLAVE fails to reset the master's binlog coordinates
792003-02-16
10:44
2003-03-17
14:08
MySQL Server: ReplicationClosed
(6832 days)
S34.0Any (all)Anyrelay_log_space_limit can cause deadlock if we have a big transaction
802003-02-17
9:51
2003-03-11
5:54
MySQL Server: ReplicationClosed
(6838 days)
S34.0Any (all)AnyObscure error message in replication (Error updating slave list: Query error)
822003-02-18
14:07
2003-03-03
5:52
MySQL Server: ReplicationClosed
(6846 days)
S24.0Any (all)AnyLOAD DATA *LOCAL* INFILE is not properly written to the binary log
862003-02-20
13:17
2003-02-20
13:31
MySQL Server: ReplicationClosed
(6857 days)
S33.23, 4.0Any (all)AnyLOAD DATA INFILE is not replicated by slave if replicate_*_table is set
882003-02-21
6:41
2008-09-27
8:44
MySQL Server: ReplicationClosed
(4811 days)
S35.0Any (all)AnySome SET commands should be written to the binlog as they affect next updates
902003-02-21
15:59
2019-04-05
13:29
MySQL Server: Command-line ClientsClosed
(6837 days)
S34.1Any (at least Linux)AnyIn 4.0 the mysql client prints "Unknown database ¬(;Ðpöÿ¿(öÿ¿h_@'" at connect
952003-02-24
13:44
2003-03-03
5:58
MySQL ServerClosed
(6846 days)
S34.0.11Any (all)AnyDROP TABLE returns wrong error when the database does not exist
1042003-02-26
13:33
2003-03-06
14:03
MySQL ServerClosed
(6843 days)
S34.0Any (all)AnyINSERT DELAYED does not care about SQL_LOG_BIN=0
1362003-03-09
15:55
2003-03-11
16:26
MySQL Server: ReplicationClosed
(6838 days)
S24.0Linux (Linux at least)AnyINSERT SELECT does not write the same num of rows on master and slave
1592003-03-17
7:39
2003-03-19
7:13
MySQL Server: ReplicationClosed
(6830 days)
S33.23, 4.0Any (all)Anymysqldump --first-slave or --master-data silently purges master's binlogs
1692003-03-19
14:22
2003-03-24
13:38
MySQL ServerClosed
(6825 days)
S23.23.56 and below (not in 4.0)Any (all)AnyDELETE FROM t; does not lock 't' enough, causes bad order in binlog
1742003-03-21
6:35
2003-03-21
12:27
MySQL ServerClosed
(6828 days)
S24.1Any (all)AnySHOW BINLOG EVENTS crashes (SEGV) the server if it is the first command
1772003-03-21
13:09
2003-05-13
14:17
MySQL Server: ReplicationClosed
(6775 days)
S34.0Any (all)AnyCONNECTION_ID() is badly replicated
1782003-03-21
13:12
2020-09-13
20:45
MySQL Server: ReplicationDuplicate
(6706 days)
S34.0Any (all)AnyUSER() is badly replicated (is replicated to "")
1802003-03-21
14:58
2003-04-08
9:50
MySQL Server: ReplicationClosed
(6810 days)
S34.0Any (all)AnyGRANT/REVOKE is replicated even if --replicate-wild-ignore-table=mysql.%
1862003-03-24
5:54
2003-03-25
8:09
MySQL Server: ReplicationClosed
(6824 days)
S34.0Any (all)AnyIf a connection has temporary tables and does RESET MASTER, this breaks replic.
1912003-03-25
14:24
2003-04-18
13:56
MySQL Server: ReplicationClosed
(6800 days)
S33.23Linux (Linux at least)AnyMany connections from the slave to the master cause "alarm queue is full"
1982003-03-27
6:31
2003-06-21
7:31
MySQL Server: ReplicationClosed
(6736 days)
S33.23, 4.0Any (all)AnyReplication between a 4.0.12 master and 3.23.52 slave does not work
2182003-04-01
8:09
2003-04-09
14:29
MySQL ServerClosed
(6809 days)
S33.23, 4.0Any (all)AnyLOAD DATA INFILE IGNORE is well logged, but read as LOAD DATA INFILE REPLACE
2212003-04-02
2:10
2011-02-16
23:40
MySQL Server: ReplicationWon't fix
(4633 days)
S34.0, 4.1, 5.1Any (all)AnyLOAD_FILE is not replicated
2222003-04-02
5:11
2003-04-03
1:39
MySQL Server: ReplicationClosed
(6815 days)
S34.0Any (all)AnyOptions of LOAD DATA lost in replication (FIELDS TERMINATED BY etc)
2542003-04-08
15:04
2003-06-06
7:52
MySQL Server: ReplicationClosed
(6751 days)
S2Any (all)Any3.23 master, 4.0 slave. Slave loss temp tables everytime FLUSH LOGS on master
2582003-04-09
5:23
2003-04-09
5:24
MySQL Server: ReplicationNot a Bug
(6809 days)
S3 AnyThis is a test, I'm sure I assigned #254 to me while creating so why is it open
3112003-04-21
15:04
2019-05-14
14:22
MySQL ServerClosed
(6796 days)
S34.0Linux (linux)AnyWhen selecting an unknow system variable, one can get Packets out of order
3152003-04-23
5:47
2003-04-26
5:15
MySQL Server: Command-line ClientsClosed
(6792 days)
S34.1Linux (linux at least)AnyCtrl-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 »