This is a new Beta development release, fixing recently discovered bugs.
This Beta release, as any other pre-production release, should not be installed on production level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release. Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
This section documents all changes and bug fixes that have been applied since the last official MySQL release. 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.
Functionality added or changed:
The number of function names affected by
IGNORE_SPACE was reduced
significantly in MySQL 5.1.13, from about 200 to about 30. (For
see Section 8.2.4, “Function Name Parsing and Resolution”.) This change improves
the consistency of parser operation. However, it also introduces
the possibility of incompatibility for old SQL code that relies
on the following conditions:
For functions that are no longer affected by
IGNORE_SPACE as of MySQL
5.1.13, that strategy no longer works. Either of the following
approaches can be used if you have code that is subject to the
If a stored function has a name that conflicts with a
built-in function, refer to the stored function with a
schema name qualifier, regardless of whether whitespace is
present. For example, write
Alternatively, rename the stored function to use a nonconflicting name and change invocations of the function to use the new name.
system variable has been removed and should no longer be used.
Binary distributions of MySQL 5.1.12 were built without support for partitioning. This has been corrected except for NetWare. (Bug#23949)
If the user specified the server options
--table-open-cache=, a warning would be given in some cases that some
values were recalculated, with the result that
--table-open-cache could be
assigned greater value.
In such cases, both the warning and the increase in the
--table-open-cache value were
completely harmless. Note also that it is not possible for the
MySQL Server to predict or to control limitations on the maximum
number of open files, since this is determined by the operating
mysql_upgrade now passes all the parameters
specified on the command line to both
mysqldump --single-transaction now uses
START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT
*/ rather than
BEGIN to start
a transaction, so that a consistent snapshot will be used on
those servers that support it.
InnoDB showed substandard performance with
multiple queries running concurrently.
Important Change: When installing MySQL on AIX 5.3, you must upgrade AIX to technology level 7 (5300-07) to ensure the required thread libraries are available.
MySQL Cluster: Backup of a cluster failed if there were any tables with 128 or more columns. (Bug#23502)
MySQL Cluster: Cluster backups failed when there were more than 2048 schema objects in the cluster. (Bug#23499)
MySQL Cluster: Restoring a cluster failed if there were any tables with 128 or more columns. (Bug#23494)
The management client command
ALL DUMP 1000
would cause the cluster to crash if data nodes were connected to
the cluster but not yet fully started.
NDB source file included a
memset() call with reversed arguments.
MySQL Cluster: If a node restart could not be performed from the REDO log, no node takeover took place. This could cause partitions to be left empty during a system restart. (Bug#22893)
When inserting a row into an
table with a duplicate value for a nonprimary unique key, the
error issued would reference the wrong key.
MySQL Cluster: Aborting a cluster backup too soon after starting it caused a forced shutdown of the data nodes. (Bug#19148)
Replication: Column names were not quoted properly for replicated views. (Bug#19736)
Transient errors in replication from master to slave may trigger
Got fatal error 1236: 'binlog truncated in the
middle of event' errors on the slave.
Disk Data: In the event of an aborted multiple update, the space in the Disk Data log buffer to be freed as a result was actually freed twice, which could eventually lead to a crash. (Bug#23430)
Cluster API: When multiple processes or threads in parallel performed the same ordered scan with exclusive lock and updated the retrieved records, the scan could skip some records, which as a result were not updated. (Bug#20446)
There was a race condition in the
yaSSL-related memory leaks were detected by Valgrind. (Bug#23981)
MySQL 5.0.26 introduced an ABI incompatibility, which this release reverts. Programs compiled against 5.0.26 are not compatible with any other version and must be recompiled. (Bug#23427)
M % 0
NULL, but (
M % 0) IS NULL
InnoDB crashed when trying to display an
error message about a foreign key constraint violation when the
two tables are in different schemas.
MySQL failed to build on Linux/Alpha. (Bug#23256)
This regression was introduced by Bug#21250.
cause a server crash for several operations on
MyISAM tables: repair table, create index by
sort, repair by sort, parallel repair, bulk insert.
The return value from
my_seek() was ignored.
SQL_BIG_RESULT did not influence the
sort plan for query execution.
If a table contains an
inserting into an insertable view on the table that does not
AUTO_INCREMENT column should not
change the value of
LAST_INSERT_ID(), because the
side effects of inserting default values into columns not part
of the view should not be visible. MySQL was incorrectly setting
LAST_INSERT_ID() to zero.
NULL pointer caused a server
The optimizer sometimes mishandled R-tree indexes for
GEOMETRY data types, resulting in a server
Use of a DES-encrypted SSL certificate file caused a server crash. (Bug#21868)
Use of a subquery that invoked a function in the column list of the outer query resulted in a memory leak. (Bug#21798)
It was not possible to do an atomic rename of the log tables without the possibility of losing rows. Now you can do this:
USE mysql; CREATE TABLE IF NOT EXISTS general_log2 LIKE general_log; RENAME TABLE general_log TO general_log_backup, general_log2 TO general_log;
Within a prepared statement,
SELECT (COUNT(*) =
1) (or similar use of other aggregate functions) did
not return the correct result for statement re-execution.
Within a stored routine, a view definition cannot refer to routine parameters or local variables. However, an error did not occur until the routine was called. Now it occurs during parsing of the routine creation statement.
A side effect of this fix is that if you have already created
such routines, and error will occur if you execute
SHOW CREATE PROCEDURE or
SHOW CREATE FUNCTION. You
should drop these routines because they are erroneous.
WITH ROLLUP could group unequal values.
Range searches on columns with an index prefix could miss records. (Bug#20732)
The server did not allocate sufficient memory for some queries
for which a
BY conversion is possible and an
BY clause is present, resulting in a server crash.
LIKE searches failed for indexed
utf8 character columns.
sql_mode = TRADITIONAL, MySQL
incorrectly aborted on warnings within stored routines and
FLUSH INSTANCES in Instance Manager triggered
an assertion failure.
Within a trigger for a base table, selecting from a view on that base table failed. (Bug#19111)
DELETE IGNORE could hang for foreign key
InnoDB used table locks (not row locks)
within stored functions.
At shutdown, Instance Manager told guarded server instances to stop, but did not wait until they actually stopped. (Bug#17486)
mysql-test-run did not work correctly for RPM-based installations. (Bug#17194)
A client library crash was caused by executing a statement such
SELECT * FROM t1 PROCEDURE ANALYSE() using
a server side cursor on a table
t1 that does
not have the same number of columns as the output from
A literal string in a
GROUP BY clause could
be interpreted as a column name.
Entries in the slow query log could have an incorrect
Lack of validation for input and output
TIME values resulted in several
SEC_TO_TIME() in some
cases did not clip large values to the
TIME range appropriately;
BIGINT UNSIGNED values as signed; only
truncation warnings were produced when both truncation and
Several string functions could return incorrect results when given very large length arguments. (Bug#10963)