Release dates for all upcoming MariaDB Server releases can be found on Jira.

MariaDB Server Development Release

MariaDB Server Rolling Release

MariaDB Server Long-Term Release

MariaDB Connectors

See Also

• . The table on the right contains dates for the next MariaDB server releases

Overview

and MariaDB Community Server support data-in-transit encryption, which secures data transmitted over the network. The server and clients encrypt data using the Transport Layer Security (TLS) protocol, a newer version of the Secure Socket Layer (SSL) protocol.

is available on the MariaDB documentation.

This release of MariaDB Enterprise Server 10.5 is an internal release.

MariaDB Enterprise Server 10.5.4-1 was released on 2020-07-16.

This release substantially aligns to the features made available in MariaDB Enterprise Server 10.5.4-2.

About

enables a predictable development and operations experience through an . This enterprise lifecycle incorporates optimized builds, predictable release behavior, and vendor support.

Minor and maintenance releases of MariaDB Enterprise Server incorporate bug fixes and security fixes. Like all releases of MariaDB Enterprise Server, minor and maintenance releases undergo extensive QA testing before release to customers.

The frequency of minor and maintenance releases is variable. Minor or maintenance releases occur for each release series at least quarterly. A portion of minor and maintenance releases occur on a pre-scheduled basis. Additional releases may be added by MariaDB Corporation between scheduled release dates to manage the flow of change or to address specific defects.

Next Scheduled Releases

Upcoming minor or maintenance releases are scheduled for:

• 2026-03-16

• 2026-06-15

• 2026-09-14

• 2026-12-14

Prior Releases

See the list of

Obtaining MariaDB Enterprise Server

MariaDB Enterprise Server is available to MariaDB subscription customers via the .

If you are not yet a MariaDB subscription customer, for more information.

MariaDB Enterprise Server binary and source code is delivered over secure protocols from MariaDB Corporation-maintained infrastructure.

When to Use the AWS KMS Encryption Plugin?

The AWS KMS Encryption Plugin (aws_key_management) allows you to:

• Use to manage MariaDB's encryption keys.

• Encrypt MariaDB data using those keys, including:

• Rotate encryption keys.

Additional information is available .

MariaDB Enterprise Server 10.5.19-14 has been withdrawn, and is no longer available from MariaDB package repositories.

A regression has been reported for MariaDB Enterprise Server 10.5.19-14, which results in InnoDB not freeing undo logs when they are no longer needed. This issue could cause the InnoDB system tablespace or the undo log tablespaces to grow indefinitely.

Customers who have deployed MariaDB Enterprise Server 10.5.19-14 may contact MariaDB Support for assistance or upgrade to the next maintenance release. The next maintenance release of MariaDB Enterprise Server is scheduled for 2023-06-12.

About

• Enterprise Server Lifecycle

• Enterprise Server Release Schedule

• Enterprise Server Differences

• Software Bill of Materials (SBOM)

Current Releases

Old Releases

MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability.

In addition to different release cycles, QA, etc, there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start, and also only includes features that are fully supported and maintained.

In addition to this, there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 11.4 but not in MariaDB Community Server 11.4:

Enterprise Features

• Index limit increased to 128 indexes.

• Slow master shutdown as default

  • MariaDB Enterprise Cluster (powered by Galera)

  • Enhanced Enterprise Data-at-Rest Encryption

  • XA Support

  • Non-Blocking operation for DDLs

  • TLS certificate expiration monitoring

  • SSL/TLS is enabled by default

• Dynamic resize of

• Dynamic change of threads

• Sybase SQL mode for extended aliases

Backported Features

• New, Detailed Replication Lag Representation

• New Information Schema Table For Password-Related Data

• GTID binlog events now include the thread ID

• Automatic SST user account management for Galera

• PARSEC authentication plugin

• Extending timestamp range to 2106

• Limit the size of the created disk temporary files and tables

• The Software Bill of Materials (SBOM) JSON file is generated in the downloads archive

• Vector Search capability has been added (MENT-2233)

• Segmented key cache for Aria

  • A new variable (default 1) to define the number of segments has been added. The default disables the new feature.

Overview

MariaDB Enterprise Server and MariaDB Community Server support data-at-rest encryption, which secures data on the file system. The server and storage engines encrypt data before writing and decrypt it during reads, ensuring that the data is only unencrypted when accessed directly through the server.

Encryption Plugins

Storage Engine Encryption

Replication Cache Encryption

Additional information is available on the page.

Overview

MariaDB Enterprise Server and MariaDB Community Server support , which secures data on the file system. The server and storage engines encrypt data before writes and decrypt it during reads, ensuring that the data is only unencrypted when accessed directly through the server.

In many versions of MariaDB Server, the GCache used by Galera Cluster does not support data-at-rest encryption.

However, MariaDB Enterprise Server 10.4 and later support an enterprise version of Galera 4, which adds support for encrypting the GCache.

In those versions, the GCache supports the following data-at-rest encryption features:

• The GCache can be automatically encrypted.

For more information, see the following resources:

Overview

MariaDB Enterprise Server and MariaDB Community Server support , which secures data on the file system. The server and storage engines encrypt data before writing and decrypt during reads, ensuring that the data is only unencrypted when accessed directly through the server.

They support multiple encryption plugins, which are suited for different use cases.

MariaDB publishes a Software Bill of Materials (SBOM) for each MariaDB Enterprise Server release. An SBOM lists the components that make up a build (libraries, packages, versions, licenses, and hashes); enabling customers to meet compliance requirements, perform vulnerability management, and understand supply chain risk.

About

Coverage: Core MariaDB Enterprise Server binaries and packages for each supported platform/release

Formats: CycloneDX JSON (.json)

Contents: Component names & versions, suppliers, licenses, purls/CPEs (when available), cryptographic hashes, and dependencies

Availability: SBOM files are provided alongside each release’s download artifacts in the customer portal, or from the "Software Bill of Materials (SBOM)" link on the Enterprise Server download page

Updates: A new SBOM is published for every release; compare SBOMs across versions to see component deltas

Recommended Uses

• Vulnerability management: Import the SBOM into a scanner or platform to match against advisories (e.g., OSV/CVE feeds)

• Compliance & audits: Produce component/license reports and demonstrate software composition controls

• Change analysis: Diff SBOMs between versions to identify updated/deprecated components

Viewing SBOM Files

The recommended viewer for the MariaDB SBOM files is the CycloneDX Web Tool (hosted by the CycloneDX project), which can be found at https://cyclonedx.github.io/cyclonedx-web-tool

Advantages of the CycloneDX Web Tool include:

• Our SBOM files are explicitly built for CycloneDX including upload/view functionality for both XML and JSON

• The CycloneDX Web Tool is maintained by the CycloneDX project so it aligns with the standard and will remain compatible

• The CycloneDX Web Tool works via browser so you do not need to install anything

This release of MariaDB Enterprise Server 10.5 is an internal release.

MariaDB Enterprise Server 10.5.3-1 was released on 2020-05-21.

The successor to this release is MariaDB Enterprise Server 10.5.4-2.

MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability.

MariaDB Enterprise Server enables a predictable development and operations experience through an enterprise lifecycle. This enterprise lifecycle incorporates optimized builds, predictable release behavior, and vendor support. For more information about the Enterprise Server Lifecycle .

In addition to different release cycle, QA, and etc..., there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start and also only includes features that are fully supported and maintained.

In addition to this there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 10.4 but not in MariaDB Community Server 10.4:

Enterprise Features

• Index limit increased to 128 indexes

• Slow master shutdown as default

• (powered by Galera)

Backported Features

• New option

• GTID support for MariaDB Enterprise Cluster (powered by Galera)

• Crash recovery for semi-synchronous replication

• to dump data as of a given time for system versioned tables

• JSON functions

MariaDB Enterprise Server 10.6.17-13 is a maintenance release of 10.6. This release includes a fix for a regression introduced with MariaDB Enterprise Server 10.6.17-12. Users of MariaDB Enterprise Server 10.6.17-12 are encouraged to upgrade to the latest version 10.6.17-13.

MariaDB Enterprise Server 10.6.17-13 was released on 2024-04-24.

Changes in Storage Engines

• This release incorporates MariaDB ColumnStore engine version 23.10.1.

Issues Fixed

Can result in hang or crash

• An UPDATE to a unique/primary key field can result in a server crash, if the update results in a duplicate key error message. The crash is more likely to happen for a server configuration with a lower setting than the default (299008) for --thread_stack, or when the UPDATE is executed inside of a stored function (MENT-2065)

  • For MariaDB Enterprise Server 10.6.17-12, if an update is not possible, a workaround is to increase the current setting of --thread_stack by 100k

Platforms

In alignment to the , MariaDB Enterprise Server 10.6.17-13 is provided for:

• AlmaLinux 8 (x86_64, ARM64)

• AlmaLinux 9 (x86_64, ARM64)

• CentOS 7 (x86_64)

• Debian 10 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

• Debian 12 (x86_64, ARM64)

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

• Red Hat Enterprise Linux 7 (x86_64)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 20.04 (x86_64, ARM64)

• Ubuntu 22.04 (x86_64, ARM64)

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

