924
MySQL Technical Reference for Version 4.1.1-alpha
7 SET FOREIGN_KEY_CHECKS=0 was not replicated properly. The fix probably will not be
backported to 3.23.
7 On a slave, LOAD DATA INFILE which had no IGNORE or REPLACE clause on the master,
was replicated with IGNORE. While this is not a problem if the master and slave data
are identical (a LOAD that produces no duplicate conflicts on the master will produce
none on the slave anyway), which is true in normal operation, it is better for debugging
not to silently add the IGNORE. That way, you can get an error message on the slave and
discover that for some reason, the data on master and slave are different and investigate
why. (Bug #571)
7 On a slave, LOAD DATA INFILE printed an incomplete "Duplicate entry '%-.64s' for key
%d"' message (the key name and value were not mentioned) in case of duplicate conflict
(which does not happen in normal operation). (Bug #573)
7 When using a slave compiled with --debug, CHANGE MASTER TO RELAY_LOG_POS could
cause a debug assertion failure. (Bug #576)
7 When doing a LOCK TABLES WRITE on an InnoDB table, commit could not happen, if
the query was not written to the binary log (for example, if --log-bin was not used,
or binlog-ignore-db was used). (Bug #578)
7 If a 3.23 master had open temporary tables that had been replicated to a 4.0 slave, and
the binlog got rotated, these temporary tables were immediately dropped by the slave
(which caused problems if the master used them subsequently). This bug had been fixed
in 4.0.13, but in a manner which caused an unlikely inconvenience: if the 3.23 master
died brutally (power failure), without having enough time to automatically write DROP
TABLE statements to its binlog, then the 4.0.13 slave would not notice the temporary
tables have to be dropped, until the slave mysqld server is restarted. This minor
inconvenience is fixed in 3.23.57 and 4.0.14 (meaning the master must be upgraded to
3.23.57 and the slave to 4.0.14 to remove the inconvenience). (Bug #254)
7 If MASTER_POS_WAIT() was waiting, and the slave was idle, and the slave SQL thread
terminated, MASTER_POS_WAIT() would wait forever. Now when the slave SQL thread
terminates, MASTER_POS_WAIT() immediately returns NULL ("slave stopped"). (Bug
#651)
7 After RESET SLAVE; START SLAVE;, the Relay_Log_Space value displayed by SHOW
SLAVE STATUS was too big by four bytes. (Bug #763)
7 If a query was ignored on the slave (because of replicate-ignore-table and other
similar rules), the slave still checked if the query got the same error code (0, no error)
as on the master. So if the master had an error on the query (for example, "Duplicate
entry" in a multiple-row insert), then the slave stopped and warned that the error codes
didn't match. (Bug #797)
D.3.5 Changes in release 4.0.13 (16 May 2003)
Functionality added or changed:
7 PRIMARY KEY now implies NOT NULL. (Bug #390)
7 The Windows binary packages are now compiled with --enable-local-infile to
match the Unix build configuration.
|
manual-866.html
manual-868.html
|