Release Notes for MariaDB Enterprise Server 10.3.37-18

MariaDB Enterprise Server 10.3.37-18 is a maintenance release of 10.3. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.37-18 was released on 2022-12-21.

Notable Changes

• The view shows details about the InnoDB temporary tablespace, which is the tablespace where InnoDB temporary tables are stored. (MDEV-29479)

  • Starting with this release, the details about the InnoDB temporary tablespace can be shown by querying for the name innodb_temporary:

• When a table's default collation is set to the default collation for the table's character set, shows the COLLATE clause. ()

  • In previous releases, MariaDB Enterprise Server reduced the size of SHOW CREATE TABLE output by excluding the COLLATE clause if the table's default collation was set to the default collation for the table's character set.

Issues Fixed

Can result in data loss

• When a column is renamed in a partitioned table with using the , the table can be corrupted. ()

• When the InnoDB storage engine performs change buffer operations, the I can overflow, which can cause table corruption. (MENT-1661, )

Can result in a hang or crash

• When a query contains an IN/ALL/ANY predicand and the subquery contains a GROUP BY clause with an IN/ALL/ANY predicand with a single-value subquery as the left operand, the server can crash. ()

• If an InnoDB table contains a foreign key constraint and the child table's DATABASE_NAME/TABLE_NAME.ibd is longer than 330 characters, when the parent table is renamed, the server can crash. ()

• When the global value of the is changed dynamically on a node that does not have MariaDB Enterprise Cluster (powered by Galera) configured, the server crashes when DDL is executed in TOI mode. ()

  • In previous releases, the following statements could cause a crash on a node without an Enterprise Cluster configured:

Can result in unexpected behavior

• In the presence of replication filters, revoking privileges from a non-existing user on a primary (master) breaks replication on the replica (slave). ()

• When is set on a replica node, the replica node does not skip replicated . ()

• When a Spider table has a prefix index, query results can be incorrect. ()

• InnoDB can extend tablespace files when additional capacity is not required. (

• When an InnoDB table contains virtual generated columns that are indexed, InnoDB fails to purge secondary index records. ()

• When using the InnoDB adaptive hash index, non-locking reads can return wrong results due to a potential ACID violation. (, , )

• When is used on a temporary table, an empty result set is returned. ()

• When a sequence is used as the default value in a table, rows inserted by an

Related to install and upgrade

• When MyRocks is installed from a Debian package, the rocksdb.cnf configuration file gets installed to /etc/mysql/mariadb.conf.d/ instead of /etc/mysql/conf.d/. ()

Platforms

In alignment with the , MariaDB Enterprise Server 10.3.37-18 is provided for:

• CentOS 7 (x86_64)

• Debian 10 (x86_64, ARM64)

• Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

• Red Hat Enterprise Linux 7 (x86_64)

Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see .

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}