Installation Instructions

Upgrade Instructions

MariaDB Enterprise Server 10.4 introduces the following new features:

Enterprise Lifecycle

MariaDB Enterprise Server uses an that provides optimized builds, predictable release behavior, and vendor support.

InnoDB Instant ALTER

enables reliable and predictable schema change behavior.

Optimizer Trace

collects trace data to aid query optimization and diagnosis of query execution issues.

Temporal Data

support has been expanded from system-versioned tables to also include application-time period and bitemporal tables.

Enterprise Audit Plugin

provides support for auditing resource access to MariaDB Enterprise Server.

Enterprise Backup

enables non-blocking backups of MariaDB Enterprise Server.

Data-at-Rest Encryption

With , data is encrypted before writing to the disk and decrypted when read from disk. MariaDB Enterprise Server extends data-at-rest encryption support to include:

• Encryption of Spatial indexes

• Key rotation when encrypting the InnoDB Redo Log

• Encryption of MariaDB Enterprise Cluster's write-set cache (GCache)

MariaDB Enterprise Cluster

MariaDB Enterprise Server includes support for , which incorporates Galera Cluster 4. New features include:

• Parallel replication and improved performance when blocks of grouped transactions can be committed without conflict.

• The , to eliminate transaction limitations by fragmenting huge transactions for replication.

• Rolling upgrades to permit a smooth transition of MariaDB Cluster deployments to Galera 4 functionality by operating as a Galera 3-compatible node until all nodes are Galera 4-compatible.

Data Reliability and SQL Functionality

MariaDB Enterprise Server includes changes to improve data reliability and SQL functionality:

• System tables use the Aria storage engine, making them crash-safe.

• UNIQUE index support for the BLOB data type.

• data type validation.

• Parentheses in UNION, INTERSECT, and EXCEPT operations to control order of execution.

Enhanced Credential Management

MariaDB Enterprise Server features improvements, including:

• Ability to reload SSL certificates without server restart.

• SET PASSWORD option to specify authentication plugins.

• Improved support for authentication plugins, including the ability to set multiple authentication plugins on individual users. Also supported is fallback on internal methods, such as password authentication.

• ALTER USER option for account locking, to enable MariaDB Enterprise Server to reject all new connections for an account.

• Account blocking based on number of failed login attempts.

• Ability to set password expiration dates.

• Logging of access when passwords are ignored, e.g., for passwordless authentication by UNIX socket.

Enterprise Server Builds

MariaDB Enterprise Server incorporates enhancements that are not present in MariaDB Community Server, including

• Premium features meet enterprise scaling and operations requirements.

• Priority bug fixes are available first to enterprise customers.

• Increased the code stability through restricted release of new functionality.

• Risk reduction from untested or incompatible features through the inclusion of only features with level 3 support (engineering code-level support) from MariaDB Corporation.

• Optimized the configuration defaults.

For details on features added to enhance, harden, and secure MariaDB Enterprise Server, see the following pages:

• What's New in MariaDB Enterprise Server 11.8

• What's New in MariaDB Enterprise Server 11.4

• What's New in MariaDB Enterprise Server 10.6

Enterprise Server Releases

Releases of MariaDB Enterprise Server are predictable because,

• Major releases are delivered on a schedule.

• The minor releases are focused on small, incremental defect remediation.

• Critical fixes from newer release series are selectively backported.

• Enterprise-grade testing drives a low defect rate.

• Specific changes present in each release are communicated.

Additional information on the release cycle for MariaDB Enterprise Server can be found in MariaDB Corporation Engineering Policy.

Upcoming Minor and Maintenance Releases

Planned releases of MariaDB Enterprise Server are scheduled.

Obtaining MariaDB Enterprise Server

MariaDB Enterprise Server is available to MariaDB subscription customers via the MariaDB Customer Portal.

If you are not yet a MariaDB subscription customer, contact MariaDB Corporation for more information.

MariaDB Enterprise Server binary and source code is delivered over secure protocols from MariaDB Corporation-maintained infrastructure as detailed in the Deployment Guide.

Enterprise Server Release Identifiers

Releases of MariaDB Enterprise Server are given an identifier such as 'MariaDB Enterprise Server 10.5.8-5,' whose components are,

• The product name (MariaDB Enterprise Server).

• Release series (10.5, spoken "ten-five").

• The point release of MariaDB Community Server used as the base of this Enterprise Server release (.8, spoken "ten-five-eight").

• The release postfix of MariaDB Enterprise Server starts with '-1' and is incremented for subsequent releases in that release series (-5, spoken "ten-five-eight-dash-five").

• On the Debian and Ubuntu platforms, the release postfix contains a period instead of a dash, such that release postfixes start with .1 and increment for subsequent releases in that release series (.5, spoken "ten-five-eight-dot-five").

Additional information on the release numbering for MariaDB Enterprise Server can be found in MariaDB Corporation Engineering Policy.

Enterprise Server Support

MariaDB Corporation offers vendor support for MariaDB Enterprise Server, including,

• Customer support as detailed in the Subscription Services Policy

• Professional services, including migration services, remote DBA services, and consulting

• Customer communications, managed via the MariaDB Customer Portal

• Training

• Documentation

MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability.

MariaDB Enterprise Server enables a predictable development and operations experience through an enterprise lifecycle. This enterprise lifecycle incorporates optimized builds, predictable release behavior, and vendor support.

In addition to different release cycle, QA, and etc..., there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start and also only includes features that are fully supported and maintained.

In addition to this there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 10.5 but not in MariaDB Community Server 10.5:

Enterprise Features

• Index limit increased to 128 indexes

• Slow master shutdown as default

• (powered by Galera)

  • Enhanced Enterprise Data-at-Rest Encryption

  • Non-Blocking operation for DDLs

• Dynamic resize of

• Dynamic change of threads

• Sybase SQL mode for extended aliases

Backported Features

• Crash recovery for semi-synchronous replication

• to dump data as of a given time for system versioned tables

• JSON functions

• Option for SQL thread to limit maximum execution time per query

MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability. For more information about MariaDB Enterprise Server in general please look here.

In addition to different release cycle, QA, and etc..., there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start and also only includes features that are fully supported and maintained.

In addition to this there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 10.6 but not in MariaDB Community Server 10.6:

Enterprise Features

• Index limit increased to 128 indexes

• Slow master shutdown as default

• MariaDB Enterprise Cluster (powered by Galera)

  • Enhanced Enterprise Data-at-Rest Encryption

  • XA Support

  • Non-Blocking operation for DDLs

  • TLS certificate expiration monitoring

  • SSL/TLS enabled by default

• Dynamic resize of

• Dynamic change of threads

• Sybase SQL mode for extended aliases

Backported Features

• to dump data as of a given time for system versioned tables

• JSON functions

• CONVERT_PARTITION / CONVERT_TABLE

• Option for SQL thread to limit maximum execution time per query

• Allow to be changed after database creation

• Make the optimizer handle UCASE(varchar_col)=...

• Easier way to retrieve all users that have privileges on a specific table

• Make dynamic

• Add timezone information to

• option for innodb_data_file_path system variable

• New, Detailed Replication Lag Representation

• New Information Schema Table For Password Related Data

• GTID binlog events now include the thread ID

• Software Bill of Materials (SBOM) JSON file generates in the downloads archive.

Release date: 8 Sep 2025

MariaDB Enterprise Server 10.6.23-19 is a maintenance release of . This release includes a variety of fixes.

Changes in Storage Engines

• This release incorporates MariaDB ColumnStore engine version 23.10.6

Notable changes

• updated to

Issues Fixed

Can result in data loss

• Adding (with ALTER TABLE) a UNIQUE constraint that is USING HASH to a table with foreign keys could've caused the table to become corrupted. ()

Can result in hang or crash

• Server crashes in do_mark_index_columns instead of ER_DUP_ENTRY on partitioned table ()

• CREATE OR REPLACE with self-referencing CHECK hangs forever, cannot be killed ()

• Segfault on INTERSECT ALL with UNION in Oracle mode ()

• This commit fixes a bug where Aria tables are used in (master->slave1->slave2) and a backup is taken on slave2. In this case it is possible that the replication position in the backup, stored in mysql.gtid_slave_pos, will be wrong. This will lead to replication errors if one is trying to use the backup as a new slave. ()

• Fatal InnoDB error: Unknown error Temp file write failure ()

• semi sync makes the master unresponsive when a replica is stopped ()

• json_extract crashes in Item_func_json_extract::read_json ()

• Inconsistency detected - create sequence ()

• Replica stops with "Found invalid event in binary log" ()

Can result in unexpected behaviour

• ALTER TABLE require ALTER privilege on sequence from DEFAULT value expression ()

• In certain cases privileges on sequences were too restrictive, for example, SELECT on a table might've erroneously required INSERT privilege on a sequences ()

• AUTO_INCREMENT leads to non-serializable on results ()

• UNIQUE constraint that was USING HASH and UNIQUE constrant WITHOUT OVERLAPS could be violated under heavy load in READ COMMITTED transaction isolation mode. ()

• UNIQUE KEY USING HASH accepting duplicate records ()

Changelog

For the complete list of changes in this release, see the .

Platforms

