MySQL 5.5.49

# Bugs Fixed
* InnoDB: Running REPLACE operations on multiple connections resulted in a hang.
* Replication: The test case main.merge failed when the variables binlog_format was set to “ROW,” as the server tried to get information for table creation for a child table before it was opened. With this fix, the server skips getting information for the table in the situation.
* MySQL did not build with GCC 5.
* The System-V initialization script for RHEL6 or older failed to enable the mysqld service by default.
* Improper host name checking in X509 certificates could permit man-in-the-middle attacks.
* A boolean mode full-text search caused a segmentation fault.
* Concurrent selecting and flushing of a FEDERATED table while killing connections accessing it could result in a server exit.
* Executing GRANT PROXY statements after altering the definition of the mysql.user system table could result in a server exit.
* Certain error messages included part of the SQL statement that produced them, possibly exposing data.
* Character set conversion operations on NULL parameters to prepared statements could cause a server exit.
* For INSERT and UPDATE operations that caused FOREIGN KEY constraint violations, errors were reported rather than warnings when the IGNORE keyword was used.
* Processlist state information was not updated correctly for LOAD DATA INFILE and could show a state different from executing.