Dear MySQL users,

MySQL Server 5.1.66, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.66 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.66 on new servers or upgrading
to MySQL 5.1.66 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/

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://dev.mysql.com/resources/Contributing.html

For information on open issues in MySQL 5.1, please see the errata
list at

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

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/refman/5.1/en/news-5-1-66.html <http://dev.mysql.com/doc/refman/5.1/en/news-5-1-65.html>

Enjoy!

==================================================================== A.1.1. Changes in MySQL 5.1.66 (September 29, 2012)

Bugs Fixed

* InnoDB: Certain information_schema tables originally
introduced in MySQL 5.6 are now also available in MySQL
5.5 and MySQL 5.1: INNODB_BUFFER_PAGE
(http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pag
e-table.html), INNODB_BUFFER_PAGE_LRU
(http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pag
e-lru-table.html), and INNODB_BUFFER_POOL_STATS
(http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-poo
l-stats-table.html). (Bug #13113026)

* InnoDB: When a SELECT ... FOR UPDATE, UPDATE, or other
SQL statement scanned rows in an InnoDB table using a <
or <= operator in a WHERE clause, the next row after the
affected range could also be locked. This issue could
cause a lock wait timeout for a row that was not expected
to be locked. The issue occurred under various isolation
levels, such as READ COMMITTED
(http://dev.mysql.com/doc/refman/5.1/en/set-transaction.h
tml#isolevel_read-committed) and REPEATABLE READ
(http://dev.mysql.com/doc/refman/5.1/en/set-transaction.h
tml#isolevel_repeatable-read). (Bug #11765218)

* Partitioning: The buffer for the row currently read from
each partition used for sorted reads was allocated on
open and freed only when the partitioning handler was
closed or destroyed. For SELECT statements on tables with
many partitions and large rows, this could cause the
server to use excessive amounts of memory.
This issue has been addressed by allocating buffers for
reads from partitioned tables only when they are needed
and freeing them immediately once they are no longer
needed. As part of this fix, memory is now allocated for
reading from rows only in partitions that have not been
pruned (see Partition Pruning
(http://dev.mysql.com/doc/refman/5.1/en/partitioning-prun
ing.html)). (Bug #13025132)
References: See also Bug #11764622, Bug #14537277.

* Replication: In master-master replication with
--log-slave-updates
(http://dev.mysql.com/doc/refman/5.1/en/replication-optio
ns-slave.html#option_mysqld_log-slave-updates) enabled,
setting a user variable and then performing inserts using
this variable caused the Exec_master_log_position column
in the output of SHOW SLAVE STATUS
(http://dev.mysql.com/doc/refman/5.1/en/show-slave-status
.html) not to be updated. (Bug #13596613)

* Small sort_buffer_size
(http://dev.mysql.com/doc/refman/5.1/en/server-system-var
iables.html#sysvar_sort_buffer_size) values could result
in a server crash. (Bug #14111180)

* The libmysqlclient_r client library exported symbols from
yaSSL that conflict with OpenSSL. If a program linked
against that library and libcurl, it could crash with a
segmentation fault. (Bug #14068244)

* The argument for LIMIT must be an integer, but if the
argument was given by a placeholder in a prepared
statement, the server did not reject noninteger values
such as '5'. (Bug #13868860)

* Access to INFORMATION_SCHEMA tables through a view could
leak memory. (Bug #13734987)

* A query for a FEDERATED
(http://dev.mysql.com/doc/refman/5.1/en/federated-storage
-engine.html) table could return incorrect results when
the underlying table had a compound index on two columns
and the query included an AND condition on the columns.
(Bug #12876932)

* The argument to the --ssl-key
(http://dev.mysql.com/doc/refman/5.1/en/ssl-options.html#
option_general_ssl-key) option was not verified to exist
and be a valid key. The resulting connection used SSL,
but the key was not used. (Bug #62743, Bug #13115401)

* In debug builds, an InnoDB
(http://dev.mysql.com/doc/refman/5.1/en/innodb-storage-en
gine.html) assertion was overly aggressive about
prohibiting an open range. (Bug #66513, Bug #14547952)

* Adding a LIMIT clause to a query containing GROUP BY and
ORDER BY could cause the optimizer to choose an incorrect
index for processing the query, and return more rows than
required. (Bug #54599, Bug #11762052)

* mysqlbinlog did not accept input on the standard input
when the standard input was a pipe. (Bug #49336, Bug
#11757312)

Thanks,
On Behalf of Oracle MySQL RE Team

Akhil Mohan
MySQL Release Engineer