This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.33.
Incompatible Change; MySQL Cluster:
configuration parameter has changed its type and possible
false are no longer accepted for this
parameter. If you were using this parameter and had it set to
false in a previous release, you must
change it to
0. If you had this parameter
true, you should instead use
1 to obtain the same behavior as
2 to take advantage of new
functionality introduced with this release, as described in
the section cited above.
function returned a binary string. Now it returns a string with
a character set and collation given by
collation_connection so that it
can return month and weekday names containing non-ASCII
When using a
MERGE table, the definition of
the table and the underlying
are checked each time the tables are opened for access
INSERT statement). Each table is
compared for column order, types, sizes, and associated indexes.
If there is a difference in any one of the tables, the statement
status variable, which indicates the number of seconds since the
FLUSH STATUS statement.
(Community contribution by Jeremy Cole)
SHOW PROFILES and
SHOW PROFILE statements to
display statement profile data, and the accompanying
Profiling is controlled using the
variables. see SHOW PROFILES Syntax, and
The INFORMATION_SCHEMA PROFILING Table. (Community contribution by
The profiling feature is enabled using the
to configure. These options are enabled by
default; to disable them, use
localhost anonymous user account created
during MySQL installation on Windows now has no global
privileges. Formerly this account had all global privileges. For
operations that require global privileges, the
root account can be used instead.
now is enabled by default for binary Mac OS X distributions. Use
of thread priorities degrades performance on Mac OS X.
This is the last version for which MySQL-Max RPM distributions are available. (This change was already made for non-RPM binary distributions in 5.0.27.)
to configure. If configure
is run with this option, the
--init-file options for
mysqld are disabled and cannot be used. For
Windows, the configure.js script recognizes
DISABLE_GRANT_OPTIONS flag, which has the
The bundled yaSSL library was upgraded to version 1.5.8.
INFORMATION_SCHEMA table with
ORDER BY in a subquery could cause a server
We would like to thank Oren Isacson of Flowgate Security Consulting and Stefan Streichsbier of SEC Consult for informing us of this problem. (Bug #24630, Bug #26556, CVE-2007-1420)
ENUM columns that had
enumeration values containing commas, the commas were mapped to
0xff internally. However, this rendered the
commas indistinguishable from true
characters in the values. This no longer occurs. However, the
fix requires that you dump and reload any tables that have
ENUM columns containing any true
0xff values. Dump the tables using
mysqldump with the current server before
upgrading from a version of MySQL 5.0 older than 5.0.36 to
version 5.0.36 or newer.
MySQL Cluster; Partitioning:
A query with an
IN clause against an
NDB table employing explicit
user-defined partitioning did not always return all matching
MySQL Cluster: Hosts in clusters with large numbers of nodes could experience excessive CPU usage while obtaining configuration data. (Bug #25711)
MySQL Cluster: In some circumstances, shutting down the cluster could cause connected mysqld processes to crash. (Bug #25668)
Memory allocations for
columns were calculated incorrectly, resulting in space being
wasted and other issues.
MySQL Cluster: The failure of a master node during a node restart could lead to a resource leak, causing later node failures. (Bug #25554)
MySQL Cluster: A node shutdown occurred if the master failed during a commit. (Bug #25364)
Creating a nonunique index with the
HASH clause silently created an ordered index instead
of issuing a warning.
ndb_size.tmpl file (necessary for using
ndb_size.pl script) was missing from
When a data node was shut down using the management client
STOP command, a connection event
NDB_LE_Connected) was logged instead of a
disconnection event (
MySQL Cluster: The management server did not handle logging of node shutdown events correctly in certain cases. (Bug #22013)
SELECT statements with a
TEXT column in the selected
column list and a
WHERE condition including a
primary key lookup on a
primary key produced empty result sets.
SET PASSWORD was written to
the binary log, double quotation marks were included in the
statement. If the slave was running in with the server SQL mode
ANSI_QUOTES, then the
event failed, which halted the replication process.
Replication: A stored procedure, executed from a connection using a binary character set, and which wrote multibyte data, would write incorrectly escaped entries to the binary log. This caused syntax errors, and caused replication to fail. (Bug #23619, Bug #24492)
Changes to the
system variable were not replicated.
Replication: If a slave server closed its relay log (for example, due to an error during log rotation), the I/O thread did not recognize this and still tried to write to the log, causing a server crash. (Bug #10798)
Deletion of an
took a very long time.
method using execution type
Commit and abort
AO_IgnoreError could lead to a crash
of the transaction coordinator (
Cluster API: A unique index lookup on a nonexistent tuple could lead to a data node timeout (error 4012). (Bug #25059)
libndbclient.so was not versioned.
ORDER BY or
could yield different results when selecting from a view and
selecting from the underlying table.
DISTINCT queries that were executed using a
loose scan for an
InnoDB table that had been
emptied caused a server crash.
LEFT JOIN comparisons could be
evaluated incorrectly, leading to improper query results.
WITH CHECK OPTION clause for views was
ignored for updates of multiple-table views when the updates
could not be performed on fly and the rows to update had to be
put into temporary tables first.
INFILE did not work with pipes.
InnoDB parser sometimes did not account
for null bytes, causing spurious failure of some queries.
View definitions that used the
were treated as containing the
which has a different precedence and can produce different
An error in the name resolution of nested
USING constructs was corrected.
GROUP BY and
NULL values for columns that have a
UNIQUE index. .
--with-readline option for
configure did not work for commercial source
packages, but no error message was printed to that effect. Now a
message is printed.
mysql_stmt_fetch() did an
invalid memory deallocation when used with the embedded server.
Referencing an ambiguous column alias in an expression in the
ORDER BY clause of a query caused the server
A yaSSL program named test was installed, causing conflicts with the test system utility. It is no longer installed. (Bug #25417)
UNIQUE index containing many
NULL values, the optimizer would prefer the
conditions over other more selective indexes. .
AFTER UPDATE trigger on an
InnoDB table with a composite primary key
caused the server to crash.
NULL value to a user-defined
function from within a stored procedure crashes the server.
perror crashed on some platforms due to
failure to handle a
mysql.server stop timed out too quickly (35 seconds) waiting for the server to exit. Now it waits up to 15 minutes, to ensure that the server exits. (Bug #25341)
mysql_kill() caused a server
crash when used on an SSL connection.
yaSSL was sensitive to the presence of whitespace at the ends of lines in PEM-encoded certificates, causing a server crash. (Bug #25189)
A query with
ORDER BY and
BY clauses where the
clause had more elements than the
clause caused a memory overrun leading to a crash of the server.
ON DUPLICATE KEY UPDATE defeated the
usual restriction against inserting into a join-based view
unless only one of the underlying tables is used.
Using a view in combination with a
clause caused column aliases to be ignored.
QUICK could sometimes cause one of the affected tables
to become corrupted.
ALTER TABLE ... ENABLE KEYS acquired a global
lock, preventing concurrent execution of other statements that
use tables. .
An assertion failed incorrectly for prepared statements that
contained a single-row uncorrelated subquery that was used as an
argument of the
IS NULL predicate.
A return value of
-1 from user-defined
handlers was not handled well and could result in conflicts with
Accessing a fixed record format table with a crashed key definition results in server/myisamchk segmentation fault. (Bug #24855)
mysqlaccess looked for option files in
/etc even if the
--sysconfdir option for
configure had been given to specify a
If there was insufficient memory available to mysqld, this could sometimes cause the server to hang during startup. (Bug #24751)
Optimizations that are legal only for subqueries without tables
WHERE conditions were applied for any
subquery without tables.
ORDER BY or
list included a constant expression being optimized away and, at
the same time, containing single-row subselects that returned
more that one row, no error was reported. If a query required
sorting by expressions containing single-row subselects that
returned more than one row, execution of the query could cause a
ALTER TABLE, using
could cause a
server crash. Now the
ORDER BY clause permits
only column names to be specified as sort criteria (which was
the only documented syntax, anyway).
A workaround was implemented to avoid a race condition in the
mysqltest crashed with a stack overflow. (Bug #24498)
Within stored routines or prepared statements, inconsistent
results occurred with multiple use of
INSERT ... SELECT
... ON DUPLICATE KEY UPDATE when the
DUPLICATE KEY UPDATE clause erroneously tried to
assign a value to a column mentioned only in its
Expressions of the form
(a, b) IN (SELECT a, MIN(b)
FROM t GROUP BY a) could produce incorrect results
a of table
NULL values while column
b did not.
If a prepared statement accessed a view, access to the tables listed in the query after that view was checked in the security context of the view. (Bug #24404)
Attempts to access a
MyISAM table with a
corrupt column definition caused a server crash.
When opening a corrupted
.frm file during a
query, the server crashes.
Some joins in which one of the joined tables was a view could return erroneous results or crash the server. (Bug #24345)
A view was not handled correctly if the
SELECT part contained
A query using
cause the server to crash.
unsigned_column NOT IN
Expressions of the form
(a, b) IN (SELECT c, d
...) could produce incorrect results if
b, or both were
FETCH statement using a cursor
on a table which was not in the table cache could sometimes
cause the server to crash.
Queries that evaluate
NULL IN (SELECT ... UNION SELECT
...) could produce an incorrect result
FALSE instead of
Hebrew-to-Unicode conversion failed for some characters. Definitions for the following Hebrew characters (as specified by the ISO/IEC 8859-8:1999) were added: LEFT-TO-RIGHT MARK (LRM), RIGHT-TO-LEFT MARK (RLM) (Bug #24037)
UPDATE statements were
slower than in previous versions when the search key could not
be converted to a valid value for the type of the search column.
Within a stored routine, accessing a declared routine variable
PROCEDURE ANALYSE() caused a server
When reading from the standard input on Windows, mysqlbinlog opened the input in text mode rather than binary mode and consequently misinterpreted some characters such as Control+Z. (Bug #23735)
The row count for
MyISAM tables was not
updated properly, causing
STATUS to report incorrect values.
User-defined variables could consume excess memory, leading to a
crash caused by the exhaustion of resources available to the
MEMORY storage engine, due to the fact that
this engine is used by MySQL for variable storage and
intermediate results of
GROUP BY queries.
been used, such a condition could instead give rise to the
misleading error message You may only use constant
expressions with SET, rather than Out of
memory (Needed NNNNNN bytes).
Some queries against
used subqueries failed. .
readline detection did not work correctly on
If there was insufficient memory to store or update a blob
record in a
MyISAM table then the table will
marked as crashed.
MyISAM table that became
corrupted could crash myisamchk and possibly
the MySQL Server.
The number of
setsockopt() calls performed
for reads and writes to the network socket was reduced to
decrease system call overhead.
mysql_upgrade failed when called with a
--basedir path name
SET lc_time_names = permitted only exact literal values, not expression
STDDEV() function returned a
positive value for data sets consisting of a single value.
Storing values specified as hexadecimal values 64 or more bits
UNSIGNED columns did not raise any warning or error if
the value was out of range.
SHOW COLUMNS reported some
NOT NULL columns as
Type conversion errors during formation of index search conditions were not correctly checked, leading to incorrect query results. (Bug #22344)
Changing the value of
myisam.h and recompiling MySQL resulted in
a myisamchk that saw existing
MyISAM tables as corrupt.
A crash of the MySQL Server could occur when unpacking a
BLOB column from a row in a
corrupted MyISAM table. This could happen when trying to repair
a table using either
or myisamchk; it could also happen when
trying to access such a “broken” row using
SELECT if the
table was not marked as crashed.
SSL connections could hang at connection shutdown. (Bug #21781, Bug #24148)
FEDERATED storage engine did not support
euckr character set.
When updating a table that used a
JOIN of the
table itself (for example, when building trees) and the table
was modified on one side of the expression, the table would
either be reported as crashed or the wrong rows in the table
would be updated.
mysqld_error.h was not installed when only
the client libraries were built.
InnoDB: During a restart of the MySQL Server
that followed the creation of a temporary table using the
InnoDB storage engine, MySQL failed to clean
up in such a way that
InnoDB still attempted
to find the files associated with such tables.
DEFAULT into a column with no
default value could result in garbage in the column. Now the
same result occurs as when inserting
NOT NULL column.
A stored routine containing semicolon in its body could not be reloaded from a dump of a binary log. (Bug #20396)
SELECT ... FOR
... LOCK IN SHARE MODE,
UPDATE statements executed using
a full table scan were not releasing locks on rows that did not
On Windows, if the server was installed as a service, it did not auto-detect the location of the data directory. (Bug #20376)
The BUILD/check-cpu script did not recognize Celeron processors. (Bug #20061)
If a duplicate key value was present in the table,
ON DUPLICATE KEY UPDATE reported a row count
indicating that a record was updated, even when no record
actually changed due to the old and new values being the same.
Now it reports a row count of zero.
References: See also Bug #27006, Bug #27033, Bug #27210.
readline library wrote to uninitialized
memory, causing mysql to crash.
mysqltest incorrectly tried to retrieve result sets for some queries where no result set was available. (Bug #19410)
Use of already freed memory caused SSL connections to hang forever. (Bug #19209)
CASE statements inside
stored routines could lead to excessive resource usage or a
crash of the server.
(Bug #19194, Bug #24854)
Instance Manager could crash during shutdown. (Bug #19044)
The server might fail to use an appropriate index for
LIMIT, and a nonrestricting
WHERE are present.
No warning was issued for use of the
INDEX DIRECTORY table
options on a platform that does not support them.
FEDERATED storage engine did not support
utf8 character set.
The optimizer removes expressions from
DISTINCT clauses if they
happen to participate in
WHERE clause, the idea being that, if the
expression is equal to a constant, then it cannot take on
multiple values. However, for predicates where the expression
and the constant item are of different result types (for
example, when a string column is compared to 0), this is not
valid, and can lead to invalid results in such cases. The
optimizer now performs an additional check of the result types
of the expression and the constant; if their types differ, then
the expression is not removed from the
When a prepared statement failed during the prepare operation, the error code was not cleared when it was reused, even if the subsequent use was successful. (Bug #15518)
Dropping a user-defined function sometimes did not remove the
UDF entry from the
Inserting a row into a table without specifying a value for a
column caused the column to be set to spaces, not zeros.
N) NOT NULL
On Windows, the
could sleep too long, especially after a change to the system
(Bug #14094, Bug #24686, Bug #17635)
mysqldump --order-by-primary failed if the primary key name was an identifier that required quoting. (Bug #13926)
To enable installation of MySQL RPMs on Linux systems running RHEL 4 (which includes SE-Linux) additional information was provided to specify some actions that are permitted to the MySQL binaries. (Bug #12676)
The presence of
ORDER BY in a view definition
MERGE algorithm from being used
to resolve the view even if nothing else in the definition
The internal functions for table preparation, creation, and
alteration were not re-execution friendly, causing problems in
code that: repeatedly altered a table; repeatedly created and
dropped a table; opened and closed a cursor on a table, altered
the table, and then reopened the cursor; used
ALTER TABLE to change a table's
AUTO_INCREMENT value; created indexes
CREATE TABLE, and
ALTER TABLE statements in stored
routines or as prepared statements also caused incorrect results
(Bug #4968, Bug #6895, Bug #19182, Bug #19733, Bug #22060, Bug #24879)