Dear MySQL users,
MySQL Community Server 5.1.45, a new version of the popular Open
Source Database Management System, has been released. MySQL 5.1.45 is
recommended for use on production systems.
For an overview of what's new in MySQL 5.1, please see
For information on installing MySQL 5.1.45 on new servers or upgrading
to MySQL 5.1.45 from previous MySQL releases, please see
MySQL Server is available in source and binary form for a number of
platforms from our download pages at
Not all mirror sites may be up to date at this point in time, so if
you can't find this version on some mirror, please try again later or
choose another download site.
We welcome and appreciate your feedback, bug reports, bug fixes,
For information on open issues in MySQL 5.1, please see the errata
The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
C.1.1. Changes in MySQL 5.1.45
InnoDB Plugin Notes:
* This release includes InnoDB Plugin 1.0.6. This version is
considered of Release Candidate (RC) quality.
In this release, the InnoDB Plugin is included in source and
binary distributions, except RHEL3, RHEL4, SuSE 9 (x86,
x86_64, ia64), and generic Linux RPM packages. It also does
not work for FreeBSD 6 and HP-UX or for Linux on generic ia64.
Functionality added or changed:
* mysqltest has a new --max-connections option to set a higher
number of maximum allowed server connections than the default
128. This option can also be passed via mysql-test-run.pl.
* mysql-test-run.pl has a new --portbase option and a
corresponding MTR_PORT_BASE environment variable for setting
the port range, as an alternative to the existing
* mysql-test-run.pl has a new --gprof option that runs the
server through the gprof profiler, much the same way the
currently supported --gcov option runs it through gcov.
* mysqltest has a new lowercase_result command that converts the
output of the next statement to lowercase. This is useful for
test cases where the lettercase may vary between platforms.
* mysqltest has a new remove_files_wildcard command that removes
files matching a pattern from a directory.
* Partitioning: Attempting to drop a partitioned table from one
connection while waiting for the completion of an ALTER TABLE
that had been issued from a different connection, and that
changed the storage engine used by the table, could cause the
server to crash.
* Replication: Adding an index to a table on the master caused
the slave to stop logging slow queries to the slow query log.
* Replication: Queries which were written to the slow query log
on the master were not written to the slow query log on the
slave. (Bug#23300: http://bugs.mysql.com/bug.php?id=23300)
See also Bug#48632: http://bugs.mysql.com/bug.php?id=48632.
* mysqld_multi failed due to a syntax error in the script.
* Referring to a subquery result in a HAVING clause could
produce incorrect results.
* Use of filesort plus the join cache normally is preferred to a
full index scan. But it was used even if the index is
clustered, in which case, the clustered index scan can be
faster. (Bug#50843: http://bugs.mysql.com/bug.php?id=50843)
* For debug builds, SHOW BINARY LOGS caused an assertion to be
raised if binary logging was not enabled.
* Incorrect handling of BIT columns in temporary tables could
lead to spurious duplicate-key errors.
* Full-text queries that used the truncation operator (*) could
enter an infinite loop.
* mysqltest no longer lets you execute an SQL statement on a
connection after doing a send command, unless you do a reap
first. This was previously accepted but could produce
* For debug builds on Windows, warnings about incorrect use of
debugging directives were written to the error log. The
directives were rewritten to eliminate these messages.
* Building MySQL on Fedora Core 12 64-bit failed, due to errors
* An ARZ file missing from the database directory caused the
server to crash.
* Slow CALL statements were not always logged to the slow query
log because execution time for multiple-statement stored
procedures was assessed incorrectly.
* Failure to open a view with a nonexistent DEFINER was
improperly handled and the server would crash later attempting
to lock the view.
* If EXPLAIN encountered an error in the query, a memory leak
occurred. (Bug#45989: http://bugs.mysql.com/bug.php?id=45989)
* Grouping by a subquery in a query with a DISTINCT aggregate
function led to incorrect and unordered grouping values.
* Propagation of a large unsigned numeric constant in WHERE
expressions could lead to incorrect results. This also
affected EXPLAIN EXTENDED, which printed incorrect numeric
constants in such transformed WHERE expressions.
* Valgrind warnings about uninitialized variables in optimizer
code were silenced.
* flush_cache_records() did not correctly check for errors that
should cause statement execution to stop, leading to a server
crash. (Bug#39022: http://bugs.mysql.com/bug.php?id=39022)
* When building MySQL when using a different target directory
(for example using the VPATH environment variable), the build
of the embedded readline component would fail.
* INSERT INTO ... VALUES(DEFAULT) failed to insert the correct
value for ENUM columns. For MyISAM tables, an empty value was
inserted. For CSV tables, the table became corrupt.
MySQL RE Team
Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.
|• MySQL Community Server 5.1.45 has been released||Karen Langford||17 Mar|