In alignment to the , MariaDB Enterprise Server 10.6.22-18 is provided for:

• AlmaLinux 8 (x86_64, ARM64)

• AlmaLinux 9 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

• Debian 12 (x86_64, ARM64)

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

• Oracle Linux 8 (x86_64, ARM64)

• Oracle Linux 9 (x86_64, ARM64)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64, PPC64LE)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 22.04 (x86_64, ARM64)

• Ubuntu 24.04 (x86_64, ARM64)

• Red Hat UBI 8 (x86_64, ARM64)

  • Red Hat UBI 8 is part of the Enterprise Server Docker Image. It does not support MariaDB Enterprise Cluster (Galera) or MariaDB ColumnStore.

Some components of MariaDB Enterprise Server are supported on a subset of platforms. See for details.

Installation Instructions

Upgrade Instructions

This fourth release of 10.5 is a hotfix release to address a CVE which has been rated "critical" using the criteria defined in the .

MariaDB Enterprise Server 10.5.6-4 was released on 2020-10-07.

Fixed Security Vulnerabilities

#1: MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the for details.

Changes in Storage Engines

• This release originally included .

• This release has been updated to include on 2020-11-09.

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.6-4 is provided for:

• AlmaLinux 8 (x86_64, ARM64)

• AlmaLinux 9 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

• Debian 12 (x86_64, ARM64)

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

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 20.04 (x86_64, ARM64)

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

Installation Instructions

Upgrade Instructions

This ninth release of 10.4 is a hotfix release to address a CVE which has been rated "critical" using the criteria defined in the .

MariaDB Enterprise Server 10.4.15-9 was released on 2020-10-07.

Fixed Security Vulnerabilities

#1: MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the for details.

Platforms

In alignment with the , MariaDB Enterprise Server 10.4.15-9 is provided for:

• Red Hat Enterprise Linux 8

• Red Hat Enterprise Linux 7

• Red Hat Enterprise Linux 6

• CentOS 8

• CentOS 7

• CentOS 6

• Debian 10

• Debian 9

• Debian 8

• SUSE Linux Enterprise Server 15

• SUSE Linux Enterprise Server 12

• Ubuntu 20.04

• Ubuntu 18.04

• Ubuntu 16.04

• Microsoft Windows

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

Note

CentOS 6, Debian 8, and Red Hat Enterprise Linux 6 are no longer supported as per the . Older releases are available from the . Instructions for installation are included as a README file within the download.

Installation Instructions

Upgrade Instructions

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

MariaDB Enterprise Server 10.4.34-24 is a maintenance release of . This release includes a variety of fixes.

MariaDB Enterprise Server 10.4.34-24 was released on 2024-06-11.

Notable Changes

• Galera has been updated to 26.4.18

  • The GCS protocol version has been changed, preventing a downgrade of individual nodes of a MariaDB Enterprise Cluster

Issues Fixed

Can result in data loss

• With --gtid-ignore-duplicate set, a transaction can be double-applied from another replication source if applying the transaction from the initial source required retrying in parallel execution. (MDEV-33475)

• Backups of server with innodb_encrypt_tables=1 can become corrupted in mariadb-backup --prepare (MDEV-33334)

• Galera-replicated events can, in some cases, contain the wrong time when versioning is used (MDEV-18590)

Can result in a hang or a crash

• Using current MariaDB Enterprise Backup against an older server can result in a crash, as the system variable @@aria_log_dir_path does not exist (MDEV-31251)

• For encrypted table spaces, an ALTER operation can hang when an encryption thread works on the same tablespace (MDEV-33770)

• EXPLAIN statement that uses a subquery which has a query plan that A) will examine less than @@expensive_subquery_limit rows and B) will use the join buffer, could cause a crash. (MDEV-21102)

• MariaDB Enterprise Backup fails with the following error message if the prepare step of the backup encounters a data directory, which happens to store wsrep xid position in TRX SYS page: (MDEV-33540)

InnoDB: Crash recovery is broken due to insufficient innodb_log_file_size

Can result in unexpected behavior

• Spider/ODBC passed double quotes for names, in ANSI style (MENT-958)

• Default charset doesn't work with the PHP MySQLi extension (MDEV-32975)

• Spider returns parsing failure on valid left join select by translating the on expression to () (MDEV-33679)

• Original IP not shown in network-related error messages when proxy_protocol is in use (MDEV-33506)

• Incorrect DEFAULT expression evaluated in UPDATE (MDEV-33790)

Related to performance

• Table is getting rebuilt with ALTER TABLE ADD COLUMN, although it should be an instant operation, not requiring a rebuild (MDEV-33214)

Changelog

• For the complete list of changes in this release, see the changelog.

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.4.34-24 is provided for:

• CentOS 7 (x86_64)

• Debian 10 (x86_64)

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

• Red Hat Enterprise Linux 7 (x86_64)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 20.04 (x86_64, ARM64)

Some of the components of MariaDB Enterprise Server are supported on a subset of platforms. See MariaDB Engineering Policies for details.

Installation Instructions

Upgrade Instructions

MariaDB Enterprise Server 10.5.27-21 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.27-21 was released on 2024-12-10.

Notable Changes

• A new parameter --quick-max-column-width is now available in the mariadb client to limit the field width when used with the --quick mode (MDEV-34704)

Changes in Storage Engines

• This release incorporates MariaDB ColumnStore engine version 5.6.8

Issues Fixed

Can result in data loss

• Using group_concat with a compressed or GIS column can lead to a server crash and potential data corruption for users performing group_concat operations on tables containing these data types (MDEV-16699)

Can result in hang or crash

• A query could cause a crash if it has a HAVING clause with a construct tblX.column=column_or_constant and the optimizer was able to infer that table tblX is a constant table. Note that HAVING clause may be from the original query or may come from ) (MDEV-23983)

• Calling a UDF for the engine SPIDER results in a crash if the SPIDER storage engine plugin could not be loaded (MDEV-34682)

• Under Windows Subsystem for Linux, InnoDB crashes on ALTER TABLE or OPTIMIZE TABLE (MDEV-34938)

• Server crashes when setting wsrep_cluster_address after adding invalid value to wsrep_allowlist table (MDEV-31173)

• mariadbd hangs on startup when --init-file target does not exist (MDEV-34814)

• Possible server crash in cases where the function DEFAULT() is part of a query (MDEV-35276)

• Possible unique hash index corruption for system-versioned tables after DML including DELETE HISTORY statement. This can lead to data corruption, crashes, and incorrect query results (MDEV-33470)

  • Possible error log entry

[ERROR] InnoDB: Record in index `c` of table `test`.`t` was not found on update...

• In some situations, where a MariaDB Enterprise cluster (Galera) node crashes, some threads are still working. This is visible via the error log, which is still getting errors written by the node. As the node stops interacting correctly with other cluster nodes and is blocking them from taking over the primary state, the whole cluster hangs (MDEV-32363)

Can result in unexpected behavior

• When a user runs mariadb-binlog with --stop-position, they would expect the output to contain events up to that event. If the output did not contain events up to that event, this may result in various unexpected behaviors, e.g., an incomplete database state if they piped the output to the mariadb client and expected certain transactions to have executed in the database, yet never were run (MDEV-27037)

• Changing a data type of a field used in a foreign key constraint fails with Error "Cannot change column '...': used in a foreign key constraint '...'" (MDEV-34392)

  • This ALTER only fails if the type of field is changed in a multi-ALTER statement, where types of other fields are changed with the ALTER

• Creation of a view with UNION and SELECT ... FOR UPDATE in the definition fails with error "ER_PARSE_ERROR (1064): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near..." (MDEV-29537)

• INSERT...SELECT on MyISAM or ARIA tables are replicated by MariaDB Enterprise Cluster (Galera) (MDEV-34647)

• SELECT MIN on Spider table returns more rows than expected (MDEV-26345)

• Can't selectively restore sequences using innodb tables from backup (MDEV-32350)

• LOAD DATA INFILE with geometry data fails (MDEV-34883)

• Executing an UPDATE statement in prepared statement mode having positional parameter bound with an array can result in an incorrect number of updated rows in case there is a BEFORE UPDATE trigger that executes yet another UPDATE statement to change a table (MDEV-34718)

• Recovery fails to note some log corruption, resulting in "log sequence number in the future" error messages, and possibly adds more corruption (MDEV-34802)

  • When log corruption is noted, the server can now only be started when using the option innodb_force_recovery

• Unexpected error "Row size too large (> 8123)..." for a correct INSERT after a instantly dropped BLOB column (MDEV-35122)

• Wrong binlog timestamps on secondary nodes of MariaDB Enterprise Cluster (MENT-2164)

• When the MariaDB Enterprise Audit Plugin is configured to log ACL queries, a statement CREATE USER .. IDENTIFIED VIA ed25519 USING PASSWORD(...) is logged including the password (MENT-2181)

• When the MariaDB Enterprise Audit Plugin is configured to log ACL queries, passwords are masked for CREATE USER .. IDENTIFIED BY, but not for CREATE OR REPLACE USER, or SET STATEMENT ... FOR CREATE USER (MENT-2188)

Related to performance

