Log message:
mysql56: updated to 5.6.45

Changes in MySQL 5.6.45:

Functionality Added or Changed

Microsoft Windows: A new warning message now reminds DBAs that connections made \ 
using the MySQL named pipe on Windows has limited the permissions a connector \ 
can request on the named pipe.

Previously, the named_pipe_full_access_group system variable was set to a value \ 
that maps to the built-in Windows Everyone group (SID S-1-1-0) by default. \ 
However, this group is not ideal and should be replaced with a group that \ 
restricts its membership for connectors that are unable to request fewer \ 
permissions on the MySQL named pipe.

The new warning is written to the error log at startup if the string value \ 
assigned to named_pipe_full_access_group is '*everyone*' (or the Windows System \ 
Language equivalent) and named pipes are enabled. In addition, the warning is \ 
written to the error log and raised to the client if the system variable is \ 
reset to the Everyone group at runtime.

Bugs Fixed

InnoDB: A query that scanned the primary key of a table did not return the \ 
expected result.

InnoDB: A full-text cache lock taken when data is synchronized was not released \ 
if the full-text cache size exceeded the full-text cache size limit.

InnoDB: Client sessions using different auto_increment_increment values while \ 
performing concurrent insert operations could cause a duplicate key error.

Replication: In query log events in the binary log, the thread ID used for the \ 
execution of DROP TABLE and DELETE statements was identified incorrectly or not \ 
at all. On a multi-threaded replication slave, where temporary tables were \ 
involved (which require the correct thread ID as they are session specific), \ 
this omission resulted in errors when using mysqlbinlog to replay the binary log \ 
for point-in-time recovery. The thread ID is now set correctly.

Installing from RPM packages could result in an error log with incorrect permissions.

Enabling audit log encryption could cause a server exit.

MySQL Installer did not install OpenSSL DLL dependencies if the Development \ 
component was not selected.

The parser could leak memory for certain multiple-statement queries.

MySQL does not support OpenSSL session tickets, but did not set the \ 
SSL_OP_NO_TICKET flag to inform OpenSSL of that. The flag is now set.

UpdateXML() did not always free memory properly in certain cases.

Empty values in the name column of the mysql.plugin system table caused the \ 
server to exit during startup.

Some PROXY grants were not replicated to slaves, causing incorrect replication.

If an INSTALL PLUGIN statement contained invalid UTF-8 characters in the shared \ 
library name, it caused the server to hang (or to raise an assertion in debug \ 
builds).

Log message:
mysql56-client: Disable epoll in bundled libevent too.

Log message:
Bump PKGREVISION for addition of USE_GCC_RUNTIME

Log message:
Add USE_GCC_RUNTIME to mysql{51,55,56}

Log message:
mysql56: updated to 5.6.44

mysql-5.6.44:
Unknown changes

Log message:
mysql56-client: fix some pkglint issues

Log message:
Fix pkgbase

Log message:
mysql56-{client,server}: updated to 5.6.43

Changes in MySQL 5.6.43:

Functionality Added or Changed

Microsoft Windows: The access control granted to clients on the named pipe \ 
created by the MySQL server now is set to the minimum necessary for successful \ 
communication on Windows. Newer MySQL client software can open named pipe \ 
connections without any additional configuration. If older client software \ 
cannot be upgraded immediately, the new named_pipe_full_access_group server \ 
system variable can be used to give a Windows group the necessary permissions to \ 
open a named pipe connection. Membership in the full-access group should be \ 
restricted and temporary.

Bugs Fixed

Replication: A patch to correct the handling of quotes for identifiers in \ 
ROLLBACK TO SAVEPOINT statements in the binary log was not correctly applied to \ 
subsequent MySQL versions.

Replication: In some circumstances, the CHANGE MASTER TO statement could not be \ 
used on a replication slave if the master info log had been changed from a table \ 
(master_info_repository=TABLE) into a file (master_info_repository=FILE).

Replication: The value returned by a SHOW SLAVE STATUS statement for the total \ 
combined size of all existing relay log files (Relay_Log_Space) could become \ 
much larger than the actual disk space used by the relay log files. The I/O \ 
thread did not lock the variable while it updated the value, so the SQL thread \ 
could automatically delete a relay log file and write a reduced value before the \ 
I/O thread finished updating the value. The I/O thread then wrote its original \ 
size calculation, ignoring the SQL thread's update and so adding back the space \ 
for the deleted file. The Relay_Log_Space value is now locked during updates to \ 
prevent concurrent updates and ensure an accurate calculation.

Replication: If the relay log index file was temporarily locked for viewing by a \ 
backup process for a replication slave, and MySQL Server also attempted to \ 
access the file at that time for rename or delete operations, the backup \ 
completed with warnings, but MySQL Server experienced an unexpected halt. MySQL \ 
Server now retries the file access operation a number of times in case this or a \ 
similar scenario is the explanation and the file becomes available again before \ 
long.

