MySQL 5.5.44

# 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: 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: Estimates that were too low for the size of merge chunks in the result sorting algorithm caused a server exit.
- SHOW VARIABLES mutexes were being locked twice, resulting in a server exit.
- A Provides rule in RPM .spec files misspelled “mysql-embedded” as “mysql-emdedded”.
- Under certain conditions, the libedit command-line library could write outside an array boundary and cause a client program crash.
- Host value matching for the grant tables could fail to use the most specific of values that contained wildcard characters.
- A user with a name of event_scheduler could view the Event Scheduler process list without the PROCESS privilege.
-SHOW GRANTS after connecting using a proxy user could display the password hash of the proxied user.
- 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.
- Loading corrupt spatial data into a MyISAM table could cause the server to exit during index building.
- 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.
- MySQL failed to compile using OpenSSL 0.9.8e.