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.
Functionality added or changed:
mysqld now reads an additional option file
group having a name corresponding to the server's release
[mysqld-4.0] for 4.0.x servers,
[mysqld-4.1] for 4.1.x servers, and so
forth. This allows options to be specified on a
A documentation change: Function
INTERVAL(NULL, ...) returns
SQL_CALC_FOUND_ROWS option now always
returns the total number of rows for any
Comment lines in option files can now start from the middle of
a line, too (like
basedir=c:\mysql # installation
Changed optimizer slightly to prefer index lookups over full table scans in some boundary cases.
that can be used to force the optimizer to use keys instead of
table scans even if the cardinality of the index is low.
Added optimization that converts
to normal join in some cases.
A documentation change: added a paragraph about failover in replication (how to use a surviving slave as the new master, how to resume to the original setup). See Section 14.10, “Replication FAQ”.
MySQL now issues a warning (not an error, as in 4.0.13) when it opens a table that was created with MySQL 4.1.
SHOW BINLOG EVENTS FROM x where
x is less than 4 now silently converts
x to 4 instead of printing an error. The
same change was done for
CHANGE MASTER TO
CHANGE MASTER TO
mysqld now only adds an interrupt handler
SIGINT signal if you start it with
--gdb option. This is
done because some MySQL users encountered strange problems
when they accidentally sent
variable; the relay log is rotated automatically when its size
0 (the default),
max_binlog_size is used (as
in older versions).
max_binlog_size still applies
to binary logs in any case.
now rotates relay logs in addition to the other types of logs
set was rewritten. The old algorithm could not handle cases
"sä" > "ßa". See
Section 9.2, “Using the German Character Set”. In rare cases it
resulted in table corruption.
Fixed a problem with the password prompt on Windows. (Bug#683)
ALTER TABLE ... UNION=(...) for
MERGE table is now allowed even if some
MyISAM tables are read only.
Fixed a problem with
CREATE TABLE t1 SELECT
Removed some incorrect lock warnings from the error log.
Fixed a probable race condition in the replication code that
could potentially lead to
INSERT statements not being
replicated in the event of a
command or when the binary log exceeds
Fixed a crashing bug in
GROUP BY or
Fixed bugs in optimizer that sometimes prevented MySQL from
FULLTEXT indexes even though it was
possible (for example, in
SELECT * FROM t1 WHERE
MATCH a,b AGAINST("index") > 0).
Fixed a bug with “table is full” in
Fixed a security problem that enabled users with no privileges
to obtain information on the list of existing databases by
SHOW TABLES and similar
Fixed a stack problem on UnixWare/OpenUnix.
Fixed a configuration problem on UnixWare/OpenUNIX and OpenServer.
Fixed a problem with
SET CHARACTER SET DEFAULT works.
MERGE table behavior in
ORDER BY ... DESC queries. (Bug#515)
Fixed password-checking problem on Windows. (Bug#464)
ERROR 1105: Unknown error that
occurred for some
queries, where a column that was declared as
NULL was compared with an expression that took
Changed timeout in
mysql_real_connect() to use
poll() instead of
select() to work around problem with many
open files in the client.
Fixed incorrect results from
AGAINST used with a
The maximum value for system variables was limited to 4294967295 when specified on the command line.
Fixed a bug that sometimes caused spurious “Access
denied” errors in
HANDLER ... READ
statements, when a table is referenced via an alias.
Fixed portability problem with
which caused MySQL to give "Freeing wrong aligned pointer"
errors on SCO 3.2.
ALTER TABLE ... ENABLE/DISABLE KEYS could
cause a core dump when done after an
INSERT DELAYED statement on the
Fixed problem with conversion of localtime to GMT where some times resulted in different (but correct) timestamps. Now MySQL should use the smallest possible timestamp value in this case. (Bug#316)
Fixed a bug (accidentally introduced by us but present only in
version 4.0.13) that made
SELECT into an
column not replicate well. This bug is in the master, not in
the slave. (Bug#490)
Fixed a bug: When an
SELECT statement inserted rows into a
nontransactional table, but failed at some point (for example,
due to a “Duplicate key” error), the query was
not written to the binary log. Now it is written to the binary
log, with its error code, as all other queries are. About the
slave-skip-errors option for how to handle
partially completed queries in the slave, see
Section 14.8, “Replication and Binary Logging Options and Variables”. (Bug#491)
SET foreign_key_checks = 0 was not
replicated properly. The fix probably will not be backported
On a slave,
DATA INFILE which had no
REPLACE clause on the
master, was replicated with
Although this is not a problem if the master and slave data
are identical (a
LOAD that produces no
duplicate conflicts on the master produces none on the slave
anyway), which is true in normal operation, it is better for
debugging not to silently add the
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)
On a slave,
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)
When using a slave compiled with
CHANGE MASTER TO RELAY_LOG_POS could cause
a debug assertion failure. (Bug#576)
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)
If a 3.23 master had open temporary tables that had been
replicated to a 4.0 slave, and the binary log 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
statements to its binary log, 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)
waiting, and the slave was idle, and the slave SQL thread
would wait forever. Now when the slave SQL thread terminates,
If a query was ignored on the slave (because of
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