This is a bugfix release for the current MySQL Community Server production release family. It replaces MySQL 5.0.51b.
Functionality Added or Changed
To enable stricter control over the location from which
user-defined functions can be loaded, the
plugin_dir system variable has
been backported from MySQL 5.1. If the value is nonempty,
user-defined function object files can be loaded only from the
directory named by this variable. If the value is empty, the
behavior that is used prior to the inclusion of
plugin_dir applies: The UDF
object files must be located in a directory that is searched by
your system's dynamic linker.
If the plugin directory is writable by the server, it may be
possible for a user to write executable code to a file in the
... INTO DUMPFILE. This can be prevented by making
plugin_dir read only to the
server or by setting
--secure-file-priv to a directory
SELECT writes can be made
Incompatible Change; Important Change:
FEDERATED storage engine is now disabled
by default in the
.cnf files shipped with
MySQL distributions (
my-medium.cnf, and so forth). This affects
server behavior only if you install one of these files.
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
Some changes were made to
CHECK TABLE ... FOR
TABLE with respect to detection and handling of tables
.frm files (files created
with a different version of the MySQL server). These changes
also affect mysqlcheck because that program
CHECK TABLE and
REPAIR TABLE, and thus also
mysql_upgrade because that program invokes
If your table was created by a different version of the
MySQL server than the one you are currently running,
CHECK TABLE ...
FOR UPGRADE indicates that the table has an
.frm file with an incompatible version.
In this case, the result set returned by
CHECK TABLE contains a line
Msg_type value of
error and a
Table upgrade required. Please do "REPAIR
tbl_name`" to fix
REPAIR TABLE without
USE_FRM upgrades the
.frm file to the current version.
If you use
REPAIR TABLE ...USE_FRM and
your table was created by a different version of the MySQL
server than the one you are currently running,
REPAIR TABLE will not attempt
to repair the table. In this case, the result set returned
REPAIR TABLE contains a
line with a
Msg_type value of
error and a
Failed repairing incompatible .FRM
Previously, use of
...USE_FRM with a table created by a different
version of the MySQL server risked the loss of all rows in
mysqld and other binaries now are compiled
with debugging symbols included to enable easier use with a
debugger. If you do not need debugging symbols and are short on
disk space, you can use strip to remove the
symbols from the binaries.
The ndbd and ndb_mgmd man pages have been reclassified from volume 1 to volume 8. (Bug #34642)
mysql-test-run.pl now supports
--client-libdir options for specifying the
directory where client binaries and libraries are located.
mysql_upgrade now has a
--tmpdir option to enable
the location of temporary files to be specified.
mysqltest now has
rmdir commands for creating and removing
The default value of the
connect_timeout system variable
was increased from 5 to 10 seconds. This might help in cases
where clients frequently encounter errors of the form
Lost connection to MySQL server at
XXX', system error:
mysqldump produces a
completed on comment
at the end of the dump if
--comments is given. The date
causes dump files for identical data take at different times to
appear to be different. The new options
control whether the date is added to the comment.
suppresses date printing. The default is
--dump-date (include the date
in the comment).
mysql_odbc_escape_string() C API
function has been removed. It has multi-byte character escaping
issues, doesn't honor the
NO_BACKSLASH_ESCAPES SQL mode
and is not needed anymore by Connector/ODBC as of 3.51.17.
References: See also Bug #41728.
The argument for the mysql-test-run.pl
options is now interpreted as a Perl regular expression if there
is a pattern metacharacter in the argument value. This enables
more flexible specification of which tests to perform or skip.
Security Fix; Important Change:
It was possible to circumvent privileges through the creation of
MyISAM tables employing the
options to overwrite existing table files in the MySQL data
directory. Use of the MySQL data directory in
INDEX DIRECTORY path
name is no longer permitted.
Additional fixes were made in MySQL 5.0.70.
(Bug #32167, CVE-2008-2079)
References: See also Bug #39277.
Security Fix: Three vulnerabilities in yaSSL versions 1.7.5 and earlier were discovered that could lead to a server crash or execution of unauthorized code. The exploit requires a server with yaSSL enabled and TCP/IP connections enabled, but does not require valid MySQL account credentials. The exploit does not apply to OpenSSL.
The proof-of-concept exploit is freely available on the Internet. Everyone with a vulnerable MySQL configuration is advised to upgrade immediately.
(Bug #33814, CVE-2008-0226, CVE-2008-0227)
RENAME TABLE against a
table with explicit
DATA DIRECTORY and
INDEX DIRECTORY options can be used to
overwrite system table information by replacing the symbolic
link points. the file to which the symlink points.
MySQL will now return an error when the file to which the symlink points already exists. (Bug #32111, CVE-2007-5969)
When using a
FEDERATED table, the local
server could be forced to crash if the remote server returned a
result with fewer columns than expected.
ALTER VIEW retained the original
DEFINER value, even when altered by another
user, which could enable that user to gain the access rights of
the view. Now
ALTER VIEW is
permitted only to the original definer or users with the
Security Enhancement: It was possible to force an error message of excessive length which could lead to a buffer overflow. This has been made no longer possible as a security precaution. (Bug #32707)
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.
InnoDB had a race condition for an adaptive
hash rw-lock waiting for an X-lock. This fix may also provide
significant speed improvements on systems experiencing problems
with contention for the adaptive hash index.
It was possible to use
FRAC_SECOND as a
INTERVAL; now, using
FRAC_SECOND with anything other than
TIMESTAMPDIFF() produces a syntax
Incompatible Change: It was possible for option files to be read twice at program startup, if some of the standard option file locations turned out to be the same directory. Now duplicates are removed from the list of files to be read.
Also, users could not override system-wide settings using
was read last. The latter file now is read earlier so that
~/.my.cnf can override system-wide
The fix for this problem had a side effect such that on Unix,
MySQL programs looked for options in
~/my.cnf rather than the standard location
~/.my.cnf. That problem was addressed as
Incompatible Change: It was possible to create a view having a column whose name consisted of an empty string or space characters only.
One result of this bug fix is that aliases for columns in the
SELECT statement are checked to ensure
that they are legal column names. In particular, the length must
be within the maximum column length of 64 characters, not the
maximum alias length of 256 characters. This can cause problems
for replication or loading dump files. For additional
information and workarounds, see
Restrictions on Views.
References: See also Bug #31202.
Several type-preserving functions and operators returned an
incorrect result type that does not match their argument types:
CASE. These now aggregate using the
precise SQL types of their arguments rather than the internal
type. In addition, the result type of the
STR_TO_DATE() function is now
DATETIME by default.
mode enabled, queries such as
SELECT a FROM t1 HAVING
COUNT(*)>2 were not being rejected as they should
This fix results in the following behavior:
There is a check against mixing group and nongroup columns
This check is done both for the select list and for the
HAVING clause if there is one.
This behavior differs from previous versions as follows:
Incompatible Change: The MySQL 5.0.50 patch for this bug was reverted because it changed the behavior of a General Availability MySQL release. (Bug #30234)
References: See also Bug #27525.
Important Change; MySQL Cluster:
AUTO_INCREMENT columns had the following
problems when used in
AUTO_INCREMENT counter was not
updated correctly when such a column was updated.
AUTO_INCREMENT values were not
prefetched beyond statement boundaries.
AUTO_INCREMENT values were not handled
After being set,
showed a value of 1, regardless of the value it had
actually been set to.
As part of this fix, the behavior of
has changed. Setting this to less than 32 no longer has any
effect on prefetching within statements (where IDs are now
always obtained in batches of 32 or more), but only between
statements. The default value for this variable has also
changed, and is now
(Bug #25176, Bug #31956, Bug #32055)
Important Change; Replication:
When the master crashed during an update on a transactional
table while in
the slave failed. This fix causes every transaction (including
autocommit transactions) to be
recorded in the binary log as starting with a
ending with a
The current fix does not cause
nontransactional changes to be wrapped in
when written to the binary log. For this purpose, any
statements affecting tables using a nontransactional storage
engine such as
regarded as nontransactional, even when
autocommit is enabled.
References: See also Bug #29288, Bug #49522.
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.
The server no longer issues warnings for truncation of excess
spaces for values inserted into
CHAR columns. This reverts a
change in the previous release that caused warnings to be
Important Note; Replication: Network timeouts between the master and the slave could result in corruption of the relay log. This fix rectifies a long-standing replication issue when using unreliable networks, including replication over wide area networks such as the Internet. If you experience reliability issues and see many You have an error in your SQL syntax errors on replication slaves, we strongly recommend that you upgrade to a MySQL version which includes this fix. (Bug #26489)
MySQL Cluster: Incorrectly handled parameters could lead to a crash in the Transaction Coordinator during a node failure, causing other data nodes to fail. (Bug #33168)
An improperly reset internal signal was observed as a hang when
using events in the
NDB API but
could result in various errors.
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: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug #32160)
When inserting a row into an
table with a duplicate value for a nonprimary unique key, the
error issued would reference the wrong key.
This improves on an initial fix for this issue made in MySQL 5.0.30 and MySQL 5.0.33 (Bug #21072)
Primary keys on variable-length columns (such as
VARCHAR) did not work correctly.
NDBCLUSTER test failures
occurred in builds compiled using icc on IA64
MySQL Cluster: Transaction atomicity was sometimes not preserved between reads and inserts under high loads. (Bug #31477)
MySQL Cluster: Having tables with a great many columns could cause Cluster backups to fail. (Bug #30172)
It was possible in
config.ini to define
cluster nodes having node IDs greater than the maximum permitted
ON DUPLICATE KEY UPDATE concurrently with or following
TRUNCATE TABLE statement on an
NDB table failed with
NDB error 4350
Transaction already aborted.
An uninitialized variable in the
NDB storage engine code led to
AUTO_INCREMENT failures when the server was
compiled with gcc 4.2.1.
References: This bug was introduced by Bug #27437.
NDB storage engine code was not
safe for strict-alias optimization in gcc
UPDATE IGNORE could sometimes fail on
NDB tables due to the use of
unitialized data when checking for duplicate keys to be ignored.
An error with an
if statement in
sql/ha_ndbcluster.cc could potentially lead
to an infinite loop in case of failure when working with
AUTO_INCREMENT columns in
MySQL Cluster: An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug #29390)
MySQL Cluster: Transaction timeouts were not handled well in some circumstances, leading to excessive number of transactions being aborted unnecessarily. (Bug #30379)
MySQL Cluster: In some cases, the cluster managment server logged entries multiple times following a restart of ndb_mgmd. (Bug #29565)
When a stored routine or trigger, running on a master that used
MySQL 5.0 or MySQL 5.1.11 or earlier, performed an insert on an
AUTO_INCREMENT column, the
insert_id value was not
replicated correctly to a slave running MySQL 5.1.12 or later
(including any MySQL 6.0 release).
References: See also Bug #19630.
insert_id was not written to
the binary log for inserts into
Replication: The character sets and collations used for constant identifiers in stored procedures were not replicated correctly. (Bug #34289)
statement was written to the binary log by a connection that did
not use any transactional tables.
DROP USER, or
RENAME USER statement that fails
on the master, or that is a duplicate of any of these
statements, is no longer written to the binlog; previously,
either of these occurrences could cause the slave to fail.
References: See also Bug #29749.
Replication: Some kinds of internal errors, such as Out of memory errors, could cause the server to crash when replicating statements with user variables.
certain internal errors. (Bug #37150)
References: See also Bug #32575.
PURGE BINARY LOGS TO and
BINARY LOGS BEFORE did not handle missing binary log
files correctly or in the same way. Now for both of these
statements, if any files listed in the
.index file are missing from the file
system, the statement fails with an error.
(Bug #18199, Bug #18453)
START SLAVE UNTIL
issued on a slave that was using
--log-slave-updates and that was
involved in circular replication would cause the slave to run
and stop one event later than that specified by the value of
The nonspecific error message Wrong parameters to
function register_slave resulted when
START SLAVE failed to register on
the master due to excess length of any the slave server options
--report-password. An error
message specific to each of these options is now returned in
such cases. The new error messages are:
Failed to register slave: too long 'report-host'
Failed to register slave: too long 'report-user'
Failed to register slave; too long 'report-password'
References: See also Bug #19328.
MASTER_POS_WAIT() did not return
NULL when the server was not a slave.
STOP SLAVE did not stop
connection attempts properly. If the I/O slave thread was
attempting to connect,
waited for the attempt to finish, sometimes for a long period of
time, rather than stopping the slave immediately.
References: See also Bug #30932.
server_id did not
update its value for the current session.
SQL statements containing comments using
syntax were not replayable by mysqlbinlog,
even though such statements replicated correctly.
DROP VIEW statement
caused replication to fail if the view did not actually exist.
Use of the
@@hostname system variable in
not replicate. The workaround is to select its value into a user
variable (which does replicate) and insert that.
SHOW SLAVE STATUS as
mysqld was shutting down could cause a crash.
UPDATE statement using a
stored function that modified a nontransactional table was not
logged if it failed. This caused the copy of the
nontransactional table on the master have a row that the copy on
the slave did not.
In addition, when an
ON DUPLICATE KEY UPDATE statement encountered a
duplicate key constraint, but the
UPDATE did not actually change
any data, the statement was not logged. As a result of this fix,
such statements are now treated the same for logging purposes as
UPDATE statements, and so
are written to the binary log.
References: See also Bug #12713.
Replication: It was possible for the name of the relay log file to exceed the amount of memory reserved for it, possibly leading to a crash of the server. (Bug #31836)
References: See also Bug #28597.
Replication: One thread could read uninitialized memory from the stack of another thread. This issue was only known to occur in a mysqld process acting as both a master and a slave. (Bug #30752)
Replication: Due a previous change in how the default name and location of the binary log file were determined, replication failed following some upgrades. (Bug #28597, Bug #28603)
References: See also Bug #31836. This bug was introduced by Bug #20166.
Stored procedures having
parameters were not replicated correctly.
A replication slave sometimes failed to reconnect because it was
unable to run
SHOW SLAVE HOSTS.
It was not necessary to run this statement on slaves (since the
master should track connection IDs), and the execution of this
statement by slaves was removed.
References: See also Bug #13963, Bug #21869.
Replication: Corruption of log events caused the server to crash on 64-bit Linux systems having 4 GB or more of memory. (Bug #31793)
CREATE VIEW statements containing
extended comments were not written to the binary log correctly,
causing parse errors on the slave. Now, all comments are
stripped from such statements before being written to the binary
References: See also Bug #36570.
When reading a
BIT(64) value using
bytes were written to the buffer rather than the expected 8
The fix for Bug #33812 had the side effect of causing the mysql client not to be able to read some dump files produced with mysqldump. To address this, that fix was reverted. (Bug #38158)
The server was built even when configure was
run with the
References: See also Bug #23973.
mysql_install_db failed if the server was
running with an SQL mode of
TRADITIONAL. This program now
resets the SQL mode internally to avoid this problem.
When a view containing a reference to
was created, the reference was removed when the definition was
stored, causing some queries against the view to fail with
invalid SQL syntax errors.
mysqldump failed to return an error code when
without binary logging being enabled on the server.
A malformed URL used for a
CONNECTION option value in a
CREATE TABLE statement was not
handled correctly and could crash the server.
statement on a table having both a foreign key reference and a
DELETE trigger crashed the server.
A query using
col1 used a binary collation and
string2 except for case, failed to
match any records even when matches were found by a query using
the equivalent clause
Reuse of prepared statements could cause a memory leak in the embedded server. (Bug #33796)
In some cases a query that produced a result set when using
ORDER BY ASC did not return any results when
this was changed to
ORDER BY DESC.
NAME_CONST() with a negative number and
an aggregate function caused MySQL to crash. This could also
have a negative impact on replication.
Under some circumstances a combination of aggregate functions
GROUP BY in a
SELECT query over a view could
lead to incorrect calculation of the result type of the
aggregate function. This in turn could lead to incorrect
results, or to crashes on debug builds of the server.
A query that performed a
ref_or_null join where the
second table used a key having one or columns that could be
NULL and had a column value that was
NULL caused the server to crash.
References: This bug was introduced by Bug #12144.
Some subqueries using an expression that included an aggregate function could fail or in some cases lead to a crash of the server. (Bug #34620)
Under some conditions, a
innodb_autoextend_increment statement could fail.
References: This bug is a regression of Bug #31177.
Some queries using a combination of
CONCAT(), and an implicit type
conversion could return an incorrect result.
DISTINCT queries, MySQL 4.0 and 4.1
stopped reading joined tables as soon as the first matching row
was found. However, this optimization was lost in MySQL 5.0,
which instead read all matching rows. This fix for this
regression may result in a major improvement in performance for
DISTINCT queries in cases where many rows
Certain combinations of views, subselects with outer references and stored routines or triggers could cause the server to crash. (Bug #33389)
UPDATE privilege on
one column of a view caused the server to crash.
Disabling concurrent inserts caused some cacheable queries not to be saved in the query cache. (Bug #33756)
SLEEP(0) failed to return on
64-bit Mac OS X due to a bug in
For an indexed integer column
col_name and a value
N that is one greater than the
maximum value permitted for the data type of
col_name, conditions of the form
WHERE failed to return rows
where the value of
N - 1
INFILE with a view could crash the server.
Under some circumstances, the value of
mysql_insert_id() following a
SELECT ... INSERT statement could return an
incorrect value. This could happen when the last
... INSERT did not involve an
AUTO_INCREMENT column, but the value of
mysql_insert_id() was changed by
some previous statements.
A memory-handling error associated with use of
GROUP_CONCAT() in subqueries
could result in a server crash.
Table and database names were mixed up in some places of the subquery transformation procedure. This could affect debugging trace output and further extensions of that procedure. (Bug #34830)
Queries such as
SELECT ROW(1, 2) IN (SELECT t1.a, 2)
FROM t1 GROUP BY t1.a (combining row constructors and
subqueries in the
FROM clause) could lead to
assertion failure or unexpected error messages.
Incorrect assertions could cause a server crash for
DELETE triggers for transactional tables.
There was a memory leak when connecting to a
FEDERATED table using a connection string
that had a host value of
localhost or omitted
the host and a port value of
0 or omitted the
FEDERATED table with an index on a
nullable column, accessing the table could crash a server,
return an incorrect result set, or return
(HY000): Got error 1430 from storage engine.
mysqldump attempts to set the
variable after connecting to the server. This failed for pre-4.1
servers that have no such variable, but
mysqldump did not account for this and 1)
failed to dump database contents; 2) failed to produce any error
message alerting the user to the problem.
Some binaries produced stack corruption messages due to being built with versions of bison older than 2.1. Builds are now created using bison 2.3. (Bug #34926)
On Windows, the installer attempted to use JScript to determine whether the target data directory already existed. On Windows Vista x64, this resulted in an error because the installer was attempting to run the JScript in a 32-bit engine, which wasn't registered on Vista. The installer no longer uses JScript but instead relies on a native WiX command. (Bug #36103)
Debugging symbols were missing for some executables in Windows binary distributions. (Bug #35104)
A server crash could occur if
INFORMATION_SCHEMA tables built in memory
were swapped out to disk during query execution.
SET GLOBAL myisam_max_sort_file_size=DEFAULT
to an incorrect value.
References: See also Bug #31177.
The fix for Bug #11230 and Bug #26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug #33057)
CREATE TABLE ...
SELECT created tables that for date columns used the
Field_date type instead of
The server crashed when executing a query that had a subquery
containing an equality X=Y where Y referred to a named select
list expression from the parent select. The server crashed when
trying to use the X=Y equality for
Use of uninitialized memory for
filesort in a
subquery caused a server crash.
The parser permitted control structures in compound statements to have mismatched beginning and ending labels. (Bug #33618)
The correct data type for a
resulting from a
UNION could be
determined incorrectly in some cases: 1) Not correctly inferred
NULL depending on the number of selects;
2) Not inferred correctly as
NULL if one
select used a subquery.
For queries containing
, there was a
limitation that the
col_list ORDER BY
DISTINCT columns had to
be the same as
ORDER BY columns. Incorrect
results could be returned if this was not true.
References: See also Bug #33402, Bug #30617.
UNION constructs cannot contain
INTO except in the final
SELECT. However, if a
UNION was used in a subquery and
INTO clause appeared in the top-level
query, the parser interpreted it as having appeared in the
UNION and raised an error.
could not be used as views due to incorrect column reference
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.
ALTER VIEW statement
on a table crashed the server.
Repeated creation and deletion of views within prepared statements could eventually crash the server. (Bug #32890)
References: See also Bug #34587.
Large unsigned integers were improperly handled for prepared statements, resulting in truncation or conversion to negative numbers. (Bug #33798)
mysql_explain_log concatenated multiple-line
statements, causing malformed results for statements that
contained SQL comments beginning with
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)
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)
mysqlbinlog left temporary files on the disk after shutdown, leading to the pollution of the temporary directory, which eventually caused mysqlbinlog to fail. This caused problems in testing and other situations where mysqlbinlog might be invoked many times in a relatively short period of time. (Bug #35543)
The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement.
The fix for this bug had the side effect of causing the problem reported in Bug #38158, so it was reverted in MySQL 5.0.67. (Bug #33812)
The code for detecting a byte order mark (BOM) caused mysql to crash for empty input. (Bug #35480)
An empty bit-string literal (
b'') caused a
server crash. Now the value is parsed as an empty bit value
(which is treated as an empty string in string context or 0 in
The mysql client failed to recognize comment
lines consisting of
-- followed by a newline.
Some binary distributions had a duplicate “-64bit” suffix in the file name. (Bug #37623)
that used a temporary table could fail to update all qualifying
rows or fail with a spurious duplicate-key error.
EXPLAIN EXTENDED, execution
of an uncorrelated
IN subquery caused a crash
if the subquery required a temporary table for its execution.
On Windows 64-bit systems, temporary variables of
long types were used to store
ulong values, causing key cache
initialization to receive distorted parameters. The effect was
values of 2GB or more caused memory exhaustion to due allocation
of too much memory.
The fix for Bug #20748 caused a problem such that on Unix, MySQL
programs looked for options in
rather than the standard location of
ORDER BY query using
NULL in the
WHERE clause did not
return correct results.
mysqltest ignored the value of
--tmpdir in one place.
Conversion of a
FLOAT ZEROFILL value to
string could cause a server crash if the value was
The server crashed inside
NOT IN subqueries
with an impossible
HAVING clause, such as
(SELECT ... FROM t1, t2, ... WHERE 0).
An error in calculation of the precision of zero-length items
NULL) caused a server crash for
queries that employed temporary tables.
Several additional configuration scripts in the
BUILD directory now are included in source
distributions. These may be useful for users who wish to build
MySQL from source. (See
Installing MySQL Using a Development Source Tree, for information
about what they do.)
SET GLOBAL debug='' resulted in a Valgrind
DbugParse(), which was reading
beyond the end of the control string.
The combination of
could crash the server when the right table is empty.
mysql-stress-test.pl and mysqld_multi.server.sh were missing from some binary distributions. (Bug #21023, Bug #25486)
The MySQL Instance Configuration Wizard would not permit you to choose a service name, even though the criteria for the service name were valid. The code that checks the name has been updated to support the correct criteria of any string less than 256 character and not containing either a forward or backward slash character. (Bug #27013)
LIKE on tables having indexed
CHAR columns using either of the
sets did not return correct results.
Queries testing numeric constants containing leading zeros
ZEROFILL columns were not evaluated
The server returned the error message Out of memory; restart server and try again when the actual problem was that the sort buffer was too small. Now an appropriate error message is returned in such cases. (Bug #31590)
If an alias was used to refer to the value returned by a stored function within a subselect, the outer select recognized the alias but failed to retrieve the value assigned to it in the subselect. (Bug #30787)
References: This bug is a regression of Bug #20777.
The SQL parser did not accept an empty
UNION=() clause. This meant that, when there
were no underlying tables specified for a
SHOW CREATE TABLE and
mysqldump both output statements that could
not be executed.
Now it is possible to execute a
statement with an empty
SHOW CREATE TABLE and
mysqldump do not output the
UNION=() clause if there are no underlying
tables specified for a
This also means it is now possible to remove the underlying
tables for a
MERGE table using
ALTER TABLE ...
utf8 was set as the connection character
SPACE() with a
non-Unicode column produced an error.
References: See also Bug #23637.
The mysql_config command would output
CFLAGS values that were incompatible with C++
for the HP-UX platform.
SET column whose definition specified 64
elements could not be updated using integer values.
On Mac OS X, mysqld did not react to
Control+C when run under gdb, even when run
SHOW COLUMNS on a
TEMPORARY table caused locking issues.
The client library had no way to return an error if no
connection had been established. This caused problems such as
silently if no
errmsg.sys file was
When sorting privilege table rows, the server treated escaped
wildcard characters (
\_) the same as unescaped wildcard characters
_), resulting in
incorrect row ordering.
For distributions compiled with the bundled
libedit library, there were difficulties
using the mysql client to enter input for
non-ASCII or multi-byte characters.
On Windows, for distributions built with debugging support, mysql could crash if the user typed Control+C. (Bug #26243)
ORDER BY clauses, mixing aggregate
functions and nongrouping columns is not permitted if the
ONLY_FULL_GROUP_BY SQL mode is
enabled. However, in some cases, no error was thrown because of
On Mac OS X, the StartupItem for MySQL did not work. (Bug #25008)
If an error occurred during file creation, the server sometimes did not remove the file, resulting in an unused file in the file system. (Bug #31781)
The MySQL header files contained some duplicate macro definitions that could cause compilation problems. (Bug #23839)
For Windows 64-bit builds, enabling shared-memory support caused client connections to fail. (Bug #24992)
On Windows, an error in
installation of source distributions to fail.
could display process entries with a
*** DEAD ***.
An orphaned PID file from a no-longer-running process could cause mysql.server to wait for that process to exit even though it does not exist. (Bug #30378)
Inserting strings with a common prefix into a table that used
ucs2 character set corrupted the table.
Binary logging for a stored procedure differed depending on whether or not execution occurred in a prepared statement. (Bug #30604)
MySQLInstanceConfig.exe did not save the
innodb_data_home_dir value to
my.ini file under certain
If a user installed MySQL Server and set a password for the
root user, and then uninstalled and
reinstalled MySQL Server to the same location, the user could
not use the MySQL Instance Config wizard to configure the server
because the uninstall operation left the previous data directory
intact. The config wizard assumed that any
new install (not an upgrade) would have the default data
directory where the
root user has no
password. The installer now writes a registry key named
FoundExistingDataDir. If the installer finds
an existing data directory, the key will have a value of 1,
otherwise it will have a value of 0. When
MySQLInstanceConfig.exe is run, it will
attempt to read the key. If it can read the key, and the value
is 1 and there is no existing instance of the server (indicating
a new installation), the Config Wizard will permit the user to
input the old password so the server can be configured.
Using mysqldump in MySQL 5.1 resulted in dump
files that could not be loaded in MySQL 5.0 because
options in index definitions appeared after the index column
list, whereas 5.0 accepted only the old syntax that has
USING before the column list. The parser in
5.0 now accepts
USING following the column
option, mysqlhotcopy now determines the slave
status information from the result of
SLAVE STATUS by using the
Exec_Master_Log_Pos values rather than the
Read_Master_Log_Pos values. This provides a
more accurate indication of slave execution relative to the
A data file required for the
ndb_restore_different_endian_data test case
was missing from binary distributions, causing the test to fail.
The data file now is included.
(Bug #31453, Bug #11747239)
Name resolution for correlated subqueries and
HAVING clauses failed to distinguish which of
two was being performed when there was a reference to an outer
aliased field. This could result in error messages about a
HAVING clause for queries that had no such
mysqlcheck -A -r did not correctly identify all tables that needed repairing. (Bug #25347)
resolveip failed to produce correct results for host names that begin with a digit. (Bug #27427)
For Windows Vista, MySQLInstanceConfig.exe did not include a proper manifest enabling it to run with administrative privileges. (Bug #22563)
References: See also Bug #24732.
Views were treated as insertable even if some base table columns with no default value were omitted from the view definition. (This is contrary to the condition for insertability that a view must contain all columns in the base table that do not have a default value.) (Bug #29477)
mysqldumpslow returned a confusing error message when no configuration file was found. (Bug #20455)
mysql-test-run.pl sometimes set up test scenarios in which the same port number was passed to multiple servers, causing one of them to be unable to start. (Bug #31880)
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)
mysql_config output did not include
-lmygcc on some platforms when it was needed.
SHOW STATUS caused a server crash
InnoDB had not been initialized.
The mysqld crash handler failed on Windows. (Bug #31745)
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)
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)
The MySQL preferences pane did not work to start or stop MySQL on Mac OS X 10.5 (Leopard). (Bug #28854)
DISABLE KEYS and
KEYS on a nonempty table would cause the size of the
index file for the table to grow considerable. This was because
DISABLE KEYS operation would only mark
the existing index, without deleting the index blocks. The
ENABLE KEYS operation would re-create the
index, adding new blocks, while the previous index blocks would
remain. Existing indexes are now dropped and recreated when the
ENABLE KEYS statement is executed.
Under some circumstances, a UDF initialization function could be passed incorrect argument lengths. (Bug #29804)
On Windows, the
implementation was incorrect.
On Windows, the
implementation was incorrect. One symptom was that invalidating
the query cache could cause a server crash.
DELETE statements that remove
rows based on an index read could fail to remove all matching
RENAME while tables were open for
HANDLER statements could
cause a server crash.
Clients were ignoring the TCP/IP port number specified as the
default port using the
Internal conversion routines could fail for several multi-byte
character sets (
sjis) for empty
strings or during evaluation of
(Bug #31069, Bug #31070)
Allocation of an insufficiently large group-by buffer following creation of a temporary table could lead to a server crash. (Bug #31249)
The fix for Bug #24989 introduced a problem such that a
NULL thread handler could be used during a
rollback operation. This problem is unlikely to be seen in
The parser confused user-defined function (UDF) and stored
function creation for
FUNCTION and required that there be a default database
when creating UDFs, although there is no such requirement.
(Bug #28318, Bug #29816)
--without-geometry option for
configure caused server compilation to fail.
Values for the
incorrectly were treated as values for the
MEMORY tables, lookups for
NULL values in
indexes could return incorrect results.
Versions of mysqldump from MySQL 4.1 or
higher tried to use
START TRANSACTION WITH CONSISTENT
SNAPSHOT if the
--master-data options were
given, even with servers older than 4.1 that do not support
CONVERT( would fail on invalid input, but processing
was not aborted for the
WHERE clause, leading
to a server crash.
mysql-test-run.pl tried to create files in a
directory where it could not be expected to have write
permission. mysqltest created
.reject files in a directory other than the
one where test results go.
comp_err created files with permissions such that they might be inaccessible during make install operations. (Bug #27789)
GROUP_CONCAT() could cause a
Values of types
ZEROFILL, were not zero-filled when converted to a
character representation in the C prepared statement API.
Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:
larger than 4GB are permitted on 64-bit platforms (except
Windows, for which large values are truncated to 4GB with a
MAKEDATE() incorrectly moved year
values in the 100 to 200 range into the 1970 to 2069 range.
(This is legitimate for 00 to 99, but three-digit years should
be used unchanged.)
The length of the result from
IFNULL() could be calculated
incorrectly because the sign of the result was not taken into
SELECT 1 REGEX NULL caused an assertion
failure for debug servers.
A buffer used when setting variables was not dimensioned to
accommodate the trailing
'\0' byte, so a
single-byte buffer overrun was possible.
A character set introducer followed by a hexadecimal or bit-value literal did not check its argument and could return an ill-formed result for invalid input. (Bug #30986)
CHAR( did not check its
argument and could return an ill-formed result for invalid
The result from
CHAR() did not add a leading 0x00 byte for input
strings with an odd number of bytes.
For a fatal error during a filesort in
find_all_keys(), the error was returned
without the necessary handler uninitialization, causing an
The result from
incorrectly assumed in some contexts to return a single-byte
After changing the SQL mode to a restrictive value that would make already inserted dates in a column be considered invalid, searches returned different results depending on whether the column was indexed. (Bug #28687)
SHOW VARIABLES did not display
relay_log_info_file system variables.
Selecting spatial types in a
UNION could cause a server crash.
The metadata in some
could be incorrect when a temporary table was used to evaluate a
The anonymous accounts were not being created during MySQL installation. (Bug #27692)
MyISAM tables could not exceed 4294967295
(232 – 1) rows on Windows.
INFORMATION_SCHEMA tables are intended
for internal use, but could be accessed by using
An assertion designed to detect a bug in the
ROLLUP implementation would incorrectly be
triggered when used in a subquery context with noncacheable
On Windows, mysql_upgrade created temporary
C:\ and did not clean them up.
MOD() function and the
% operator crashed the server for a divisor
less than 1 with a very long fractional part.
GROUP BY on an expression of the form
caused a server
crash due to incorrect calculation of number of decimals.
When invoked with constant arguments,
STR_TO_DATE() could use a cached
value for the format string and return incorrect results.
For a spatial column with a regular
SPATIAL) index, queries failed if the
optimizer tried to use the index.
NULL when used in an
BY that was evaluated using
filesort, a server crash could result.
When expanding a
* in a
NATURAL join, the
check for table access for both tables in the join was done
using only the grant information of the first table.
Setting certain values on a table using a spatial index could cause the server to crash. (Bug #30286)
Index hints specified in view definitions were ignored when using the view to select from the base table. (Bug #28702)
Views do not have indexes, so index hints do not apply. Use of index hints when selecting from a view is no longer permitted. (Bug #28701)
The mysqlbug script did not include the
correct values of
CXXFLAGS that were used to configure the
configure did not find
on some Linux platforms.
GROUP BY NULL WITH ROLLUP could cause a
References: See also Bug #32558.
mysql_change_user() C API
function was subject to buffer overflow.
DROP USER caused an increase in
Under some circumstances,
CREATE TABLE ...
SELECT could crash the server or incorrectly report
that the table row size was too large.
GeomFromText() function could
cause a server crash if the first argument was
NULL or the empty string.
nonconstant arguments triggered an assertion failure.
Nonconstant arguments are no longer permitted.
A column with malformed multi-byte characters could cause the full-text parser to go into an infinite loop. (Bug #31950)
The optimizer could ignore
ORDER BY in cases
when the result set is ordered by
resulting in rows being returned in incorrect order.
',' rather than an empty string when the
argument column contained only empty strings.
Under certain conditions, the presence of a
BY clause could cause an
clause to be ignored.
Full-text searches on
ucs2 columns caused a
server crash. (
FULLTEXT indexes on
ucs2 columns cannot be used, but it should be
possible to perform
IN BOOLEAN MODE searches
ucs2 columns without a crash.)
For an almost-full
MyISAM table, an insert
that failed could leave the table in a corrupt state.
The examined-rows count was not incremented for
variables were displayed by
VARIABLES but could not be accessed in expressions as
@@log_slow_queries. Also, attempting to set
produced an incorrect
Unknown system variable
message. Now these variables can be accessed in expressions and
attempting to set their values produces an error message that
the variable is read only.
HAVING could treat lettercase of table
aliases incorrectly if
Comparison results for
different from those for operators like
DATETIME-like values with
trailing extra characters such as
the values as
the other operators performed a binary-string comparison. Now
they all uniformly use a
comparison, but generate warnings for values with trailing
In debug builds, testing the result of an
NULL caused an assertion
User-defined functions are not loaded if the server is started
option, but the server did not properly handle this case and
issued an Out of memory error message
readline library has been updated to
version 5.2. This addresses issues in the
mysql client where history and editing within
the client would fail to work as expected.
SELECT ... INTO
OUTFILE, if the
ENCLOSED BY string
is empty and the
FIELDS TERMINATED BY string
started with a special character (one of
N), every occurrence
of the character within field values would be duplicated.
mysql stripped comments from statements sent
to the server. Now the
--skip-comments option can be
used to control whether to retain or strip comments. The default
(Bug #11230, Bug #26215)
A build problem introduced in MySQL 5.0.52 was resolved: The x86 32-bit Intel icc-compiled server binary had unwanted dependences on Intel icc runtime libraries. (Bug #32514)
The default grant tables on Windows contained information for
production.mysql.com, which should not
The rules for valid column names were being applied differently for base tables and views. (Bug #32496)
myisamchk --unpack could corrupt a table that when unpacked has static (fixed-length) row format. (Bug #31277)
When doing a
DELETE on a table
that involved a
MERGE tables and the
JOIN referred to the same table, the
operation could fail reporting
ERROR 1030 (HY000): Got
error 134 from storage engine. This was because scans
on the table contents would change because of rows that had
already been deleted.
Tables with a
GEOMETRY column could be marked
as corrupt if you added a non-
Many nested subqueries in a single query could led to excessive memory consumption and possibly a crash of the server. (Bug #31048)
Server variables could not be set to their current values on Linux platforms. (Bug #31177)
References: See also Bug #6958.
Repeated execution of a query containing a
CASE expression and numerous
OR relations could
crash the server. The root cause of the issue was determined to
be that the internal
SEL_ARG structure was
not properly initialized when created.
Memory corruption could occur due to large index map in
Range checked for each record status reported
SELECT. The problem was based in an incorrectly
calculated length of the buffer used to store a hexadecimal
representation of an index map, which could result in buffer
overrun and stack corruption under some circumstances.
Comparison of a
BIGINT NOT NULL column with a
constant arithmetic expression that evaluated to NULL mistakenly
caused the error Column '...' cannot be
null (error 1048).
ORDER BY query on a view created using a
FEDERATED table as a base table caused the
server to crash.
Referencing within a subquery an alias used in the
SELECT list of the outer query
was incorrectly permitted.
SELECT INTO OUTFILE with 8-bit
ENCLOSED BY characters led to corrupted data
when the data was reloaded using LOAD DATA INFILE. This was
SELECT INTO OUTFILE failed to escape
the 8-bit characters.
SELECT ... GROUP BY
with an assertion if the length of the
BIT column used for the
GROUP BY was not an integer multiple of 8.
A subquery using an
IS NULL check of a column
NOT NULL in a table used in the
FROM clause of the outer query produced an
When casting a string value to an integer, cases where the input
string contained a decimal point and was long enough to overrun
unsigned long long type were not handled
correctly. The position of the decimal point was not taken into
account which resulted in miscalculated numbers and incorrect
truncation to appropriate SQL data type limits.
Some queries using the
NAME_CONST() function failed to
return either a result or an error to the client, causing it to
hang. This was due to the fact that there was no check to insure
that both arguments to this function were constant expressions.
(Bug #27545, Bug #32559)
mysqld sometimes miscalculated the number of
digits required when storing a floating-point number in a
CHAR column. This caused the
value to be truncated, or (when using a debug build) caused the
server to crash.
References: See also Bug #12860.
If the expected precision of an arithmetic expression exceeded the maximum precision supported by MySQL, the precision of the result was reduced by an unpredictable or arbitrary amount, rather than to the maximum precision. In some cases, exceeding the maximum supported precision could also lead to a crash of the server. (Bug #24907)
The options available to the
TABLE statement were also permitted in
OPTIMIZE TABLE and
ANALYZE TABLE statements, but
caused corruption during their execution. These options were
never supported for these statements, and an error is now raised
if you try to apply these options to these statements.
REGEXP operations could cause a
server crash for character sets such as
Now the arguments are converted to
possible, to permit correct results to be produced if the
resulting strings contain only 8-bit characters.
On some 64-bit systems, inserting the largest negative value
BIGINT column resulted in
euc-kr characters having the
second byte in the ranges
[0x61..0x7A] were rejected.
InnoDB does not support
SPATIAL indexes, but could crash when asked
to handle one. Now an error is returned.
ssl-cipher values in option files were not
being read by
mysql-test-run.pl could not run
QUERY statements to target a connection running
SELECT SLEEP() could freeze the server.
FLUSH TABLES WITH
READ LOCK, the server failed to properly detect
write-locked tables when running with low-priority updates,
resulting in a crash or deadlock.
Use of a
BY expression in conjunction with
ROLLUP could cause a server crash.
References: See also Bug #31095.
For transactional tables, an error during a multiple-table
DELETE statement did not roll
back the statement.
NULL values in the value
CREATE TABLE LIKE was treated
libmysqld than by the
Assigning a 65,536-byte string to a
TEXT column (which can hold a
maximum of 65,535 bytes) resulted in truncation without a
warning. Now a truncation warning is generated.
Changing the SQL mode to cause dates with “zero”
parts to be considered invalid (such as
'1000-00-00') could result in indexed and
nonindexed searches returning different results for a column
that contained such dates.
ucs2 does not work as a client character set,
but attempts to use it as such were not rejected. Now
character_set_client cannot be
ucs2. This also affects statements
SET NAMES and
CREATE TABLE ... LIKE statement
that was waiting for a name lock caused a server crash. When the
statement was killed, the server attempted to release locks that
were not held.
The mysql client program now ignores Unicode byte order mark (BOM) characters at the beginning of input files. Previously, it read them and sent them to the server, resulting in a syntax error.
Presence of a BOM does not cause mysql to
change its default character set. To do that, invoke
mysql with an option such as
For comparisons of the form
the comparison is done using
DATETIME values, per the fix for
Bug #27590. However that fix caused any index on
date_col not to be used and
compromised performance. Now the index is used again.
The server crashed in the parser when running out of memory. Memory handling in the parser has been improved to gracefully return an error when out-of-memory conditions occur in the parser. (Bug #31153)
Within a subquery,
handled differently than at the top level, which could result in
incorrect results or a server crash.
(Bug #32036, Bug #32051)
Improper calculation of
expression results could lead to value truncation.
Use of the
cp932 character set with
CAST() in an
BY clause could cause a server crash.
Various test program cleanups were made: 1)
were removed. 2) bug25714 displays an error
message when invoked with incorrect arguments or the
--help option. 3)
mysql_client_test exits cleanly with a proper
Specifying a nonexistent column for an
INSERT DELAYED statement caused a
server crash rather than producing an error.
libmysqld to crash.
MySQL declares a
UNIQUE key as a
PRIMARY key if it doesn't have
NULL columns and is not a partial key, and
PRIMARY key must alway be the first key.
However, in some cases, a nonfirst key could be reported as
PRIMARY, leading to an assert failure by
InnoDB. This is fixed by correcting the key
The optimizer incorrectly optimized conditions out of the
WHERE clause in some queries involving
subqueries and indexed columns.
CREATE ... SELECT ... FROM, where the
resulting table contained indexes, adding
SQL_BUFFER_RESULT to the
SELECT part caused index
corruption in the table.
Denormalized double-precision numbers cannot be handled properly by old MIPS processors. For IRIX, this is now handled by enabling a mode to use a software workaround. (Bug #29085)
A race condition between killing a statement and the thread executing the statement could lead to a situation such that the binary log contained an event indicating that the statement was killed, whereas the statement actually executed to completion. (Bug #27571)
The optimizer made incorrect assumptions about the value of the
is_member value for user-defined functions,
sometimes resulting in incorrect ordering of UDF results.
BLACKHOLE tables caused 100%
CPU use due to locking problems.
If no automatically generated value is successfully inserted,
Zero-padding of exponent values was not the same across platforms. (Bug #12860)
transactional and nontransactional tables caused an assertion
init_time() library function
was renamed to
my_init_time() to avoid
conflicts with external libraries.
The parser used signed rather than unsigned values in some cases that caused legal lengths in column declarations to be rejected. (Bug #15776)