Log Message:
mysql56: update to 5.6.38

Changes in MySQL 5.6.38:

Packaging Notes
---------------
mysqlcheck was missing in the MySQL Server Docker image, which prevented \ 
mysql_upgrade from running.

Bugs Fixed
----------
InnoDB: Replication lag occurred on slave instances during large update \ 
operations on tables with many partitions.
InnoDB: A failure occurred during an end range comparison.
InnoDB: Enabling the innodb_buffer_pool_load_now setting failed in readonly \ 
mode. The event that signals the buffer pool load thread was not initialized.
InnoDB: A long wait for a dictionary operation lock held by a full-text search \ 
synchronization operation caused a server exit.
Partitioning: Queries involving NULL were not always handled correctly on tables \ 
that were partitioned by LIST.
Replication: When replicating a partitioned table with an index, on a \ 
replication slave where HASH_SCAN was specified as part of the \ 
slave_rows_search_algorithms setting, the slave I/O thread sometimes stopped \ 
with an error HA_ERR_KEY_NOT_FOUND.
Replication: Replication clients no longer enable LOCAL capability for LOAD DATA \ 
statements, because they do not use LOAD DATA LOCAL statements.
Replication: In case of a failure while creating multiple slave applier worker \ 
threads, some threads would be left orphaned and their resources would not be \ 
collected. Thanks to Laurynas Biveinis for his contribution to fixing this bug.
MSI packages for Windows failed to detect when Microsoft Visual C++ 2010 \ 
Redistributable Package was installed.
yaSSL could incorrectly perform TLS cipher negotiation.
The server failed to check the maximum path length for partition names.
Identifiers containing a mixture of backslashes and backticks could be parsed \ 
incorrectly.
Source packages for Debian platforms contained prebuilt debug binaries, causing \ 
build failures on any architectures other than the one on which those binaries \ 
were built.
Uninstalling the daemon_memcached plugin caused a serious error.
Selecting from a view could yield different results with materialization enabled \ 
versus materialization disabled.
The Performance Schema failed to check the maximum host length for client \ 
connections.
A server error occurred when a full text search result exceeded the \ 
innodb_ft_result_cache_limit setting. The patch for this bug also backports a \ 
related patch.
If a stored function was considered a constant by the optimizer, calling it from \ 
a subquery in a NOT IN condition in the WHERE clause could cause a server exit.
A mysqldump memory leak was fixed.
If a session rolled back to a savepoint and then was killed, the statements up \ 
to the point of the savepoint could be committed.
For clients that used Connector/Python and authenticated using the \ 
sha256_password plugin, the server could handle connections incorrectly.
NAME_CONST() can return null if incorrect arguments are given. In some cases, \ 
this was not handled and could cause a server exit.