• Unnecessary copying of log records by MariaDB Enterprise Backup when further transaction commits are blocked by BACKUP STAGE BLOCK_COMMIT (MENT-2133)

  • It also would cause further effort of rolling back incomplete transactions after the backup is restored

• Aria internal temporary tables unnecessarily write all changed blocks to disk when the table is closed at end of query (MENT-2182)

Changelog

For the complete list of changes in this release, see the changelog.

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.5.27-21 is provided for:

• AlmaLinux 8 (x86_64, ARM64)

• AlmaLinux 9 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

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

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (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".

nstallation Instructions

• MariaDB Enterprise Server 10.5

• 10

• Enterprise Spider Sharded Topology with MariaDB Enterprise Server 10.5

• Enterprise Spider Federated Topology with MariaDB Enterprise Server 10.5

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.4.28-19

MariaDB Enterprise Server 10.4.28-19 is a maintenance release of . This release includes a variety of fixes.

MariaDB Enterprise Server 10.4.28-19 was released on 2023-03-13.

Notable Changes

• Output for the function has been optimized to reduce the number of lines needed. (MDEV-19160)

  • For compatibility, has been added as an alias to JSON_DETAILED(). (MDEV-19160)

• This release incorporates Galera library version 26.4.14

Issues Fixed

Can result in data loss

• When executing a DELETE or UPDATE with a subselect, the server can crash. (MDEV-10087)

• When performing an incremental backup, MariaDB Enterprise Backup does not reflect databases that have been dropped and recreated. (MDEV-23335)

Can result in a hang or crash

• When DELETE HISTORY is executed for a system versioned table with a full-text index, the server can crash. (MDEV-25004)

• When an ALTER TABLE statement causes InnoDB to rebuild a table with a spatial index, the server can crash. (MDEV-29856)

• When using SPIDER with SPIDER_DIRECT_SQL and spider_udf_ds_use_real_table=1, the server can crash. (MDEV-29855)

• When executing REPLACE INTO ... PARTITION(...), the server can crash. (MDEV-29636)

• Galera SST doesn't properly handle undo* files from InnoDB. As a result, SST may terminate incorrectly when --innodb-undo-tablespaces is set to 3 or more. (MDEV-30157)

• With a query containing nested WINDOW clauses, the server can crash. (MDEV-30052)

• When executing a SELECT from a complex view with a WHERE clause and with the setting derived_merge=on, the server can crash. (MDEV-30081)

• Infinite sequence of recursive calls when processing embedded CTE, when such a reference has the same table name as the name of the CTE. (MDEV-30248)

• A deadlock between InnoDB statistics updates and BLOB insert can result in a server hang. (MDEV-29883)

• GET_LOCK() / RELEASE_LOCK() calls are not rejected by MariaDB Enterprise Cluster. (MDEV-27115)

• With a cluster-wide conflict, MariaDB Enterprise Cluster can hang if a binlog purging is running (such as in the case that binlog expiration is configured). (MDEV-29512)

• mariadbd hangs when running with --wsrep-recover and --plugin-load-add=ha_spider.so options. (MDEV-30370)

Can result in unexpected behavior

• log_query_not_using_indexes=OFF is ignored when log_slow_filter is an empty string. (MDEV-21187)

• MariaDB Enterprise Backup returns with an error when the option --galera-info is used for creating a backup of a MariaDB Server instance, which is not a MariaDB Enterprise Cluster node. Failed to get master wsrep state from SHOW STATUS (MDEV-30293)

• When querying a table with virtual generated columns using full text search, these columns are not generated and are always NULL in the result set. (MDEV-29169)

• Identifiers are not quoted for the output of SHOW GRANTS. Using the result to execute the grant statement results in a syntax error if reserved keywords are used. (MDEV-30056)

• Spider table with CHARSET utf32/utf16/ucs2 tries to set client CHARSET to unsupported value. (MDEV-29562)

• Incorrect results are returned when using STDDEV_SAMP() with a view. (MDEV-19071)

• A spurious error can be generated: ERROR 1292 (22007) at line 15: Truncated incorrect DECIMAL value:

(MDEV-30342)

• When running mariadb-binlog using the option --verbose, cannot read row events with compressed columns: Error: Don't know how to handle column type:... (MDEV-25277)

• Incorrect results are returned with outer join, merged derived table, and view. (MDEV-28602)

• Some DDL, such as ANALYZE, can be completed out of order on parallel replicas. (MDEV-30323)

• seconds_behind_master is incorrect for delayed parallel replicas. (MDEV-29639)

Related to install and upgrade

• APT reports the message: dpkg: warning: downgrading galera-4 from 26.4.12-buster to 26.4.12-bullseye ([MDEV-29392](https://jira.mariadb.org/browse/MDEV-29392))

Interface Changes

• function added.

Platforms

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.4.28-19 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)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64 Red Hat Enterprise Linux 8 packages)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (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

MariaDB Enterprise Server 10.5.29-23 is a maintenance release of 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.29-23 was released on 11 Jun 2025.

Fixed Security Vulnerabilities

Changes in Storage Engines

• This release incorporates MariaDB ColumnStore engine version 5.6.9.

Notable changes

• MariaDB effectively running as root CAP_DAC_OVERRIDE ()

• my_getopt compares option names case sensitively ()

• updated to

Issues Fixed

Can result in data loss

• Assertion InnoDB searching row in wrong partition for multiple system versioned DELETE with same timestamp and same multistatement transaction ()

Can result in hang or crash

• ALTER TABLE…SEQUENCE does not work correctly with InnoDB ()

• Server aborts while deleting the record in spatial index ()

• Upgrades fail on Windows ()

• Field pointer may be uninitialized in fill_record ()

• Incorrect undo logging for indexes on virtual columns whose index ID does not fit in 32 bits ()

• With wsrep_ignore_apply_errors = 0, the node crashes due to assertion thd->is_error() failed in Sql_cmd_dml::prepare(), shown in the logs ()

• In some cases, if there are MDL locks (for example, when LOCK TABLE is executed), a node could get stuck in the system thread due to incorrect handling of metadata locks (MDL) in server code when a transaction was BF aborted. ()

• Regression after the fix for - sometimes the server crashes with an assertion in wsrep::transaction::before_rollback(), for example when using OPTIMIZE TABLE on an ARIA table with wsrep_osu_method=RSU. ()

• SST failure occurs when gtid_strict_mode is enabled under high load, such as OLTP load is active on the primary node. A typical symptom of this error is the presence of the diagnostic "[ERROR] mariadbd: Error writing file 'binlog'", in the debug version it is also possible to crash on assertion in the wsrep::transaction::before_rollback() function with the message "Assertion `state() == s_executing || state() == s_preparing || state() == s_prepared || state() == s_must_abort || state() == s_aborting || state() == s_cert_failed || state() == s_must_replay' failed". ()

• In Galera, creating sequence with a small cache leads to signal 6 error: [ERROR] WSREP: FSM: no such a transition REPLICATING -> COMMITTED. ()

• Under high load wsrep internal thread may terminate due to memory pressure conditions, but this is not a crash, however in debug version user may encounter assertion in wsrep_to_isolation_begin() function with following message: "int wsrep_to_isolation_begin(THD*, const char*, const char*, const TABLE_LIST*, const Alter_info*, const key_array*, const HA_CREATE_INFO*): Assertion `(0)' failed." ()

• Assertion `commit_trx' failed in innobase_commit() (ha_innodb.cc). An INSERT with sql_log_bin=0 is still replicated in Galera (per ), despite binary logging being disabled. This results in a partial binlog bypass, requiring a two-phase commit (2PC). During 2PC, the INSERT is first prepared (entering the PREPARED state in InnoDB), and on commit, the new assertion from fails, causing a crash with "Assertion 'commit_trx' failed" in logs. ()

• When a sequence is used and inserts run in parallel on multiple Galera nodes, a transaction may be aborted after passing certification. If it then attempts to roll back, the binlog statement cache—which includes reserved sequence values—may be written prematurely. This causes a crash with the diagnostic "WSREP: FSM: no such a transition REPLICATING -> COMMITTED" in the logs, as the transaction is supposed to replay and only write to the binlog during the final commit. ()

• corruption when query cache cannot allocate block ()

• Stack looping and SIGSEGV in Item_args::walk_args on UPDATE ()

• Server crash in find_field_in_tables, Assertion `name' failed in find_field_in_table_ref ()

• Long server_audit_file_path causes buffer overflow ()

• Server crash when inserting from derived table containing insert target table ()

Can result in unexpected behaviour

• Segfault on concurrent ALTER and SELECT for partitioned table ()

• ST_PointFromWKB ignores SRID argument and always creates the POINT with 0 for it's SRID ()

• mariadb-dump used wrong quoting character ()

• After a corrupted table on one node triggers the cluster to vote to evict a node that failed a transaction, the current master can’t commit any more and hangs. (, MENT-2081)

• intended to fix spider wrapper so that it is case insensitive, among other things. However that fix was incomplete, as the udf spider_direct_sql may still require case sensitivity. fixes this. ()

• Creating partitioned tables is disallowed when wsrep_osu_method=TOI and wsrep_strict_ddl=ON, preventing alteration or deletion of partitioned tables. ()

• Attempting to create a CONNECT engine table results in "non-InnoDB sequences in Galera cluster" error message in logs due to an incorrect engine check. ()

• MariaDB Backup returns with an error like "Error on file ./test/t1#P#p513.MYD open during `test`.`t1` table copy for partitioned MyISAM tables when running out of file handles (MENT-2089)

• User without any privileges to a sequence can read from it and modify it via column default ()

• User has unauthorized access to a sequence through a view with security invoker ()

Unexpected results

• The untested ha_spider::index_first_internal constructs broken queries ()

• Wrong results from tables with a single record and an aggregate ()

• Unexpected error 1264 'Out of Range Value for Column' when inserting into ... select ... from a spider table ()

• group by handler missing constant fields when selecting from a view ()

• Tests calling the udf spider_copy_tables fail with --view-protocol ()

Changelog

For the complete list of changes in this release, see the .

Platforms

In alignment to the , MariaDB Enterprise Server 10.5.28-22 is provided for:

• AlmaLinux 8 (x86_64, ARM64)

• AlmaLinux 9 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

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

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 20.04 (x86_64, ARM64)

• Red Hat UBI 8 (x86_64, ARM64)

  • Red Hat UBI 8 is part of the Enterprise Server Docker Image. It does not support MariaDB Enterprise Cluster (Galera) or MariaDB ColumnStore.

Some components of MariaDB Enterprise Server are supported on a subset of platforms. See for details.

This fifth release of 10.4 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.4.11-5 was released on 2020-01-06.

Notable Changes

• no longer sends unnecessary warnings to the error log about maximum row size for DDL statements when and ()

• Redundant writes to the redo log have been removed. ()

• The default for the plugin load option plugin-maturity is now stable (MENT-240)

• and the MariaDB Audit plugin trace now add the user who initiated statements with the DELAYED option. In previous versions a system user was added. (MENT-237)

• MariaDB ColumnStore, a columnar storage engine, is now included with MariaDB Enterprise Server 10.4. Specific details on this component may be found in the .

• no longer permits to be set to SYSLOG on Microsoft Windows. (MENT-258)

Issues Fixed

Can result in data loss

• A table could not be loaded after an instant ALTER ... ADD COLUMN or ALTER ... DROP COLUMN, if the primary key is a CHAR column with variable-length encoding like UTF8 ()

• In rare conditions commits could be applied in the wrong order if the replica is running in optimistic mode. ()

Can result in a hang or crash

• Primary (master) could crash when it executes and a replica (slave) reconnects having reset its connection status with the primary (e.g., CHANGE MASTER TO MASTER_USE_GTID = slave_pos). (MENT-19376)

• "Out of memory" error could occur when accessing partitioned tables. ()

• A crash could occur when ADD PRIMARY KEY was executed by a connection just after another connection issued an instant ADD COLUMN to the same table and if DMLs were executed at the same time. ()

• A crash could occur when rowid filtering optimization is enabled using ()

Can result in unexpected behavior

• Client received error SEC_E_INVALID_TOKEN when SSL is used and connecting to MariaDB Enterprise Server running on Microsoft Windows. ()

• The restore of tables was not always possible if MariaDB Backup was using the parameters --incremental ()

• An incomplete result set was returned when was too small. ()

• A query with system versioning filters did not show an error when executed on not . ()

• erroneously reported error "Found a misplaced row" for with history partition. ()

• An instant operation could fail when adding a column and changing the collation on a non-indexed column. ()

Interface Changes

• None.

Platforms

In alignment with the , MariaDB Enterprise Server 10.4.11-5 is provided for:

• Red Hat Enterprise Linux 8

• Red Hat Enterprise Linux 7

• Red Hat Enterprise Linux 6

• CentOS 8

• CentOS 7

• CentOS 6

• Ubuntu 18.04

• Ubuntu 16.04

• Debian 10

• Debian 9

• Debian 8

• SUSE Linux Enterprise Server 15

• SUSE Linux Enterprise Server 12

• Microsoft Windows

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

Note

CentOS 6, Debian 8, and Red Hat Enterprise Linux 6 are no longer supported as per the . Older releases are available from the . Instructions for installation are included as a README file within the download.

Installation Instructions

Upgrade Instructions

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

This fourth release of 10.4 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.4.10-4 was released on 2019-11-18.

Fixed Security Vulnerabilities

Notable Changes

• New option innodb_change_buffer_dump added to Debug builds. This option dumps the contents of the change buffer to the server error log at startup. This is useful when a slow shutdown cannot be performed successfully. ()

• Eliminated unnecessary logging of warnings to the error log regarding maximum row size for DML statements which should be present only for DDL operations. (MENT-454)

• Improved [[]] error logging to explain that GCache recovery is not possible when GCache encryption is enabled. (MENT-373)

Issues Fixed

Can result in data loss

• ... could overwrite binary logs if certain conditions were present. () Conditions which must be present to trigger this bug:

  • is executed on the MariaDB Server host, and

  • Configuration files from the master are used, and

  • Configuration files enable binary logging

If unable to upgrade to MariaDB Enterprise Server 10.4.10-4, where this bug is fixed, a workaround is available: use the --defaults option to to avoid the bug-triggering conditions by specifying a different configuration file.

Can result in a hang or crash

• Prior removal of a FULLTEXT index from an table can cause a hang on startup. ()

• Removal of a FULLTEXT index from an table can cause a hang. ()

• Change to a table containing a FULLTEXT index can cause Server to become unresponsive. ()

• Removal of a virtual column used by an index can result in a crash. (MENT-434)

• , , or on an table can cause Server to become unresponsive. ()

• INSTANT ADD COLUMN on an table which includes a OREIGN KEY definition can result in a crash. (MENT-435)

• INSTANT column DROP or column reorder can result in a crash. Server restart can also crash unless is set to E2E or greater. ()

Can result in unexpected behavior

• Unnecessary logging of warnings to the error log regarding maximum row size for DML statements which should be present only for DDL operations. (MENT-454)

• After server restart, a using a FULLTEXT index on tables can fail to return some data. ()

• and MariaDB Backup, when using mbstream, recreated xtrabackup_info in the same directory as the backup file. Repeated extract of the backup could fail. ()

• mysqld_multi.sh script could not be launched and returned a syntax error. (MENT-433)

• Though not supported on Microsoft Windows, the system variable for the Audit plugin accepted a SYSLOG value. ()

• FOREIGN KEY constraints have been ignored during when parent table is . ()

• from child table with FOREIGN KEY was not possible when the table is . ()

• cannot perform GCache recovery when GCache encryption is enabled, but no warning was sent to the error log. (MENT-373)

Related to install and upgrade

• Installing MariaDB Enterprise Server from repository failed on CentOS 7 due to package dependencies. (MENT-420)

Interface Changes

• WARN_INNODB_PARTITION_OPTION_IGNORED error code added

Platforms

In alignment with the , MariaDB Enterprise Server 10.4.10-4 is provided for:

• CentOS 8

• CentOS 7

• CentOS 6

• Debian 10

• Debian 9

• Debian 8

• Red Hat Enterprise Linux 8

• Red Hat Enterprise Linux 7

• Red Hat Enterprise Linux 6

• SUSE Linux Enterprise Server 15

• SUSE Linux Enterprise Server 12

• Ubuntu 18.04

• Ubuntu 16.04

• Microsoft Windows

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

Note

CentOS 6, Debian 8, and Red Hat Enterprise Linux 6 are no longer supported as per the . Older releases are available from the . Instructions for installation are included as a README file within the download.

Installation Instructions

Upgrade Instructions

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

MariaDB Enterprise Server 10.6.12-8 is a maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes. Users of MariaDB Enterprise Server 10.6.12-7 are encouraged to upgrade. Additional steps are required if upgrading from Enterprise Server 10.6.12-7 to 10.6.12-8.

The next scheduled maintenance release for MariaDB Enterprise Server is 2023-06-12.

MariaDB Enterprise Server 10.6.12-8 was released on 2023-05-24.

Fixed Security Vulnerabilities

#1: MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the MariaDB Engineering Policy for details.

Upgrade Procedure

MariaDB Enterprise Server 10.6.12-8 has a special upgrade procedure that only applies to users who previously deployed MariaDB Enterprise Server 10.6.12-7.

The following procedure is required to truncate the undo log tablespaces:

1. Upgrade from ES 10.6.12-7 to 10.6.12-8 using the normal upgrade procedure.

2. After the server has been started with ES 10.6.12-8, set innodb_fast_shutdown=0:

SET GLOBAL innodb_fast_shutdown=0;

1. Shutdown the server:

$ sudo systemctl stop mariadb

1. Change innodb_undo_tablespaces to a different value than its current value:

[mariadb]
innodb_undo_tablespaces=4

1. Start the server:

$ sudo systemctl start mariadb

Notable Changes

• The optimizer can now use column histogram data when estimating output cardinality of hashed (BNL-H) joins. (MDEV-30812)

  • Starting with this release, the has a new flag called hash_join_cardinality that can enable the feature.

  • When enabled, the optimizer uses a formula that provides conservative estimates.

  • To enable this functionality in a given session, set the flag using the :

SET optimizer_switch='hash_join_cardinality=on';

Issues Fixed

Can result in a hang or crash

• When a prepared statement is used to query a view that contains a UNION, the server can crash. (MDEV-31102)

• When is set and is greater than 0, replica servers can hang if data is inserted into tables with a sequence. (MDEV-29621)

  • In previous releases, the replica server would treat full inserts into the sequence as DDL statements, which would cause it to acquire an exclusive lock on the sequence table. If another parallel replication thread is waiting on the lock at the same time, the two threads can deadlock.

  • Starting with this release, replica servers manage their locks better to avoid deadlocks in this scenario.

• When InnoDB splits or merges a B-tree page, the server can hang due to a race condition. (MDEV-29835)

• When InnoDB undo log truncation is enabled by setting innodb_undo_log_truncate=ON, if some undo log tablespace exceeds innodb_max_undo_log_size, the server can hang. (MDEV-30863)

  • In previous releases, InnoDB chooses an undo log tablespace for truncation and marks all the related rollback segments with the state "truncation in progress". When the truncation is completed, InnoDB fails to re-enable the rollback segments. Consequently, if there are further write transactions before the server is shut down, the transactions must wait for usable rollback segments in a busy-loop. Since InnoDB does not re-enable the rollback segments, the transactions wait indefinitely.

  • Starting with this release, InnoDB properly manages the state of rollback segments when InnoDB undo log truncation is enabled.

Can result in unexpected behavior

• For certain data distributions, the optimizer histogram code can produce wrong selectivity, which can lead to performance degradation. (MDEV-31067)

• The optimizer does not take into account the selectivity of the equality conditions for Block Nested Hash (BNL-H) joins.

  • In previous releases, this issue can cause mis-estimates and bad query plans when running with set to 3 or higher (the default is 2).

• When the lateral derived optimization is used to execute a query, the derived table is re-filled on every incoming row combination, even if the parameter values have not changed. (MDEV-26301)

• When is optimistic and is greater than 0, can fail with an out-of-order binlog error if the sequence uses InnoDB. (MDEV-31077)

  • In previous releases, the following error can be raised:

Last_Error: Error 'An attempt was made to binlog GTID 0-1-100 which would create an out-of-order sequence number with existing GTID 0-1-100 and gtid stric mode is enabled' on query. Default database: 'test'. Query: 'alter sequence s1 restart with 1' will be shown.

• InnoDB does not free undo logs when they are no longer needed. (MDEV-31234)

  • In the previous release, when innodb_undo_tablespaces is set to 0, the undo logs would be stored in the InnoDB system tablespace (ibdata1 by default), so this issue could cause the InnoDB system tablespace to grow indefinitely.

  • Starting with this release, InnoDB frees undo logs when they are no longer needed.

  • For servers that previously ran ES 10.6.12-7, a special procedure is required to truncate the undo log tablespaces after the upgrade is complete.

• InnoDB history list length increases faster in MariaDB Enterprise Server 10.6 compared to MariaDB Enterprise Server 10.5 for the same load. (MDEV-29401)

Changes in Storage Engines

• This release incorporates MariaDB ColumnStore engine version 23.02.3.

Interface Changes

• hash_join_cardinality=off has been incrementally added to the default value of the system variable.

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.12-8 is provided for:

• CentOS 7 (x86_64)

• Debian 10 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

• Red Hat Enterprise Linux 7 (x86_64)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (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)

• Ubuntu 22.04 (x86_64, ARM64)

Windows packages are not currently available for this release.

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

Installation Instructions

Upgrade Instructions

MariaDB Enterprise Server 10.6 introduces the new features listed below.

Atomic DDL

DDL (Data Definition Language) statements are now atomic operations. If the DDL statement is not fully successful, the operation will be rolled back. When the server crashes or is killed in the middle of a DDL statement, the operation is rolled back during crash recovery when the server is restarted.

During crash recovery, the server uses the DDL log to determine if an operation needs to be rolled back. When the is enabled, the crash recovery process ensures that the successful operations are written to the binary log and that the unsuccessful operations are not.

By default, the DDL log is at ddl-recovery.log in the . When DDL statements are being executed, the DDL log is synchronized to disk very frequently. If you want to configure a custom path for the DDL log, the option can be used.

As of this release, the following storage engines fully support atomic DDL:

SKIP LOCKED

ignores already-locked rows.

One use case for this feature is within applications that sell a limited resource, such as ticketing, rentals, or seat-based sales. In these applications, you need a way to display only the available inventory. This can be accomplished by querying available inventory and skipping locked rows.

Enterprise Audit Object Filters

allows database-specific and table-specific filters.

For example:

JSON_TABLE

returns a table from JSON data.

Queryable rows and columns are produced based on the JSON input, but are not stored in a table on disk. Column mappings are defined in a JSON path expression.

Prior to this release, the and functions could be used to retrieve values from JSON data on a per-column basis.

With JSON_TABLE():

• JSON data can JOIN with existing tables.

• A table can be created from JSON data using against a JSON_TABLE().

• enables extraction of nested data from JSON arrays and objects.

Sys Schema

sys schema provides a set of views, functions, and stored procedures to aid DBA analysis of the .

OFFSET Syntax

Additional syntax is supported for

OFFSET start { ROW | ROWS } FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } { ONLY | WITH TIES } is an alternative to LIMIT .. OFFSET

The WITH TIES option requires the use of ORDER BY and allows the number of rows to exceed the FETCH count to ensure that the final row in the chunk includes any additional rows that have the same values in the ORDER BY fields (eliminating the need to fetch the next chunk to check for spill-over).

• For example, the following query can return more than 10 rows if there are more username rows that match the username in the 10th row (the order of the purchase values within the complete set of each username's records is non-deterministic):

• For example, the following query specifies ONLY instead of WITH TIES, so the query can't return more than 10 rows:

Enhanced Consistency for Semi-sync Replication

When , consistency is guaranteed for a Primary server in an HA (Primary/Replica) topology when using semi-synchronous 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.

Enhanced Compatibility with Oracle

Expanded compatibility with Oracle through new functions:

• Added function

• Added function

• Added function

• Added function

Expanded compatibility with Oracle through enhancements:

• With sql_mode=ORACLE added MINUS as an alias to EXCEPT

• With sql_mode=ORACLE improved SYSDATE to allow use without parenthesis.

• With sql_mode=ORACLE supports a pseudo-column name as an alias for the function.

• With sql_mode=ORACLE subqueries in a FROM clause do not require the AS clause.

Enhanced Compatibility with Sybase SQL Anywhere

Enhanced compatibility with Sybase SQL Anywhere through [sql_mode=EXTENDED_ALIASES]

• With sql_mode=EXTENDED_ALIASES, alias resolution and use of column aliases in the SQL list and WHERE clause.

• With sql_mode=EXTENDED_ALIASES, support use of an alias in the list before the alias is defined.

• With sql_mode=EXTENDED_ALIASES, if the same label is used for an alias and a column, the alias is used.

Backported Features

• The UUID data type has been backported for more efficient storage of UUID values.

• The new is available to set the maximum execution time for queries on replica nodes.

• To simplify maintenance, the supports new clauses to convert tables to partitions, and partitions to tables

• In previous releases, the number of undo logs was configurable before InnoDB was initialized. With this release, the number of undo logs can also be configured after install

• has been backported

• has been backported

• A new view sys.privileges_by_table_by_level in the sys schema, to show privileges granted to a table on a global, schema, or table level

• Option s3_debug can now be changed without the need to restart the server

• New Time Zone Options %Z and %z for DATE_FORMAT

• Server Audit Log with Milliseconds Precision Timestamps

Available Versions

See also:

Installation Instructions

Upgrade Instructions

MariaDB Enterprise Server 10.5.25-19 is a maintenance release of 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.25-19 was released on 2024-06-11.

Fixed Security Vulnerabilities

Notable Changes

• Galera has been updated to 26.4.18

  • The GCS protocol version has been changed, preventing a downgrade of individual nodes of a MariaDB Enterprise Cluster

Changes in Storage Engines

This release incorporates MariaDB ColumnStore engine version 5.6.8.

Issues Fixed

Can result in data loss

• With --gtid-ignore-duplicate set a transaction can be double-applied from another replication source if at applying the transaction from the initial source required retrying in parallel execution. ()

• Backups of server with innodb_encrypt_tables=1 can become corrupted in mariadb-backup --prepare ()

• The TIMESTAMP value of '1970-01-01 00:00:00' can be inserted via a INSERT ...FROM ... SELECT in strict mode although it should result in an error ()

• Galera-replicated events can in some cases contain the wrong time when versioning is used ()

• wrong row targeted with "insert ... on duplicate" and "replace", leading to data corruption ()

Can result in hang or crash

• Using current MariaDB Enterprise Backup against an older server can result in a crash, as the system variable @@aria_log_dir_path does not exist ()

• When using a non-default setting for "innodb_change_buffering", the server can crash ()

• When a fulltext search query with more than 4G inserted or updated rows is executed, the server can crash ()

• For encrypted table spaces an ALTER operation can hang when an encryption thread works on the same tablespace ()

• EXPLAIN statement that uses a subquery which has a query plan that A) will examine less than @@expensive_subquery_limit rows and B) will use join buffer could cause a crash. ()

