Release Notes for MariaDB Enterprise Server 10.3.23-7
This seventh release of MariaDB Enterprise Server 10.3 is a maintenance release, including a variety of fixes.
MariaDB Enterprise Server 10.3.23-7 was released on 2020-06-08.
Fixed Security Vulnerabilities
CVE (with cve.mitre.org link)
CVSS base score
MariaDB CVEs do not have a CVSS base score. This CVE is rated "medium" according to the definition in the engineering policy.
upgradenow displays a warning when upgrading a replica from MySQL Server to MariaDB Enterprise Server if data was present in the
mysql.slave_relay_log_infotables. A warning is needed as this information will be ignored. (MDEV-10047)
mysqldump has a new
--ignore-table-data=<table>option. When used, the dump will include the table definition for the listed tables, but not the INSERT statements for the data in the table. (MDEV-22037)
mariabackup has a new --rollback-xa option. By default, mariabackup will not commit or rollback uncommitted XA transactions, and when the backup is restored any uncommitted XA transactions must be manually committed using XA COMMIT or be manually rolled-back using XA ROLLBACK. The --rollback-xa option can be used to rollback uncommitted XA transactions while performing a --prepare operation, eliminating the need for manual commit or rollback when the backup is restored. (MDEV-21168)
shutdown-wait-for-slaves system variable added, to control that a primary server only completes the shutdown after the last binary log has been sent to all connected slaves. This behavior is not active by default. Before the addition of this system variable, this was achieved using
mysqladmin shutdown --wait_for_all_slavesfor a master. (MENT-202)
instant_system variable added to control whether an instant alter_ column_ allowed
DROPcolumn or reorder can change an InnoDB format. The default is
add_lastto allow an instant
ADD COLUMNas the last column of the table. Option
nevershould be used if a tablespace import to older version of MariaDB Server should be possible. (MDEV-20590)
Can result in data loss
Can result in crashes, hangs, stalls
MariaDB Enterprise Backup ignored the timeout setting --ftwrl-wait-timeout when an explicit
LOCK TABLES ... WRITEwas active in another session. As a result, MariaDB Enterprise Server waited for release of the lock even if the timeout was reached. (MDEV-20230)
open_table_caches_instanceshave been created, a crash could occur due to exceeding the limit of open file descriptors. (MDEV-18027)
Can result in unexpected behavior
A duplicate key error showed the duplicate key value truncated to 64 characters without indicating the truncation. (MDEV-20604)
SET GLOBALfor the InnoDB variables innodb_
ft_, innodb_ aux_ table ft_, innodb_ server_ stopword_ table ft_, and innodb_ user_ stopword_ table buffer_could lead to corrupted strings for the settings. (MDEV-22393) pool_ filename
Replication could be aborted when the replication data includes nested version-based conditional comments.
Server-Idcould lead to events being disabled for replicas, even if a single node configuration without a replica was used. (MDEV-21758)
encryption_system variable maximum value changed from threads
instant_system variable added alter_ column_ allowed
wait_system variable added for_ slaves
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.3.23-7 is provided for:
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
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".