Release Notes for MariaDB Enterprise Server 10.6.23-19

MariaDB Enterprise Server 11.6.23-19 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6, released on 2025-09-08

Download Release Notes Changelog Overview of Enterprise Server 10.6

Release date: 8 Sep 2025

MariaDB Enterprise Server 10.6.23-19 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes.

Changes in Storage Engines

• This release incorporates MariaDB ColumnStore engine version 23.10.6

Notable changes

• Galera updated to 26.4.23

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

Can result in hang or crash

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

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

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

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

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

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

• json_extract crashes in Item_func_json_extract::read_json (MDEV-21530)

• Inconsistency detected - create sequence (MENT-2297)

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

Can result in unexpected behaviour

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

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

• AUTO_INCREMENT leads to non-serializable on results (MDEV-36330)

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

• UNIQUE KEY USING HASH accepting duplicate records (MENT-2324)

Changelog

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

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.23-19 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 MariaDB Engineering Policies for details.

Installation Instructions

• Deploy MariaDB Enterprise with Repositories

• Deploy MariaDB Enterprise with Package Tarballs

• Deploy MariaDB Enterprise with Docker

Upgrade Instructions

• Upgrade to MariaDB Enterprise Server 10.6

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