Release Notes for MariaDB Enterprise Server 10.6.5-2

Overview

MariaDB Enterprise Server 10.6.5-2 is a maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes.

MariaDB Enterprise Server 10.6.5-2 was released on 2021-12-13.

Fixed Security Vulnerabilities

CVE (with cve.mitre.org link)

CVSS base score

CVE-2021-46662

5.5

CVE-2021-46667

7.5

Notable Changes

  • Enterprise Spider no longer enables pushdown of UDFs and Stored Functions to the Data Node by default:

    • The default value of spider_use_pushdown_udf has changed from -1 to 0

    • 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. (MDEV-26545)

  • Performance Schema tables provide descriptions of each column in the COMMENT column option. (MDEV-25325)

  • In the Spider ODBC Topology, Enterprise Spider automatically sets the appropriate transaction isolation level for the ODBC data source. (MENT-1328)

  • The InnoDB Force Recovery procedure has changed to differentiate between rollback of DDL and DML operations. The changes are:

    • The behavior of innodb_force_recovery is no longer identical when innodb_force_recovery=3 and innodb_force_recovery=4

    • When innodb_force_recovery=3 is set, InnoDB skips rollback of DML operations, but DDL operations will still be rolled back using the DDL log.

    • When innodb_force_recovery=4 is set, InnoDB skips rollback of both DML and DDL operations. This behavior is equivalent to setting innodb_force_recovery=3 in versions earlier than MariaDB Enterprise Server 10.6.5. (MDEV-25683)

  • Galera updated to 26.4.10.

  • Debian 11 support added.

Changes in Storage Engines

Issues Fixed

Can result in data loss

Can result in a hang or crash:

Can result in unexpected behavior

Install and Upgrade

  • Running mariadb-upgrade with no 'root'@'localhost' user may fail with the message The user specified as a definer ('root'@'localhost') does not exist FATAL ERROR: Upgrade failed. (MDEV-26925)

  • On CentOS 7, auth_pam_tool has incorrect permissions. (MDEV-26380)

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.5-2 is provided for:

  • CentOS 7 (x86_64)

  • Debian 9 (x86_64 / ARM64)

  • Debian 10 (x86_64 / ARM64)

  • Debian 11 (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".