Incompatible Change: These changes were made to mysqld_safe:
Unsafe use of rm and chown in mysqld_safe could result in privilege escalation. chown now can be used only when the target directory is
/var/log. An incompatible change is that if the directory for the Unix socket file is missing, it is no longer created; instead, an error occurs. Due to these changes, /bin/bash is required to run mysqld_safe on Solaris. /bin/sh is still used on other Unix/Linux platforms.
--lediroption now is accepted only on the command line, not in option files.
mysqld_safe ignores the current working directory.
Other related changes:
Initialization scripts that invoke mysqld_safe pass
Initialization scripts create the error log file only if the base directory is
Unused systemd files for SLES were removed.
(Bug #24483092, Bug #25088048, Bug #25378439, Bug #25378565)
References: See also: Bug #24464380, Bug #24388753, Bug #24619033, Bug #82920.
Incompatible Change: A change made in MySQL 5.5.51 for handling of multibyte character sets by
LOAD DATAwas reverted due to the replication incompatibility that it caused. (Bug #24487120, Bug #82641)
References: See also: Bug #23080148.
InnoDB: The GCC
mach_parse_compressedfunction should load one to five bytes depending on the value of the first byte. Due to a GCC bug, GCC 5 and 6 emit code to load four bytes before the first byte value is checked (GCC Bug #77673). A workaround prevents this behavior. Thanks to Laurynas Biveinis for the patch. (Bug #24707869, Bug #83073)
Some Linux startup scripts did not process the
datadirsetting correctly. (Bug #25159791)
CREATE TABLEnow requires the
INDEX DIRECTORYis specified explicitly as a table or partition option.
ALTER TABLErequires the
FILEprivilege if either option is specified explicitly as a partition option (it ignores them if specified as table options). (Bug #25092566)
OEL RPM packages now better detect which platforms have multilib support (for which 32-bit and 64-bit libraries can be installed). Thanks to Alexey Kopytov for the patch. (Bug #24925181, Bug #83457)
If mysqladmin shutdown encountered an error determining the server process ID file, it displayed an error message that did not clearly indicate the error was nonfatal. It now indicates that execution continues. (Bug #24496214)
The data structure used for
ZEROFILLcolumns could experience memory corruption, leading eventually to a server exit. (Bug #24489302)
Use of very long subpartition names could result in a server exit. Now partition or subpartition names larger than 64 characters produce an
ER_TOO_LONG_IDENTerror. (Bug #24400628, Bug #82429)
gettimeofday()could return an invalid value and cause a server shutdown. (Bug #23499695)
A union query resulting in tuples larger than
max_join_sizecould result in a server exit. (Bug #23303485)
For some deeply nested expressions, the optimizer failed to detect stack overflow, resulting in a server exit. (Bug #23135667)
--character-set-serveroption could set connection character set system variables to values such as
ucs2that are not permitted. (Bug #15985752, Bug #23303391)