Log Message:
Changes 5.1.71:

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.

Bugs Fixed
* InnoDB: During an insert buffer merge, InnoDB would invoke \ 
lock_rec_restore_from_page_infimum() on a potentially invalid record pointer.
* 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.
* InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never \ 
used, has been removed from the code base.
* 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.
* Shared-compatibility conflict errors occurred for RPM install operations, even \ 
if no shared-compatibility RPMs were already installed.
* 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.
* Misoptimization of left expressions in prepared statements could cause a \ 
server exit.
* Subsequent to Prepared statement needs to be re-prepared errors, inserts into \ 
DECIMAL columns caused a server exit.
* Assigning the result of a subquery to a user variable raised an assertion when \ 
the outer query included DISTINCT and GROUP BY.