MySQL Community Server 5.1.71 has been released (no replies)

Dear MySQL users,

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

Enjoy!

Changes in MySQL 5.1.71 (2013-08-01)

   Functionality Added or Changed

     * comp_err now checks to make sure that new errors are not being
       added to MySQL 5.1 or 5.5 because the set of errors for these
       series is frozen. (Bug #16807394)

   Bugs Fixed

     * InnoDB: During an insert buffer merge, InnoDB would invoke
       lock_rec_restore_from_page_infimum() on a potentially invalid
       record pointer. (Bug #16806366)

     * InnoDB: The page_zip_validate() consistency check would fail
       after compressing a page, in page_zip_compress(). This problem
       was caused by page_zip_decompress(), which would fail to set
       heap_no correctly when a record contained no user data bytes.
       A record with no user data bytes occurs when, for example, a
       primary key is an empty string and all secondary index fields
       are NULL or an empty string. (Bug #16736929)

     * InnoDB: The pthread_mutex, commit_threads_m, which was
       initialized but never used, has been removed from the code
       base. (Bug #11829813)

     * Partitioning: When dropping a partitioned table, the table's
       .par file was deleted first, before the table definition or
       data. This meant that, if the server failed during the drop
       operation, the table could be left in an inconsistent state in
       which it could neither be accessed nor dropped.
       The fix for this problem makes the following changes:

          + Now, when dropping a partitioned table, the table's .par
            file is not removed until all table data has been
            deleted.

          + When executing DROP TABLE of a partitioned table, in the
            event that its .par file is determined to be missing, the
            table's .frm file is now immediately deleted, in effect
            forcing the drop to complete.
       (Bug #13548704, Bug #63884)

     * Shared-compatibility conflict errors occurred for RPM install
       operations, even if no shared-compatibility RPMs were already
       installed. (Bug #16678122)

     * A user variable referenced during execution of a prepared
       statement is set to memory that is freed at the end of
       execution. A second execution of the statement could result in
       Valgrind warnings when accessing this memory. (Bug #16119355)

     * Misoptimization of left expressions in prepared statements
       could cause a server exit. (Bug #16095534)

     * Subsequent to Prepared statement needs to be re-prepared
       errors, inserts into DECIMAL columns caused a server exit.
       (Bug #12608543)

     * Assigning the result of a subquery to a user variable raised
       an assertion when the outer query included DISTINCT and GROUP
       BY. (Bug #57196, Bug #11764371)

On behalf of Oracle MySQL RE Team