End of Product LifecycleActive development and support for MySQL Database Server versions 3.23, 4.0, and 4.1 has ended. For details, see http://www.mysql.com/about/legal/lifecycle/#calendar. Please consider upgrading to a recent version. Further updates to the content of this manual will be minimal. All formats of this manual will continue to be available until 31 Dec 2010.
This is a bugfix release for the MySQL 4.0 release family.
This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details, please see http://www.mysql.com/products/enterprise.
Functionality added or changed:
Deleting entries from a large
could cause index corruption when it needed to shrink. Deletes
from an index can happen when a record is deleted, when a key
changes and must be moved, and when a key must be un-inserted
because of a duplicate key. This can also happen in
REPAIR TABLE when a duplicate
key is found and in myisamchk when sorting
the records by an index. (Bug #22384)
Transient errors in replication from master to slave may
Got fatal error 1236: 'binlog
truncated in the middle of event' errors on the
slave. (Bug #4053)
A server or network failure with an open client connection would cause the client to hang even though the server was no longer available. (Bug #9678)
mysqlhotcopy did not copy
RAID directories with names that contained
nondecimal hex digits. (It copied only directories containing
9 and ignored those containing
A query with a
WHERE clause containing
unexpected results. (Bug #12728)