• For a SPIDER table, when deleting partitions from a table, the server can crash ()

• When replaying a binary log with mariadb-binlog, the tool can crash if the binary log includes statements related to sequences, like SELECT NEXTVAL(s) ()

• MariaDB Enterprise Backup fails with the following error message if the prepare step of the backup encounters a data directory which happens to store wsrep xid position in TRX SYS page: ()

• Assertion when user commits an empty transaction for DDL that was killed during certification: ()

• Graceful node shutdown can crash garbd and MariaDB Enterprise Cluster can go non-primary when SSL is used ()

Can result in unexpected behavior

• Wrong result sets are returned by the second execution of prepared statements from selects using mergeable derived tables pushed into external engine ()

• A query that uses a derived table that employs constructs with side-effects, like (SELECT @var:=... ) as derived_tbl, could produce wrong results ()

• ORDER BY COLLATE improperly applied to non-character columns which is resulting in an unordered result set ()

• Spider/ODBC passed double quotes for names, in ANSI style (MENT-958)

• Default charset doesn't work with PHP MySQLi extension ()

• Bad SEPARATOR value in GROUP_CONCAT on character set conversion can lead to a wrong result ()

• Spider returns parsing failure on valid left join select by translating the on expression to () ()

• When creating a temporary InnoDB table with CREATE TEMPORARY TABLE ... AS SELECT ... from an InnoDB table as a non SUPER / READ ONLY ADMIN user, the following error is shown instead of creating the table: ()

