Dear MySQL users,

MySQL Server 5.1.73, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.73 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.73 on new servers or upgrading
to MySQL 5.1.73 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

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.

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
online at

http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-73.html

Enjoy!

Changes in MySQL 5.1.73 (December 03, 2013)

Packaging Notes

* Previously, MySQL Server distributions included the MySQL
Reference Manual in Info format (the Docs/mysql.info file).
Because the license for the manual restricts redistribution,
its inclusion in Community packages caused problems for
downstream redistributors, such as those who create Linux
distributions. Community distributions of MySQL Server no
longer include the mysql.info file, to make the repackaging
and redistribution process easier (for example, the source
tarball and its checksum can be used directly). This change
applies to all source and binary Community packaging formats.
Commercial (Enterprise) distributions are unchanged.
For Those who wish to continue using the MySQL Reference
Manual in Info format, we have made it available at
http://dev.mysql.com/doc/.

Bugs Fixed

* InnoDB: In debug builds, test case failures would occur due to
ibuf_contract_ext performing merges and dict_stats_update
returning evicted pages back into the buffer pool while
ibuf_change_buffering_debug is enabled. (Bug #17446090)

* InnoDB: InnoDB would fail to return an error when attempting
to run a query after discarding the tablespace. (Bug
#17431533)

* InnoDB: When the change buffer is enabled, InnoDB would fail
to write a transaction log record when merging a record from
the insert buffer to a secondary index page if the insert was
performed as an "update-in-place". (Bug #16752251, Bug #69122)

* Partitioning: The storage engine was set incorrectly during a
rebuild of a partition; the table storage engine was ignored
and the default storage engine used instead. Thus, in MySQL
5.1, it was possible for REBUILD PARTITION to change the
partition storage engine from InnoDB to MyISAM, and for the
reverse (rebuilding partitions of MyISAM tables causing the
partitions to use InnoDB) to occurin MySQL 5.5 and later. Now,
when rebuilding partitions, the storage engine actually used
by the table is checked and used by the handler for the
rebuild operation, so that the partition storage engine is not
inadvertently changed. (Bug #17559867)

* Replication: When an error encountered by the dump thread
while reading events from the active binary log file was a
temporary error, so that the dump thread tried to read the
event, it was possible for the dump thread to seek the wrong
position, which could cause one or more events to be resent.
To prevent this, the thread's position is obtained after each
correct read of an event.
In addition, with this fix, only binary logs that are not
closed normally are marked as possibly being corrupted.
Finally, two warnings are added; these are now returned when a
dump thread encounters a temporary error. (Bug #17402313)

* Replication: The value of LAST_INSERT_ID() was not correctly
replicated when filtering rules were used on the slave. (Bug
#17234370, Bug #69861)

* Enabling Index Merge optimizer switches and setting a small
sort_buffer_size value could lead to a server exit. (Bug
#17617945)

* The mysql_options() C API function could leak memory if called
more than once with the MYSQL_SET_CLIENT_IP option. (Bug
#17297012)

* An error array in the SSL code was missing a comma, leading to
implicit concatenation of adjacent messages and a resulting
off-by-one error in the relationship between error numbers and
messages. (Bug #17294150)

* The filesort implementation sometimes failed to allocate
enough buffer space, leading to a server exit. (Bug #17326567)

* Very long database names in queries could cause the server to
exit. (Bug #15912213, Bug #16900358)

* The my_b_vprintf() function could produce incorrect results
for long integers on 64-bit systems. (Bug #67386, Bug
#16978278)

* Host names in grant tables are stored in lowercase, but
mysql_install_db could fail to observe this convention,
leading to accounts that could not be dropped with DROP USER.
(Bug #62255, Bug #12917164, Bug #62254, Bug #12917151)

On behalf of Oracle MySQL RE Team

Hery Ramilison

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql