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.
Functionality added or changed:
to mysqld_safe and
mysqld. This option forces all error
messages to be put in a log file if the option
--console is not given. On
--log-error is enabled
as default, with a default name of
if the name is not specified.
Changed some messages from
Note: in the log files.
The mysqld server should now compile on NetWare.
Added optimization that if one does
GROUP BY ...
ORDER BY NULL then result is not sorted.
Changed default stack size from 64KB to 192KB; This fixes a
core dump problem on Red Hat 8.0 and other systems with a
glibc that requires a stack size larger
than 128K for
gethostbyaddr() to resolve a
host name. You can fix this for earlier MySQL versions by
starting mysqld with
Added mysql_waitpid to the binary
distribution and the
subpackage (required for mysql-test-run).
Renamed the main
MySQL RPM package to
MySQL-server. When updating from an older
MySQL-server.rpm simply replaces
If a slave is configured with
rules are applied to
Added timeout value for
Fixed initialization of the random seed for newly created
threads to give a better
distribution from the first call.
Fixed bug in logging to binary log (which affects replication)
a query that inserts a
NULL in an
AUTO_INCREMENT column and also uses
Fixed an unlikely bug that could cause a memory overrun when
ORDER BY constant_expression.
Fixed a table corruption in myisamchk parallel repair mode.
Fixed bug in query cache invalidation on simple table renaming.
Fixed bug in mysqladmin --relative.
Fixed incorrect number of columns in
EXPLAIN on empty table.
Fixed bug in
LEFT JOIN that caused zero
rows to be returned in the case the
condition was evaluated as
PRIVILEGES didn't correctly flush table/column
mysql.tables_priv is empty.
Fixed bug in replication when using
INFILE one a file that updated an
AUTO_INCREMENT column with
0. This bug only
affected MySQL 4.0 masters (not slaves or MySQL 3.23 masters).
If you have a slave that has replicated a file with
AUTO_INCREMENT columns, the
slave data is corrupted and you should reinitialize the
affected tables from the master.
Fixed possible memory overrun when sending a
BLOB value larger than 16M to
Fixed incorrect error message when setting a
NULL column to an expression that returned
Fixed core dump bug in
other_str contained characters
Fixed bug: When executing on master
InnoDB failed with
table full error the binary log was