This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.84). 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.
Uninstalling MySQL using the MySQL installer on Windows would
my.ini file. The file is no longer
deleted. In addition, when a new installation is conducted, any
existing configuration file will be renamed to
myDATETIME.ini.bak during configuration.
A Windows Installation using the GUI installer would fail with:
MySQL Server 5.1 Setup Wizard ended prematurely The wizard was interrupted before MySQL Server 5.1. could be completely installed. Your system has not been modified. To complete installation at another time, please run setup again. Click Finish to exit the wizard
This was due to a step in the MSI installer that could fail to execute correctly on some environments. (Bug #45418)
Creating a new instance after previously removing an instance would fail to complete the installation properly because the security settings could not be applied correctly. (Bug #44428)
During installation on Windows, the MySQL Instance Configuration Wizard window could be opened at a size too small to be usable. (Bug #38723)
The server crashed if evaluation of
GROUP_CONCAT(... ORDER BY)
required allocation of a sort buffer but allocation failed.
The server crashed when executing a prepared statement
containing a duplicated
MATCH() function call
in the select list and
ORDER BY clause; for
SELECT MATCH(a) AGAINST('test') FROM t1 ORDER
BY MATCH(a) AGAINST('test').
SHOW PROCESSLIST could access
freed memory of a stored procedure run in a concurrent session.
Several Valgrind warnings were corrected. (Bug #46003, Bug #46034, Bug #46042)
An optimization that moved an item from a subquery to an outer query could cause a server crash. (Bug #46051)
Invalid memory reads could occur using the compressed client/server protocol. (Bug #45031)
After an error such as a table-full condition,
could cause an assertion failure for debug builds.
For problems reading SSL files during SSL initialization, the
server wrote error messages to
than to the error log.
The server did not always check the return value of calls to the
A test for stack growth failed on some platforms, leading to server crashes. (Bug #42213)
References: See also Bug #62856.
make_binary_distribution did not always generate correct distribution names. (Bug #37808)
Compiler warnings on Windows were fixed. (Bug #45287)
The vendor name change from MySQL AB to Sun Microsystems, Inc. in RPM packages was not handled gracefully when upgrading MySQL using an RPM package. (Bug #45534)
Invalid input could cause invalid memory reads by the parser. (Bug #45010)
The server printed warnings at startup about adjusting the value
variable. (These were harmless, but might be seen by users as
InnoDB reached its limit on the number of
concurrent transactions (1023), it wrote a descriptive message
to the error log but returned a misleading error message to the
client, or an assertion failure occurred.
References: See also Bug #46672.
Installation of MySQL on Windows would fail to set the correct location for the character set files, which could lead to mysqld and mysql failing to initialize properly. (Bug #17270)
When performing an installation on Windows using the GUI
installer, the installer would fail to wait long enough during
installation for the MySQL service to be installed, which would
cause the installation to fail and may cause security settings,
such as the
root password to not be applied