[ 21:08 joneum  ]

• 533270 databases/mysql56-client/Makefile
• 533270 databases/mysql56-server/Makefile
• 533270 databases/mysql56-server/distinfo
• 533270 databases/mysql56-server/files/patch-storage_innobase_handler_i_s.cc

databases/mysql56-{client, server}: Update to latest release 5.6.48

Bugfix:
- InnoDB: A tablespace import operation that failed due to the source and
destination tables being defined with different DATA DIRECTORY clauses reported
an insufficiently descriptive schema mismatch error. Moreover, if a .cfg file
was not present, the same operation would raise an assertion failure. A more
informative error message is now reported in both cases before the import
operation is terminated due to the data directory mismatch.

- InnoDB: Updating certain InnoDB system variables that take string values
raised invalid read errors during Valgrind testing.

- Replication: In the event of an unplanned disconnection of a replication slave
from the master, the reference to the master's dump thread might not be removed
from the list of registered slaves, in which case statements that accessed the
list of slaves would fail. The issue has now been fixed

- Replication: With the settings binlog_format=MIXED,
tx_isolation=READ-COMMITTED, and binlog_row_image=FULL, an INSERT ... SELECT
query involving a transactional storage engine omitted any columns with a null
value from the row image written to the binary log. This happened because when
processing INSERT ... SELECT statements, the columns were marked for inserts
before the binary logging format was selected. The issue has now been fixed.

More Infos: https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-48.html

MFH:		2020Q2
Security:	21d59ea3-8559-11ea-a5e2-d4c9ef517024 (MySQL - Server)
Security:	622b5c47-855b-11ea-a5e2-d4c9ef517024 (MySQL - Client)
Sponsored by:	Netzkommune GmbH