The server permitted creation of databases with the same name as redo log files, \ 
which could result in unexpected server behavior. Such names are no longer \ 
permitted as database names.

When a subquery contained a UNION, the count of the number of subquery columns \ 
was calculated incorrectly.

Comparing log file names as strings using the memcmp() function resulted in \ 
uninitialized memory read errors. The comparison now uses the strncmp() \ 
function. Thanks to Zsolt Parragi and Laurynas Biveinis for their contributions.

The transformation of IN subquery predicates into semijoins was not handled \ 
correctly for a very large number of tables.

Executing a prepared statement to do a multiple-row insert with large number of \ 
placeholders consumed excessive memory and could execute slowly.

The parser accepted invalid SET statement syntax in trigger definitions that \ 
could result in a server exit.

MyISAM index corruption could occur for bulk-insert and table-repair operations \ 
that involve the repair-by-sorting algorithm and many (more than 450 million) \ 
rows.

A query employing a dynamic range and an index merge could use more memory than \ 
expected.

Log message:
mysql56-client: change the default configuration to avoid information
disclosure to a malicious server.

Backport of upstream commit:
https://github.com/mysql/mysql-server/commit/98ed3d8bc8ad724686d26c7bf98dced3bd1777be

Exploit method described here:
https://gwillem.gitlab.io/2019/01/17/adminer-4.6.2-file-disclosure-vulnerability/

Log message:
mysql56: updated to 5.6.42

Changes in MySQL 5.6.42

Functionality Added or Changed

* Previously, file I/O performed in the I/O cache in the mysys library was not \ 
instrumented, affecting in particular file I/O statistics reported by the \ 
Performance Schema about the binary log index file. Now, this I/O is \ 
instrumented and Performance Schema statistics are accurate. Thanks to Yura \ 
Sorokin for the contribution.

* The zlib library version bundled with MySQL was raised from version 1.2.3 to \ 
version 1.2.11. MySQL implements compression with the help of the zlib library.

* The zlib compressBound() function in zlib 1.2.11 returns a slightly higher \ 
estimate of the buffer size required to compress a given length of bytes than it \ 
did in zlib version 1.2.3. The compressBound() function is called by InnoDB \ 
functions that determine the maximum row size permitted when creating compressed \ 
InnoDB tables or inserting rows into compressed InnoDB tables. As a result, \ 
CREATE TABLE ... ROW_FORMAT=COMPRESSED or INSERT operations with row sizes very \ 
close to the maximum row size that were successful in earlier releases could now \ 
fail.

Bugs Fixed

* InnoDB: An ALTER TABLE operation that added a primary key produced a \ 
segmentation fault.

* InnoDB: An assertion was raised during an OPTIMIZE TABLE operation.

* InnoDB: A foreign key constraint name was duplicated during a rename table \ 
operation, causing a failure during later query execution.

* InnoDB: The location of the Innodb Merge Temp File that reported by the \ 
wait/io/file/innodb/innodb_temp_file Performance Schema instrument was \ 
incorrect.

* Replication: When FLUSH statements for specific log types (such as FLUSH SLOW \ 
LOGS) resulted in an error, the statements were still written to the binary log. \ 
This stopped replication because the error had occurred on the master, but did \ 
not occur on the slave. MySQL Server now checks on the outcome of these FLUSH \ 
statements, and if an error occurred, the statement is not written to the binary \ 
log.

* Microsoft Windows: On Windows, uninstallation of the MySQL Server MSI package \ 
through MySQL Installer produced a spurious popup window.

* Concurrent INSERT and SELECT statements on a MERGE table could result in a \ 
server exit.

* MySQL Server and test RPM packages were missing perl-Data-Dumper as a dependency.

* For the mysql client, the -b short option was associated with two long \ 
options, --no-beep and --binary-as-hex. The -b option now is associated only \ 
with --no-beep.

* Very long table keys were handled incorrectly on replication slaves.

* During server startup/shutdown, PID files could be mishandled.

* For MEMORY tables, memory overflow errors could occur.

* When converting from a BLOB (or TEXT) type to a smaller BLOB (or TEXT) type, \ 
no warning or error was reported informing about the truncation or data loss. \ 
Now an appropriate error is issued in strict SQL mode and a warning in nonstrict \ 
SQL mode.

* Failure to create a temporary table during a MyISAM query could cause a server \ 
exit. Thanks to Facebook for the patch.

* An attempted read of an uncommitted transaction raised an assertion.

* ALTER TABLE ... REORGANIZE PARTITION ... could result in incorrect behavior if \ 
any partition other than the last was missing the VALUES LESS THAN part of the \ 
syntax.

* yum update did not properly update from RHEL5 RPM packages to current packages.

* It was possible for a subquery that used a unique key on a column allowing \ 
NULL to return multiple rows.