This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.56). 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/advisors.html.
Functionality Added or Changed
Important Change; Cluster API:
memory page sizes in bytes rather than kilobytes, it has been
page_size_bytes. The name
page_size_kb is now deprecated and thus
subject to removal in a future release, although it currently
remains supported for reasons of backward compatibility. See
Ndb_logevent_type Type, for more information
The ndbd and ndb_mgmd man pages have been reclassified from volume 1 to volume 8. (Bug #34642)
mysqltest now has
rmdir commands for creating and removing
InnoDB adaptive hash latches could be held
too long during filesort operations, resulting in a server
crash. Now the hash latch is released when a query on
InnoDB tables performs a filesort. This
eliminates the crash and may provide significant performance
improvements on systems on which many queries using filesorts
with temporary tables are being performed.
When configured with
MySQL failed to compile using gcc 4.3 on
64bit FreeBSD systems.
MySQL Cluster: The failure of a DDL statement could sometimes lead to node failures when attempting to execute subsequent DDL statements. (Bug #34160)
A periodic failure to flush the send buffer by the
NDB TCP transporter could cause a
unnecessary delay of 10 ms between operations.
When all data and SQL nodes in the cluster were shut down
abnormally (that is, other than by using
in the cluster management client), ndb_mgm
used excessive amounts of CPU.
MySQL Cluster: Transaction atomicity was sometimes not preserved between reads and inserts under high loads. (Bug #31477)
NDBCLUSTER test failures
occurred in builds compiled using icc on IA64
MySQL Cluster: Having tables with a great many columns could cause Cluster backups to fail. (Bug #30172)
ON DUPLICATE KEY UPDATE concurrently with or following
TRUNCATE TABLE statement on an
NDB table failed with
NDB error 4350
Transaction already aborted.
It was possible in
config.ini to define
cluster nodes having node IDs greater than the maximum permitted
When reading a
BIT(64) value using
bytes were written to the buffer rather than the expected 8
mysql_explain_log concatenated multiple-line
statements, causing malformed results for statements that
contained SQL comments beginning with
ALTER VIEW statement
on a table crashed the server.
Passing anything other than an integer argument to a
LIMIT clause in a prepared statement would
fail. (This limitation was introduced to avoid replication
problems; for example, replicating the statement with a string
argument would cause a parse failure in the slave). Now,
arguments to the
LIMIT clause are converted
to integer values, and these converted values are used when
logging the statement.
An internal buffer in mysql was too short. Overextending it could cause stack problems or segmentation violations on some architectures. (This is not a problem that could be exploited to run arbitrary code.) (Bug #33841)
Large unsigned integers were improperly handled for prepared statements, resulting in truncation or conversion to negative numbers. (Bug #33798)
make_binary_distribution passed the
--print-libgcc-file option to the C compiler,
but this does not work with the ICC compiler.
When MySQL was built with OpenSSL, the SSL library was not properly initialized with information of which endpoint it was (server or client), causing connection failures. (Bug #33050)
Repeated creation and deletion of views within prepared statements could eventually crash the server. (Bug #32890)
References: See also Bug #34587.
Executing a prepared statement associated with a materialized cursor sent to the client a metadata packet with incorrect table and database names. The problem occurred because the server sent the name of the temporary table used by the cursor instead of the table name of the original table.
The same problem occurred when selecting from a view, in which case the name of the table name was sent, rather than the name of the view. (Bug #32265)
SHOW STATUS caused a server crash
InnoDB had not been initialized.
The mysqld crash handler failed on Windows. (Bug #31745)
The MySQL preferences pane did not work to start or stop MySQL on Mac OS X 10.5 (Leopard). (Bug #28854)
For upgrading to a new major version using RPM packages (such as 4.1 to 5.0), if the installation procedure found an existing MySQL server running, it could fail to shut down the old server, but also erroneously removed the server's socket file. Now the procedure checks for an existing server package from a different vendor or major MySQL version. In such case, it refuses to install the server and recommends how to safely remove the old packages before installing the new ones. (Bug #28555)
mysqlhotcopy silently skipped databases with names consisting of two alphanumeric characters. (Bug #28460)
mysql did not use its completion table. Also, the table contained few entries. (Bug #24624)
mysql_config output did not include
-lmygcc on some platforms when it was needed.