-
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. (Bug #69990, Bug #17299181)
-
InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. (Bug #20816223)
-
InnoDB: Removal of a foreign key object from the data dictionary cache during error handling caused the server to exit. (Bug #20442523)
-
InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. (Bug #20417397)
-
InnoDB: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit. (Bug #20049521)
-
SHOW VARIABLES mutexes were being locked twice, resulting in a server exit. (Bug #20788853)
-
A Provides rule in RPM .spec files misspelled“mysql-embedded”as“mysql-emdedded”. (Bug #20734434)
-
Under certain conditions, the libedit command-line library could write outside an array boundary and cause a client program crash. (Bug #20318154)
-
Host value matching for the grant tables could fail to use the most specific of values that contained wildcard characters. (Bug #20181776)
-
A user with a name of event_scheduler could view the Event Scheduler process list without the PROCESS privilege. (Bug #20007583, Bug #20754369)
-
SHOW GRANTS after connecting using a proxy user could display the password hash of the proxied user. (Bug #19817663)
-
For a prepared statement with an ORDER BY that refers by column number to a GROUP_CONCAT() expression that has an outer reference, repeated statement execution could cause a server exit. (Bug #19814337)
-
Loading corrupt spatial data into a MyISAM table could cause the server to exit during index building. (Bug #19573096)
-
Certain queries for the INFORMATION_SCHEMA TABLES and COLUMNS tables could lead to excessive memory use when there were large numbers of empty InnoDB tables. (Bug #72322, Bug #18592390)
-
MySQL failed to compile using OpenSSL 0.9.8e. (Bug #68999, Bug #16861371)
