Log Message:
Changes 5.6.16:
Functionality Added or Changed
* InnoDB: New global configuration parameters, innodb_status_output and \ 
innodb_status_output_locks, allow you to dynamically enable and disable the \ 
standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling \ 
and disabling monitors for periodic output by creating and dropping specially \ 
named tables is deprecated and may be removed in a future release.
* Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result \ 
had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old \ 
temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD \ 
INDEX, and FORCE operations. This conversion cannot be done using the INPLACE \ 
algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error.
* CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir \ 
value. If unspecified, the value defaults to P_tmpdir in <stdio.h>.

Bugs Fixed
* InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration \ 
with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak \ 
memory.
* InnoDB: A boolean mode full-text search query would result in a memory access \ 
violation during parsing.
* InnoDB: When new indexes are added by an ALTER TABLE operation, instead of \ 
only saving table-level statistics and statistics for the new indexes, InnoDB \ 
would save statistics for the entire table, including the table's other indexes. \ 
This behavior slowed ALTER TABLE performance.
* InnoDB: Due to a parser error, full-text search queries that include a \ 
sub-expression could return the wrong result.
* InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve \ 
file size information, which resulted in an incorrect error message (Error: \ 
ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was \ 
exceeded. innochecksum now provides support for files larger than 2GB in both \ 
MySQL 5.6 and MySQL 5.7.
* InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was \ 
not allocated for the default memcached engine when using the default memcached \ 
engine as the backstore for data instead of InnoDB.
* InnoDB: InnoDB would report an incorrect operating system error code after \ 
failing to initialize.
* InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE \ 
... DISCARD TABLESPACE could result in a serious error.
* InnoDB: Persistent optimizer statistics would cause stalls due to latch contention.
* InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for \ 
AGAINST() could result in an error when run on an InnoDB table with a full-text \ 
search index.
* InnoDB: An InnoDB full-text search failure would occur due to an \ 
“unended” token. The string and string length should be passed for \ 
string comparison.
* InnoDB: In debug builds, a merge insert buffer during a page read would cause \ 
a memory access violation.
* InnoDB: Truncating a memcached InnoDB table while memcached is performing DML \ 
operations would result in a serious error.
* InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call \ 
os_thread_get_curr_id.
* InnoDB: Attempting to rename a table to a missing database would result in a \ 
serious error.
more...