The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2025-03-12. For the latest, interactive version please visit https://mariadb.com/kb/.

Release Notes for MariaDB Enterprise Server 10.6.5-2

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.org link)CVSS base score
CVE-2022-273857.5
CVE-2021-466677.5
CVE-2022-316246.5
CVE-2021-466625.5

Notable Changes

  • Galera updated to 26.4.10.
  • Debian 11 support added.
  • 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 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.
  • 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: (MDEV-25683)
    • 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.

Issues Fixed

Can result in data loss

  • InnoDB tables with ROW_FORMAT=COMPRESSED could be corrupted. (MENT-1367)

Can result in a hang or crash

  • Resolving aggregate functions that are used in a view can cause in a crash. (MDEV-24454)
  • 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)
  • 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)
  • InnoDB causes server crash when a table is converted from utf8mb3 to utf8mb4 (MDEV-25951)
  • On 64-bit Microsoft Windows when MyISAM accesses key buffer and key_buffer_size is greater than 4 GB, the server crashes. (MDEV-26533)
  • InnoDB persistent statistics causes server to hang. (MDEV-15020)
  • On an InnoDB table, when a DDL statement rebuilds the parent table in a foreign key relationship, a concurrent INSERT into the child table sometimes causes a crash. (MDEV-26554)
  • On an InnoDB table, when the server crashes or is killed while a DROP TABLE or table-rebuilding ALTER TABLE operation is being executed, InnoDB causes a server crash during crash recovery, which occurs after the server has restarted. (MENT-1368)
  • InnoDB sometimes causes server crash during ALTER TABLE .. IMPORT TABLESPACE when the imported tablespace contains columns that have been instantly reordered or dropped. The MariaDB error log contains the following error message: (MDEV-18543)
    Schema mismatch (Index field name newcol doesn't match tablespace metadata field name name for field position...

Can result in unexpected behavior

  • skip_networking does not prevent replication. (MDEV-24969)
  • Memory leak with row-based replication can lead to high memory usage on replica servers. (MDEV-26712)
  • 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)
  • Spider does not work correctly for UDF and stored functions if used in a query's WHERE conditions. (MDEV-26545)
  • If an INVISIBLE column has a computed default value, an INSERT statement that doesn't specify a value for the column causes the default value to be ignored. (MDEV-25891)
  • Password validation plugins (including simple_password_check) cause a user's existing password hash to be removed from the server's in-memory privilege cache when the user tries to change their password to an invalid password. (MDEV-26650)
  • InnoDB's adaptive purging can decrease throughput by starving user threads after dict_sys.mutex removal. (MDEV-26356)
  • The server in some cases shows decreasing performance with notes
    InnoDB: Cannot close file... in the error log. This issue occurs only when open-files-limit is reached and a log-checkpoint is triggered. (MDEV-25215)
  • XA PREPARE sometimes leads to lock wait timeouts on replica servers. (MDEV-26682)
  • Replica server does not invalidate query cache after replicating table updates. (MENT-1360)
  • MariaDB Enterprise Cluster, powered by Galera, shows inconsistent values for wsrep_apply_window and wsrep_commit_window when comparing performance_schema.galera_group_members and information_schema.GLOBAL_STATUS (MENT-1333)
  • MariaDB Enterprise Cluster incorrectly streams XA transactions when wsrep_trx_fragment_unit=statements is set, which causes errors when the fragment is applied. (MENT-1344)
  • MariaDB Enterprise Backup does not write the current GTID to xtrabackup_binlog_info when a MariaDB Enterprise Cluster node is backed up and wsrep_gtid_mode=ON is set. (MDEV-26237)
  • On CentOS 7, auth_pam_tool has incorrect permissions. (MDEV-26380)
  • 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)

Changes in Storage Engines

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".

Installation Instructions

Upgrade Instructions

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.