Release Notes for MariaDB Enterprise Server 10.4.10-4
This page is part of MariaDB's Documentation.
The parent of this page is: Release Notes for MariaDB Enterprise Server 10.4
Topics on this page:
Overview
This fourth release of MariaDB Enterprise Server 10.4 is a maintenance release, including a variety of fixes.
MariaDB Enterprise Server 10.4.10-4 was released on 2019-11-18.
Fixed Security Vulnerabilities
CVE (with cve.org link) | CVSS base score |
6.5 | |
6.5 | |
4.4 |
Notable Changes
New option
innodb_change_buffer_dumpadded to Debug builds. This option dumps the contents of the InnoDB change buffer to the server error log at startup. This is useful when a slow shutdown cannot be performed successfully. (MDEV-20864)Eliminated unnecessary logging of warnings to the error log regarding InnoDB maximum row size for DML statements which should be present only for DDL operations. (MENT-454)
Improved MariaDB Enterprise Cluster error logging to explain that GCache recovery is not possible when GCache encryption is enabled. (MENT-373)
Issues Fixed
Can result in data loss
mariabackup --prepare --export ... could overwrite binary logs if certain conditions were present. (MDEV-20703)
Conditions which must be present to trigger this bug:
mariabackup is executed on the MariaDB Server host, and
Configuration files from the master are used, and
Configuration files enable binary logging
If unable to upgrade to MariaDB Enterprise Server 10.4.10-4, where this bug is fixed, a workaround is available: use the
--defaultsoption to mariabackup to avoid the bug-triggering conditions by specifying a different configuration file.
Can result in a hang or crash
Prior removal of a
FULLTEXTindex from an InnoDB table can cause a hang on startup. (MDEV-19647)Removal of a
FULLTEXTindex from an InnoDB table can cause a hang. (MDEV-19529)Change to a InnoDB table containing a
FULLTEXTindex can cause Server to become unresponsive. (MDEV-20987)Removal of a virtual column used by an index can result in a crash. (MENT-434)
CREATE INDEX, ALTER TABLE, or OPTIMIZE TABLE on an InnoDB table can cause Server to become unresponsive. (MDEV-20852)
INSTANTADD COLUMNon an InnoDB table which includes aFOREIGN KEYdefinition can result in a crash. (MENT-435)INSTANTcolumnDROPor column reorder can result in a crash. Server restart can also crash unless innodb_force_ is set torecovery 2or greater. (MDEV-20117)
Can result in unexpected behavior
Unnecessary logging of warnings to the error log regarding InnoDB maximum row size for DML statements which should be present only for DDL operations. (MENT-454)
After server restart, a SELECT using a
FULLTEXTindex on InnoDB tables can fail to return some data. (MDEV-19073)MariaDB Enterprise Backup and MariaDB Backup, when using
mbstream, recreatedxtrabackup_infoin the same directory as the backup file. Repeated extract of the backup could fail. (MDEV-18438)mysqld_multi.shscript could not be launched and returned a syntax error. (MENT-433)Though not supported on Microsoft Windows, the server_
audit_ system variable for the Audit plugin accepted aoutput_ type SYSLOGvalue. (MDEV-19851)FOREIGN KEYconstraints have been ignored during DELETE when parent table is System-Versioned. (MDEV-16210)DELETE from child table with
FOREIGN KEYwas not possible when the table is System-Versioned. (MDEV-20812)MariaDB Enterprise Cluster cannot perform GCache recovery when GCache encryption is enabled, but no warning was sent to the error log. (MENT-373)
Related to install and upgrade
Installing MariaDB Enterprise Server from repository failed on CentOS 7 due to package dependencies. (MENT-420)
Interface Changes
WARN_INNODB_PARTITION_OPTION_IGNOREDerror code added
Platforms
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.4.10-4 is provided for:
CentOS 8
CentOS 7
CentOS 6
Debian 10
Debian 9
Debian 8
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Ubuntu 18.04
Ubuntu 16.04
Microsoft Windows
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
Note
CentOS 6, Debian 8, and Red Hat Enterprise Linux 6 are no longer supported as per the MariaDB Engineering Policy. Older releases are available from the MariaDB Downloads page. Instructions for installation are included as a README file within the download.
