Log Message:
mysql57: updated to 5.7.24

Changes in MySQL 5.7.24

Deprecation and Removal Notes

* InnoDB; Partitioning: Support for placing table partitions in shared \ 
tablespaces is deprecated and will be removed in a future version of MySQL. \ 
Shared tablespaces include the system tablespace and general tablespaces. For \ 
information about identifying partitions in shared tablespaces and moving them \ 
to file-per-table tablespaces, see Preparing Your Installation for Upgrade.

* InnoDB: Support for TABLESPACE = innodb_file_per_table and TABLESPACE = \ 
innodb_temporary clauses with CREATE TEMPORARY TABLE is deprecated and will be \ 
removed in a future MySQL version.

Functionality Added or Changed

Replication: Use the group_replication_exit_state_action option to configure how \ 
Group Replication behaves when a member leaves the group involuntarily, for \ 
example when it is expelled from the group due to an unstable network \ 
connection. When group_replication_exit_state_action is set to ABORT_SERVER, \ 
upon exiting the group unintentionally, the instance shuts MySQL down, and when \ 
group_replication_exit_state_action is set to READ_ONLY the instance sets MySQL \ 
to super read only mode instead and its state is set to ERROR.

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: A query that scanned the primary key of a table did not return the \ 
expected result.

* InnoDB: A query interruption during a lock wait caused an error.

* InnoDB: An index record was not found when updating a secondary index defined \ 
on a generated column.

* InnoDB: The update log applied as part of an online ALTER TABLE operation did \ 
not take into account the computed value of the generated column in the old row \ 
while updating the secondary index.

* InnoDB: An unsupported DDL operation involving a foreign key constraint raised \ 
an assertion.

* InnoDB: An attempted foreign key check on a discarded table caused 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: In a function called before the execution of a statement in a stored \ 
procedure, a read and write operation on trx->lock.start_stmt was not \ 
protected by a mutex.

* InnoDB: An error occurred during a DDL operation due to a mismatch in a \ 
REDUNDANT row format calculation that determines the length of the online log.

* 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.

* Partitioning: When a CREATE TABLE ... PARTITION BY ... statement failed due to \ 
an invalid partition definition, the server did not remove any partition files \ 
which might have been created prior to encountering the invalid PARTITION \ 
clause.

* Partitioning: It was possible to perform FLUSH TABLES FOR EXPORT on a \ 
partitioned table created with innodb_file_per_table=1 after discarding its \ 
tablespace. Attempting to do so now raises ER_TABLESPACE_DISCARDED.

* Replication: When the binlog_group_commit_sync_delay system variable is set to \ 
a wait time to delay synchronization of transactions to disk, and the \ 
binlog_group_commit_sync_no_delay_count system variable is also set to a number \ 
of transactions, the MySQL server exits the wait procedure if the specified \ 
number of transactions is reached before the specified wait time is reached. The \ 
server manages this process by checking on the transaction count after a delta \ 
of one tenth of the time specified by binlog_group_commit_sync_delay has \ 
elapsed, then subtracting that interval from the remaining wait time.

more...