End of Product Lifecycle. Active 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.
The MySQL 4.0.19 binaries were uploaded to the download mirrors on May, 10th. However, a potential crashing bug was found just before the 4.0.19 release was publicly announced and published from the 4.0 download pages at http://dev.mysql.com/.
A fix for the bug was pushed into the MySQL source tree shortly after it could be reproduced and is included in MySQL 4.0.20. Users upgrading from MySQL 4.0.18 should upgrade directly to MySQL 4.0.20 or later.
See (Bug#3596) for details (it was reported against MySQL-4.1, but was confirmed to affect 4.0.19 as well).
Functionality added or changed:
If length of a timestamp field is defined as 19, the timestamp
is displayed as
"YYYY-MM-DD HH:MM:SS. This
is done to make it easier to use tables created in MySQL 4.1
to be used in MySQL 4.0.
If you use
RAID_CHUNKS with a value >
255 it is set to 255. This was made to ensure that all raid
directories are always 2 hex bytes. (Bug#3182)
Changed that the optimizer now considers the index specified
FORCE INDEX clause as a candidate to
ORDER BY as well.
Until now, in
SELECT ... UNION SELECT ... ORDER BY
..., it was possible to qualify a column name in the
ORDER BY clause with a table name. This is
no longer possible. Column names in
BY should refer to names established in the first
SELECT of the
MASTER_SERVER_ID is not
The following is relevant mainly for Mac OS X users who use a
case-insensitive file system. This is not relevant for Windows
InnoDB in this case always stores
file names in lower case:
You can now force
lower_case_table_names to 0
from the command line or a configuration file. This is useful
with case-insensitive file systems when you have previously
2 and you have created
InnoDB tables were stored in
mixed case while setting
lower_case_table_names to a
nonzero value now forces it to lower case (to make the table
names case insensitive).
Because it is possible to crash
tables by referring to them with different case on a
case-insensitive file system, use
lower_case_table_names = 2 on
such file systems.
Changed that the relay log is flushed to disk by the slave I/O thread every time it reads a relay log event. This reduces the risk of losing some part of the relay log in case of brutal crash.
When a session having open temporary tables terminates, the
statement automatically written to the binary log is now
DROP TEMPORARY TABLE IF EXISTS instead of
DROP TEMPORARY TABLE, for more robustness.
Do not allow stray
',' at the end of field
INTERVAL now can handle big values for
seconds, minutes and hours. (Bug#3498)
Blank host name did not work as documented for table and
column privileges. Now it works the same way as
Fixed a harmless buffer overflow in
replace utility. (Bug#3541)
Fixed a bug in
MATCH ... AGAINST() searches
when another thread was doing concurrent inserts into the
MyISAM table in question. The first ---
full-text search --- query could return incorrect results in
this case (for example, “phantom” rows or not all
matching rows, even an empty result set). The easiest way to
check whether you are affected is to start
and see whether it helps.
Fixed bug when doing
DATABASE on a directory containing non- MySQL files.
Now a proper error message is returned.
Fixed problem with multiple-table-update and BDB tables. (Bug: #3098)
Fixed memory leak when dropping database with
RAID tables. (Bug#2882)
Fixed core dump crash in replication during relay-log switch
when the relay log went over
max_relay_log_size and the
slave thread did a
flush_io_cache() at the
Fixed hangup bug when issuing multiple
START from different threads at the same time.
One can now kill threads that is 'stuck' in the join optimizer (can happen when there is MANY tables in the join in which case the optimizer can take really long time). (Bug#2825)
Fixed bug in query cache statistic, more accurate formula linked statistic variables mentioned in the manual.
Fixed bugs with names of tables, databases, and columns that end to space (Bug#2985)
Fixed all bugs in scripts for creating/upgrading system database (Bug#2874) Added tests which guarantee against such bugs in the future.
Fixed bug in
mysql command-line client in
interpreting quotes within comments. (Bug#539)
Fixed a bug in mysqlbinlog that caused one pointer to be free'd twice in some cases.
Fixed a bug in boolean full-text search, that sometimes could
lead to false matches in queries with several levels of
+ operator (for
MATCH ... AGAINST('+(+(word1 word2))
+word3*' IN BOOLEAN MODE).
Fixed Windows-specific portability bugs in
Fixed a bug in multiple-table
DELETE that was caused by
foreign key constraints. If the order of the tables
established by MySQL optimizer did not match parent-child
order, no rows were deleted and no error message was provided.
Fixed a few years old bug in the range optimizer that caused a segmentation fault on some very rare queries. (Bug#2698)
Replication: If a client connects to a slave server and issues
an administrative statement for a table (for example,
OPTIMIZE TABLE or
REPAIR TABLE), this could
sometimes stop the slave SQL thread. This does not lead to any
corruption, but you must use
SLAVE to get replication going again. (Bug#1858) The
bug was accidentally not fixed in 4.0.17 as it was
unfortunately earlier said.
Corrected the master's binary log position that
InnoDB reports when it is doing a crash
recovery on a slave server. (Bug#3015)
Changed that when a
DROP TEMPORARY TABLE
statement is automatically written to the binary log when a
session ends, the statement is recorded with an error code of
value zero (this ensures that killing a
SELECT on the master does not
result in a superfluous error on the slave). (Bug#3063)
Changed that when a thread handling
INSERT DELAYED (also known as a
delayed_insert thread) is killed, its
statements are recorded with an error code of value zero
(killing such a thread does not endanger replication, so we
thus avoid a superfluous error on the slave). (Bug#3081)
Fixed that a statement never triggers a superfluous error on
the slave, if it must be excluded given the
--replicate-* options. The bug was that if
the statement had been killed on the master, the slave would
Fixed a rare error condition that caused the slave SQL thread
spuriously to print the message
Binlog has bad magic
number and stop when it was not necessary to do so.
Fixed the column
its disk image in the
to be correct if the master had version 3.23 (it was too big
by 6 bytes). This bug does not exist in the 5.0 version.
Fixed a memory corruption when replicating a
INFILE when the master had version 3.23. Some
smaller problems remain in this setup, See
Section 14.7, “Replication Features and Known Problems”. (Bug#3422)