Release Notes for MariaDB Enterprise Server 10.3.32-14
This page is part of MariaDB's Documentation.
The parent of this page is: Release Notes for MariaDB Enterprise Server 10.3
Topics on this page:
Overview
MariaDB Enterprise Server 10.3.32-14 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.
MariaDB Enterprise Server 10.3.32-14 was released on 2021-12-13.
Fixed Security Vulnerabilities
CVE (with cve.org link) | CVSS base score |
7.5 | |
7.5 | |
6.5 | |
5.5 | |
5.5 |
Notable Changes
Galera updated to 25.3.35
Enterprise Spider no longer enables pushdown of UDFs and Stored Functions to the Data Node by default: (MDEV-26545)
The default value of
spider_use_pushdown_udf
has changed from-1
to0
In previous releases, Enterprise Spider pushed UDFs and Stored Functions down to the Data Node by default, which could cause query results to be inconsistent.
Starting with this release, all UDFs and stored functions are evaluated on the Spider Node by default. If desired, pushdown of UDFs and Stored Functions can be explicitly enabled by setting
spider_use_pushdown_udf=1
. Testing is recommended to confirm that query results are consistent.
Performance Schema tables provide descriptions of each column in the
COMMENT
column option. (MDEV-25325)
Issues Fixed
Can result in a hang or crash
MariaDB Enterprise Cluster, powered by Galera, can crash on
INSERT
if the table does not have a primary key and if the data for a field exceeds 4096 bytes. (MDEV-24978)When an InnoDB tablespace (
.ibd
) file is imported usingALTER TABLE .. IMPORT TABLESPACE
without a corresponding.cfg
file, InnoDB causes a server crash. (MDEV-26131, MDEV-20931)When
OPTIMIZE TABLE
(ormariadb-check -o
) is executed against an InnoDB table with aFULLTEXT
index, InnoDB can cause a server crash. (MDEV-25702, MENT-1198)Resolving aggregate functions that are used in a view can cause in a crash. (MDEV-24454)
Executing
CREATE OR REPLACE TABLE AS SELECT
underLOCK TABLE
can cause in a crash. (MDEV-23391)If two InnoDB tables have a foreign key and an operation cascades from the parent table to the child table, an index on a virtual generated column in the child table can become corrupt. (MDEV-26866)
MariaDB Enterprise Cluster, powered by Galera, crashes with errors like:
[ERROR] WSREP: Trx 236236 tries to abort slave trx 236238
(MDEV-25835)Server crashes when a table uses a sequence as a column default (
DEFAULT NEXT_VALUE(my_seq)
) and the table is used concurrently by both a prepared statement and a normal statement. (MDEV-22785)MariaDB Enterprise Cluster can crash due to an incorrect conflict resolution on multi-master setup. (MDEV-25992, MDEV-25114)
Can result in unexpected behavior
skip_networking
does not prevent replication. (MDEV-24969)MariaDB Enterprise Cluster joiner node incorrectly uses
localhost
for TLS certificate verification and fails to join cluster whenwsrep_sst_method=mariabackup
andencrypt=3
are configured. (MDEV-26360)mariadb --binary-mode
is not able to replay somemysqlbinlog
outputs if\\0
is in the data. (MDEV-25444)Memory leak with row-based replication can lead to high memory usage on replica servers. (MDEV-26712)
SHOW CREATE VIEW
andmariadb-dump
generate invalid SQL for some complex views. (MDEV-26299)When statement-based or mixed replication is used and a DML statement encounters an error in a transaction that creates or drops a temporary table, non-committed writes to transactional tables can be incorrectly replicated to replica servers. (MDEV-26833)
MariaDB Enterprise Cluster joiner node fails to join cluster when
wsrep_sst_method=mariabackup
and Backward Compatible SST TLS Mode is configured. (MDEV-26211)Spider does not work correctly for UDF and stored functions if used in a query's
WHERE
conditions. (MDEV-26545)On a partitioned Spider table, result of
SELECT
wrongly depends on the partition targeted by the previousSELECT
(MDEV-26333)If an
INVISIBLE
column has a computed default value, anINSERT
statement that doesn't specify a value for the column causes the default value to be ignored. (MDEV-25891)
Platforms
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.3.32-14 is provided for:
CentOS 7 (x86_
64) CentOS 8 (x86_
64, ARM64) Debian 9 (x86_
64, ARM64) Debian 10 (x86_
64, ARM64) Microsoft Windows (x86_
64) 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)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".