Log Message:
Changes 5.6.25:
Functionality Added or Changed
* MySQL Enterprise Firewall operates on parser states and does not work well \ 
together with the query cache, which circumvents the parser. MySQL Enterprise \ 
Firewall now checks whether the query cache is enabled. If so, it displays a \ 
message that the query cache must be disabled and does not load.

* my_print_defaults now masks passwords. To display passwords in cleartext, use \ 
the new --show option.

* MySQL distributions now include an innodb_stress suite of test cases. Thanks \ 
to Mark Callaghan for the contribution.

Bugs Fixed
* InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES \ 
table now shows the correct table creation time for partitioned InnoDB tables. \ 
The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the \ 
correct partition creation time for a partition of partitioned InnoDB tables.

The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a \ 
partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The \ 
UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a \ 
partition of a partitioned InnoDB table was last updated.

* InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions \ 
holding explicit locks.

* InnoDB: The strict_* forms of innodb_checksum_algorithm settings (strict_none, \ 
strict_innodb, and strict_crc32) caused the server to halt when a non-matching \ 
checksum was encountered, even though the non-matching checksum was valid. For \ 
example, with innodb_checksum_algorithm=strict_crc32, encountering a valid \ 
innodb checksum caused the server to halt. Instead of halting the server, a \ 
message is now printed to the error log and the page is accepted as valid if it \ 
matches an innodb, crc32 or none checksum.

* InnoDB: The memcached set command permitted a negative expire time value. \ 
Expire time is stored internally as an unsigned integer. A negative value would \ 
be converted to a large number and accepted. The maximum expire time value is \ 
now restricted to INT_MAX32 to prevent negative expire time values.

* InnoDB: Removal of a foreign key object from the data dictionary cache during \ 
error handling caused the server to exit.

* InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and \ 
signal count values due to a counter overflow error.

* InnoDB: Failure to check the status of a cursor transaction read-only option \ 
before reusing the cursor transaction for a write operation resulted in a server \ 
exit during a memcached workload.

* InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup \ 
FLUSH TABLES WITH READ LOCK operation to hang.

* InnoDB: Estimates that were too low for the size of merge chunks in the result \ 
sorting algorithm caused a server exit.

* InnoDB: For full-text searches, the optimizer could choose an index that does \ 
not produce correct relevancy rankings.

* Partitioning: When creating a partitioned table, partition-level DATA \ 
DIRECTORY or INDEX DIRECTORY option values that contained an excessive number of \ 
characters were handled incorrectly.

* Partitioning: Executing an ALTER TABLE on a partitioned table on which a write \ 
lock was in effect could cause subsequent SQL statements on this table to fail.

* Replication: When binary logging was enabled, using stored functions and \ 
triggers resulting in a long running procedure that inserted many records caused \ 
the memory use to increase rapidly. This was due to memory being allocated per \ 
variable. The fix ensures that in such a situation, memory is allocated once and \ 
the same memory is reused.

* Replication: If an error was encountered while adding a GTID to the received \ 
GTID set, the log lock was not being correctly released. This could cause a \ 
deadlock.

more...