• CREATE TEMPORARY TABLE (without SELECT), INSERT ... SELECT, and CREATE ... LIKE are not affected by this bug

• A view created via JSON_ARRAYAGG returns an incorrect JSON object ()

• Mariadb-dump trusts the server and does not validate the data. A modified dump file can include system commands used by the mariadb-client. Dumps are now loaded in the sandbox mode by default, a system call will result in an error ()

• Updating a case insensitive large unique key with an insensitive change of the value can result in a duplicate key error ()

• When setting binlog_annotate_row_events=1, an event of binlog file can be truncated ()

• Wrong result with semi-join and split-table derived table from queries with an IN subquery predicate in the WHERE clause and a derived table in the FROM clause to which split materialized optimization could be applied. ()

• With galera, correct transactions could not be committed with the following error when accessing system tables for read, and write to innodb tables in the same transaction: ()

• A wrong result on 2-nd execution of a prepared statement is possible when selecting from a view using a merged derived table ()

• Original IP not shown in network related error messages when proxy_protocol is in use ()

• Incorrect DEFAULT expression evaluated in UPDATE ()

• group by optimization incorrectly removing subquery where subject buried in a function ()

Related to performance

• Table is getting rebuild with ALTER TABLE ADD COLUMN although it should be an instant operation not requiring a rebuild ()

