Release Notes for MariaDB Enterprise Server 10.3.31-13
This thirteenth release of MariaDB Enterprise Server 10.3 is a maintenance release. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.31-13 was released on 2021-09-14.
Fixed Security Vulnerabilities
CVE (with cve.mitre.org link)
CVSS base score
This release of MariaDB Enterprise Server includes features backported from MariaDB Enterprise Server 10.6.
Enhanced consistency for Semi-Sync Replication
Prior to this release, when using semi-synchronous replication, if a Primary crashed before sending a transaction to the Replica, on restart the Primary could recover incomplete InnoDB transactions when rejoining as a Replica.
With this release, when using semi-synchronous replication and with
rpl_semi_sync_slave_enabled=ON, incomplete transactions will be rolled-back on the Replica, ensuring the new Primary (former Replica) and new Replica (former Primary) remain in sync.
wsrep_sst_mariabackupchecks all server-related configuration groups when processing a configuration file. (MDEV-25669)
Prior to this release, only the
[mysqld]configuration group was checked when processing a configuration file.
Prior to this release, MariaDB Enterprise Backup expected --stream=xbstream, even though the
xbstreamutility had been renamed to
InnoDB no longer acquires advisory file locks by default. (MDEV-24393)
The file_key_management encryption plugin does not support key rotation, so key rotation checks are not required.
In previous releases, unnecessary key rotation checks with the file_key_management encryption plugin could reduce performance, unless they were explicitly disabled by setting innodb_encryption_rotate_key_age=0.
Galera updated to 25.3.34
ARM64 is now supported for several platforms.
Can result in data loss
Can result in a hang or crash
Possible server crash when pushing a
WHEREcondition over a mergeable derived table / view / CTE DT into a grouping view / derived table / CTE V whose item list contained set functions with constant arguments. (MDEV-25635)
Server crashes on second execution of a stored procedure or a prepared statement when the corresponding query executes a window function on a view, CTE, or derived table. (MDEV-25565)
Server crashes possible when executing a prepared statement with a hanging recursive CTE. (MDEV-26135)
Server crashes while executing query with a CTE in a prepared statement or stored procedure. (MDEV-26025)
Server crashes while executing query with a recursive CTE that is indirectly used twice. (MDEV-26202)
Server crashes due to infinite recursion while processing an embedded recursive CTE with missing
Server crashes in InnoDB deadlock checker under high load. (MDEV-25594)
Server crashes when a virtual generated column has a prefix index. (MDEV-26220)
Server crashes when a subquery references an outer column in an
ORDER BYclause. (MDEV-25629)
Server crashes due to a stack overrun in the query optimizer while executing query with more than 32 equality conditions that compare columns of different tables (such as
Server crashes when a window function is the left expression of an
IN(SELECT ..)subquery. (MDEV-25630)
Crash when parsing query using derived table containing table value constructors (MDEV-25484)
Can result in unexpected behavior
Several fixes for MariaDB Enterprise Cluster (Galera) SST scripts. (MDEV-20580`:org-jira:`MDEV-25818) (MDEV-25759) (MDEV-25719) (MDEV-15639) (MDEV-15371) (MDEV-18797) (MENT-1170) (MDEV-24979) (MDEV-21192)
As a result of this issue, a Joiner node writes the following error to the MariaDB Error Log:
tail: cannot open 'mysql-bin.index' for reading: No such file or directory
In prior releases, the following warning could be written to the log:
InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `schema`.`child_table`"`` :org-jira:`MDEV-26062`
"Condition pushdown into derived table"optimization cannot be applied if the expression being pushed refers to a derived table column which is computed from an expression that has a stored function call, @session variable reference, or other similar construct. (MDEV-25969)
A query that uses
ORDER BY .. LIMITclause and
"Range checked for each record"optimization could produce incorrect results. (MDEV-25858)
Wrong result when selecting from views, derived tables, or CTEs with the form
(SELECT .. LIMIT <n>) ORDER BY ..(MDEV-25679)
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.3.31-13 is provided for:
CentOS 7 (x86_64)
CentOS 8 (x86_64 / ARM64)
Debian 9 (x86_64 / ARM64)
Debian 10 (x86_64 / ARM64)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64 / ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64 / ARM64)
Ubuntu 18.04 (x86_64 / ARM64)
Ubuntu 20.04 (x86_64 / ARM64)
Microsoft Windows (x86_64)