• Aggregation functions fail to leverage uniqueness property ()

  • Generally, computing aggregate function with DISTINCT argument: aggregate_func(DISTINCT col1, col2, ...) requires producing a de-duplicated set of its arguments, which can be CPU-intensive

  • When we select from one table the argument list includes the table's PRIMARY (or UNIQUE) key:

then the arguments are guaranteed not to have duplicates. Such cases are now detected allowing the optimizer to skip de-duplication.

Changelog

For the complete list of changes in this release, see the .

Platforms

• In alignment with the , MariaDB Enterprise Server 10.5.26-20 is provided for:

  • AlmaLinux 8 (x86_64, ARM64)

  • AlmaLinux 9 (x86_64, ARM64)

  • Debian 11 (x86_64, ARM64)

  • Debian 12 (x86_64, ARM64)

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

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Red Hat Enterprise Linux 9 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • Rocky Linux 9 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

Installation Instructions

Upgrade Instructions

MariaDB Enterprise Server 10.4.33-23 is a maintenance release of 10.4. This release includes a variety of fixes.

MariaDB Enterprise Server 10.4.33-23 was released on 2024-03-11.

Notable Changes

• Galera has been updated to 26.4.17

Issues Fixed

Can result in data loss

• BLOB corruption on UPDATE of PRIMARY KEY with FOREIGN KEY ()

• Corrupted table after instant ADD COLUMN failed due to attempting to exceed the maximum record length ()

• ALTER command, before entering TOI, tries to collect foreign keys of a table. For this it opens the main table with SHARED_HIGH_PRIO MDL lock which disregards any waiting queued lock requests. If there is a DML operation running on the same table, and a real TOI operation as well, this TOI operation tries to BF-abort DML operation. At the same time, because ALTER is not yet TOI, and it runs with HIGH_PRIO MDL lock, it disregards waiting TOI operation, and gets the lock and immediately gets BF-aborted either by TOI directly or by aborted DML operation. Since there is no wsrep transaction for ALTER, it gets BF-aborted by setting killed state for the tread. But before entering TOI, ALTER doesn't check killed state, so it replicates, and applies on the other nodes successfully, but then it rolls back on the local node, causing inconsistency ()

Can result in hang or crash

• Crash while trying to complain "unsupported meta-data version" on ALTER TABLE...IMPORT TABLESPACE with MySQL 8.0 files ()

• Wrong table attribute PAGE_COMPRESSED=1 shown for tables in the InnoDB system tablespace ()

• MariaDB crashes with foreign_key_checks=0 when changing a column and adding a foreign key at the same time ()

• Sometimes node has been dropped from the cluster on startup Shutdown with async replica () with diagnostics like:

and

• GTIDs may diverge in Galera cluster after CREATE TABLE AS () This can subsequently lead to diagnostics like:

and node crash:

• SHOW SLAVE STATUS can deadlock an errored replica when a parallel replica worker gets killed at about when SHOW is issued ()

• When executing SELECT BINLOG_GTID_POS(@binlog_file...) with the user variable being NULL, the server can crash ()

• A Query that uses a specific SQL construct can cause a server crash. The construct is an equality comparison of table-less row subquery and a subquery that has a UNION operation at the top level: (SELECT 'foo', 'bar') = (SELECT col1, col2 FROM t1 ... UNION ...) ()

• A DELETE with ORDER BY and semijoin optimization can cause a crash ()

• Possible crash when lateral derived in a query is guaranteed to return no rows ()

• When using EXCHANGE PARTITION to replace a partition with a table, the server can crash if the to be exchanged table is using a virtual column which is not matching the partitioning key ()

• When using INSERT DELAYED with a table using virtual columns, the server can crash ()

• When using SELECT from a derived table with using AS OF, the server can crash ()

• When using JSON_CONTAINS_PATH in a comparison in a prepared statement, the server can crash on execution of the statement ()

• Server hangs on DROP DATABASE after a failing LOCK TABLES on Spider table : ()

• When using two temporary tables in OPTIMIZE TABLE, executed as a prepared statement, the server can crash ()

• When calling SP invoking another SP with a parameter requiring a type conversion, the server can crash ()

Can result in unexpected behavior

• SHOW WARNINGS can show wrong foreign key related warnings/errors from an earlier transaction for InnoDB ()

• LeakSanitizer errors in mem_heap_create_block_func upon query from I_S.INNODB_SYS_TABLES with LIMIT ROWS EXAMINED ()

• Query from I_S.INNODB_SYS_INDEXES exceeding LIMIT ROWS EXAMINED causes ER_UNKNOWN_ERROR and LeakSanitizer errors in rec_copy_prefix_to_buf_old ()

• Unexpected ER_ERROR_ON_RENAME upon DROP non-existing FOREIGN KEY with ALGORITHM=COPY ()

• FOREIGN_KEY_CHECKS does not prevent non-copy alter from creating invalid FK structure ()

• Secondary indexes on VARCHAR columns may be corrupted when the VARCHAR is extended so much that a column prefix index must be used ()

• Spider: Valid LEFT JOIN results in ERROR 1064 ()

• Syntax error upon query with subquery from Spider table ()

• Spider doesn't recognize SEMI-JOIN ()

• wsrep_provider_options can be truncated on deep and long directory paths with diagnostics like: "Warning 1265 Data truncated for column 'VARIABLE_VALUE' at row 1" in the server log ()

• Mariadb-dump option --delete-master-logs is ignored ()

• multi source replication filters breaking GTID semantic ()

• wsrep_gtid_domain_id is ignored on any node other than bootstrapped node when the wsrep_gtid_mode is set to ON ()

• A connection can control RAND() in following connection if used in conjunction with set rand_seed1, rand_seed2 ()

• mariadb-upgrade does not remove mysql.plugin entries for plugins that became bundled. Error message "[ERROR] mariadbd: Plugin 'unix_socket' is already installed." is shown when upgrading ()

• TaskMax not set to infinity in the MariaDB systemd unit, therefor a lower number than defined in max_connections might be possible for the number of connections ()

• If storage engine Spider is loaded upon server startup, Spider related system, and status variables are not available (MENT-2043)

• Regular expressions cannot be used in queries on tables of type SPIDER ()

• MariaDB Enterprise Backup sometimes shows the error Can't open shared library '/file_key_management.so' (errno: 2, cannot open shared object file: No such file, or directory) when the option --target-dir is not used with --prepare ()

• The database part is not case sensitive in Stored Procedure names. This can lead to using the wrong stored procedure, if the same database name is used as lower, and uppercase. ()

• CREATE UNIQUE INDEX can fail with an incorrect "ERROR 1286 (42000): Unknown storage engine 'partition'" ()

• After successful connection, server sets SERVER_STATUS_AUTOCOMMIT in server_status in the OK packet although the global variable autocommit=0 is set ()

• In some cases it is possible to create a Spider table which is referencing to a table on the same instance although spider_same_server_link=0 is set ()

• Spider fails to auto-discover a table structure with ERROR 12500 (HY000): unknown ()

• REGEXP_REPLACE treats empty strings different than REPLACE in ORACLE mode ()

• The Enterprise Audit Plugin does not always report the user name (MENT-2035)

Related to performance

• An ALTER using ALGORITHM=INPLACE or adding new indexes can increase the table space file size ()

• Operations that involve extending InnoDB files can be extremely slow when the data directory resides on an NFS server that uses a smaller block size than 4096 bytes ()

* Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.4.33-23 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)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 20.04 (x86_64, ARM64)

Some components of MariaDB Enterprise Server are supported on a subset of platforms. See MariaDB Engineering Policies for details.

Installation Instructions

Upgrade Instructions

MariaDB Enterprise Server 10.4.32-22 is a maintenance release of 10.4. This release includes a variety of fixes. Users of MariaDB Enterprise Server 10.4.31-21 are encouraged to upgrade. Additional steps are required if upgrading from Enterprise Server 10.4.31-21 to 10.4.32-22.

MariaDB Enterprise Server 10.4.32-22 was released on 2023-12-12.

Fixed Security Vulnerabilities

Notable changes

• CHACHA20-POLY1305 support when WolfSSL is used ()

• The semi-synchronous replication magic number error "[ERROR] Read semi-sync reply magic number error" has been improved to show the semi-sync acknowledgment reported with printing the hex-dump of the failing network packet ()

• Disable TLS v1.0 and 1.1 for MariaDB. TLSv1.1 removed from the default tls_version system variable. ()

  • A warning is shown if TLSv1.0 or TLSv1.1 are selected.

Can result in data loss

• With binary log enabled transactions that are filtered out of binlogging by any of binlog_{do,ignore}_db option may be lost in the engine. ()

• DROP INDEX followed by CREATE INDEX may corrupt data ()

• Assertion fails in MDL_context::acquire_lock upon parallel replication of CREATE SEQUENCE ()

Can result in hang or crash

• A hang or crash could be observed in parallel replication of STATEMENT binlog format transactions modifying temporary tables. E.g. witnessed in rpl.rpl_parallel_temptable failure. ()

• A failure that occurs due to unnecessary replication of CACHE INDEX and LOAD INDEX INTO CACHE although this is a local operation. ()

• Rowid filter does not process a storage engine error correctly. A query that's executing a locking read and is using the Rowid Filter could cause a server crash if it has encountered a Lock Wait Timeout or Deadlock or a similar error when building the Rowid Filter. ()

• Crash when HAVING in a correlated subquery references columns in the outer query ()

• Due to a flaw in the SST scripts, it was not possible to execute SST when datadir, or some innodb log directory points to a path that is actually a symlink to the actual data directory. ()

• Server can crash when a table of type SPIDER starts with a comment string which is not a parameter for SPIDER. ()

• Node crashes when trying to execute "CREATE TABLE ... WITH SYSTEM VERSIONING AS SELECT ..." ()

• Lock wait timeout with INSERT-SELECT, autoinc, and statement-based replication ()

• Too strict assertion which leads to a problem since with the BINLOG statement we can execute binlog events on master also (not only in applier). ()

• Galera cannot support wsrep_forced_binlog_format=[MIXED|STATEMENT] during CREATE TABLE AS SELECT. But a crash in the form of an assertion is an overreaction. Now a warning is issued instead. ()

• When using ROW_FORMAT=COMPRESSED, the server can crash with the warning "InnoDB: 2048 bytes should have been read. Only 0 bytes read. Retrying for the remaining bytes." in the server log ()

• Possible server crash when setting SPIDER option spider_delete_all_rows to 0 and delete all rows of a spider table ()

• Use of nested row constructs in the left expression of an IN subquery should produce an error. Example: (a,(b,c)) IN (SELECT ...). In some degenerate cases, the error was not detected, and this causes a crash at a further stage in query processing. ()

• A table-less subquery with a LIMIT clause with non-zero offset, like ( SELECT two LIMIT 1 OFFSET 1) can produce unexpected results. If used inside ORDER BY, it can cause a crash. ()

• Possible crash in the full-text search plugin parser when using FULLTEXT...WITH PARSER. ()

• Intermittent crashes when using SEQUENCE in combination with Galera ()

• When two clients execute FLUSH TABLES WITH READ LOCK/UNLOCK TABLES on a Galera node, the node would sometimes get stuck in a paused state. This can cause the next requests to fail. ()

• Sometimes a node has been dropped from the cluster on startup/shutdown with async replication enabled due to inconsistency issues with the mysql.gtid_slave_pos table (between master and replica nodes), because previously this table was not previously replicated within the cluster. ()

• Server crashes in check_sequence_fields upon CREATE TABLE .. SEQUENCE=1 AS SELECT .. ()

• Crash when searching for the best split of derived table ()

• When a new user is connecting or a user is changing the password while FLUSH PRIVILEGES is executed, the server can crash (MENT-1707)

Can result in unexpected behavior

• Prefix keys for CHAR return error "ERROR 1062 (23000): Duplicate entry 'ß' for key 'a'" for MyISAM and Aria when inserting data ()

• Possible wrong results of DISTINCT with NOPAD collations when SET big_tables=1; is set ()

• Missed kill when the SQL thread goes to wait for parallel slave worker queues to drain. KILL query did not affect a replication thread, which remained alive unexpectedly by the user. ()

• InnoDB tries to purge non-delete-marked records of an index on a virtual column prefix. An error like "InnoDB: tried to purge non-delete-marked record in index b of table test.t" is shown in the server log ()

• lock_row_lock_current_waits counter in information_schema.innodb_metrics may become negative ()

• SHOW REPLICA STATUS Last_SQL_Errno race condition on Errored replica restart. A contradictory YES of slave_running_status and an error code in Last_SQL_Errno will be shown ()

• Auto-increment no longer works for explicit FTS_DOC_ID ()

• In some cases, replaying transactions on other MariaDB Enterprise Cluster nodes results in an wrong "Failed to insert streaming client" warning ()

• Wrong bit encoding using COALESCE ()

• getting error 'Illegal parameter data types row and bigint for operation '+' ' when using ITERATE in a FOR..DO ()

• While checking for altered column in foreign key constraints, InnoDB fails to ignore virtual columns ()

• seconds_behind_master is inaccurate for Delayed replication ()

• The wsrep_sst_method variable can be set to an invalid value using the SET statement. ()

• Misleading help text for mysqlbinlog (mariadb-binlog) -T/--table option ()

• mbstream breaks page compression on XFS ()

• MyISAM tables took transactional metadata locks although there were no active transactions. ()

• "rpm --setugids" breaks PAM authentication ()

• A multi-row Insert into an empty table fails if the table has a unique index using hash. CHECK TABLE returns with "Table 't1' is marked as crashed and should be repaired" ()

• wrong table name in InnoDB's "row too big" errors ()

• Slow log Rows_examined for the slow_log can be out of range. In this case the server log includes "([ERROR] Unable to write to mysql.slow_log)" ()

• An incorrect examined rows number is used in some cases like in the slow query log, with LIMIT ROWS EXAMINED, or with ANALYZE FORMAT=JSON when a query gets executed inside of a function. Each stored function call doubles the current count during processing ()

Related to performance

• Optimize is_file_on_ssd() to speedup opening tablespaces on Windows ()

• Significant slowdown for query with many outer joins ()

• An incorrect examined rows number is used in some cases like in the slow query log, with LIMIT ROWS EXAMINED, or with ANALYZE FORMAT=JSON when an executed query includes a stored function Each stored function call doubles the current count during processing ()

• Parallel replication deadlock victim preference code erroneously removed. As a result, parallel slave could retry transaction execution more times than necessary. ()

Related to install and upgrade

• mysql_install_db doesn't properly grant proxy privileges to all default root user accounts ()

• The second node cannot be started because Galera SST rsync wants to replicate snapshot directory when datadir is on a NetApp storage with NFS access ()

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.4.32-22 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)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 20.04 (x86_64, ARM64)

Some components of MariaDB Enterprise Server are supported on a subset of platforms. See for details.

Installation Instructions

Upgrade Instructions

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

MariaDB Enterprise Server 10.4.27-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. ()

  • 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 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 a DDL statement is executed using the , and is set, the server can hang. (, )

• When renaming a table to a long name, the server can crash. ()

• When an causes InnoDB to rebuild a table with a spatial index, the server can crash. ()

• When an InnoDB temporary table contains a spatial index, the server can crash if the temporary table is dropped due to DROP TEMPORARY TABLE or client disconnect. ()