> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/release-notes/enterprise-server/old-releases/10.5/10.5.12-8.md).

# Release Notes for MariaDB Enterprise Server 10.5.12-8

MariaDB Enterprise Server 10.5.12-8 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2021-09-14

This eighth release of [MariaDB Enterprise Server](/docs/release-notes/enterprise-server.md) 10.5 is a maintenance release. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.12-8 was released on 2021-09-14.

## Fixed Security Vulnerabilities

| CVE (with [cve.org](https://www.cve.org/) link)                                 | CVSS base score |
| ------------------------------------------------------------------------------- | --------------- |
| [CVE-2021-2389](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2389)   | 5.9             |
| [CVE-2021-46666](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46666) | 5.5             |
| [CVE-2021-46658](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46658) | 5.5             |
| [CVE-2021-46657](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46657) | 5.5             |
| [CVE-2021-2372](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2372)   | 4.4             |

## Backported Features

This release of MariaDB Enterprise Server includes features backported from MariaDB Enterprise Server 10.6.

* [MariaDB Enterprise Audit](/docs/server/reference/plugins/mariadb-audit-plugin.md) allows database-specific and table-specific filters. (MENT-65)\
  For example:

```
{
 "connect_event" : "ALL",
 "table_event" : ["READ","WRITE",{"ignore_tables" : "mysql.*"}],
 "query_event" : ["DDL",{"tables" : "test.t2"}]
}
```

* [MariaDB Enterprise Audit](/docs/server/reference/plugins/mariadb-audit-plugin.md) can be configured to not start the server if Audit Filters are invalid. (MENT-1243)
  * Added the new [server\_audit\_load\_on\_error](/docs/server/server-management/variables-and-modes/server-system-variables.md) system variable.
  * To configure server startup to fail if Audit Filters are invalid, set [server\_audit\_load\_on\_error](/docs/server/server-management/variables-and-modes/server-system-variables.md) to `OFF` and set [server-audit](/docs/server/reference/plugins/mariadb-audit-plugin/mariadb-audit-plugin-options-and-system-variables.md) to `FORCE` or `FORCE_PLUS_PERMANENT`.
  * The default value of [server\_audit\_load\_on\_error](/docs/server/server-management/variables-and-modes/server-system-variables.md) is `ON`, so the default behavior is the same as in prior releases.
* Enhanced consistency for Semi-Sync Replication
  * When [rpl\_semi\_sync\_slave\_enabled=ON](/docs/server/ha-and-performance/standard-replication/semisynchronous-replication.md#rpl_semi_sync_slave_enabled), consistency is guaranteed for a Primary server in an HA (Primary/Replica) topology when using semi-synchronous replication. ([MDEV-21117](https://jira.mariadb.org/browse/MDEV-21117))
  * 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 Sybase SQL Anywhere through [sql\_mode=EXTENDED\_ALIASES](/docs/server/server-management/variables-and-modes/sql_mode.md): (MENT-1062)\
  With `sql_mode=EXTENDED_ALIASES`, alias resolution and use of column aliases in the SQL [SELECT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select.md) list and `WHERE` clause.\
  With `sql_mode=EXTENDED_ALIASES`, support use of an alias in the SELECT 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.

## Notable Changes

Galera updated to 26.4.9

ARM64 is now supported for several [#platforms](#platforms).

* The script `wsrep_sst_mariadb-backup` checks all server-related configuration groups when processing a configuration file. ([MDEV-25669](https://jira.mariadb.org/browse/MDEV-25669))
  * Prior to this release, only the \[`mysqld`] configuration group was checked when processing a configuration file.
* MariaDB Enterprise Backup expects [--stream=mbstream](/docs/server/server-usage/backup-and-restore/mariadb-backup/mariadb-backup-options.md#stream) to stream a backup using the included `mbstream` utility. ([MDEV-15730](https://jira.mariadb.org/browse/MDEV-15730))
  * Prior to this release, MariaDB Enterprise Backup expected [--stream=xbstream](/docs/server/server-usage/backup-and-restore/mariadb-backup/mariadb-backup-options.md#stream), even though the `xbstream` utility had been renamed to `mbstream`.

InnoDB no longer acquires advisory file locks by default. ([MDEV-24393](https://jira.mariadb.org/browse/MDEV-24393))

The [information\_schema.KEYWORDS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-keywords-table.md) table has been added and can be used to view details about SQL keywords. ([MDEV-25129](https://jira.mariadb.org/browse/MDEV-25129))

The [information\_schema.SQL\_FUNCTIONS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-sql_functions-table.md) table has been added and can be used to view details about built-in functions. ([MDEV-25129](https://jira.mariadb.org/browse/MDEV-25129))

* When using data-at-rest encryption with the [file\_key\_management](/docs/server/security/encryption/data-at-rest-encryption/key-management-and-encryption-plugins/file-key-management-encryption-plugin.md) encryption plugin, InnoDB will automatically disable key rotation checks. ([MDEV-14180](https://jira.mariadb.org/browse/MDEV-14180))
  * The [file\_key\_management](/docs/server/security/encryption/data-at-rest-encryption/key-management-and-encryption-plugins/file-key-management-encryption-plugin.md) encryption plugin does not support key rotation, so key rotation checks are not required.
  * In previous releases, unnecessary key rotation checks with the [file\_key\_management](/docs/server/security/encryption/data-at-rest-encryption/key-management-and-encryption-plugins/file-key-management-encryption-plugin.md) encryption plugin could reduce performance, unless they were explicitly disabled by setting [innodb\_encryption\_rotate\_key\_age=0](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#innodb_encryption_rotate_key_age).

Removed SSL ciphers RC4-MD5 and RC4-SHA for [mariadbd](/docs/server/server-management/starting-and-stopping-mariadb/mariadbd.md) binaries compiled with WolfSSL. ([MDEV-26092](https://jira.mariadb.org/browse/MDEV-26092))

* The `type_mysql_json` plugin is not supported, so it has been relocated to the appropriate location. (MENT-1277)
  * For binary tarballs, the plugin was moved to the `not_supported` directory.
  * For Linux packages, the plugin was moved to the `not-supported` repositories.
* For [mariadb-binlog](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog.md), specifying the [--base64-output](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog/mariadb-binlog-options.md#options) option with no value would prevent the [BINLOG](/docs/server/reference/sql-statements/administrative-sql-statements/binlog.md) statements from being written to the output. ([MDEV-25222](https://jira.mariadb.org/browse/MDEV-25222))
  * Starting with this release, the [--base64-output](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog/mariadb-binlog-options.md#options) option requires a value, and the `always` value has been removed.

The black box tool for MariaDB Enterprise Cluster has been renamed from `bbtool` to `mariadb-bbtool`. The install directory has been changed from `sbin` to `bin`. (MENT-1291)

Improved InnoDB page flushing performance. ([MDEV-25954](https://jira.mariadb.org/browse/MDEV-25954), [MDEV-25948](https://jira.mariadb.org/browse/MDEV-25948), [MDEV-25801](https://jira.mariadb.org/browse/MDEV-25801), [MDEV-26004](https://jira.mariadb.org/browse/MDEV-26004), [MDEV-25113](https://jira.mariadb.org/browse/MDEV-25113))

The [inet6](/docs/server/reference/data-types/string-data-types/inet6.md) plugin has been upgraded to the `"stable"` maturity. ([MDEV-26226](https://jira.mariadb.org/browse/MDEV-26226))

The [S3](/docs/server/server-usage/storage-engines/s3-storage-engine.md) plugin has been upgraded to the `"stable"` maturity. ([MDEV-26226](https://jira.mariadb.org/browse/MDEV-26226))

## Issues Fixed

### Can result in data loss

* When an [ALTER TABLE ... ADD COLUMN](/docs/server/reference/sql-statements/data-definition/alter/alter-table.md) statement is executed with `ALGORITHM=INSTANT`, a warning is not raised when the operation causes the default value of a DATE column to be truncated. ([MDEV-25971](https://jira.mariadb.org/browse/MDEV-25971))

### Can result in a hang or crash

* Possible server crash when pushing a `WHERE` condition over a mergeable derived table / view / CTE DT into a grouping view / derived table / CTE V whose item list contained set functions with constant arguments. ([MDEV-25635](https://jira.mariadb.org/browse/MDEV-25635))
* Server crashes on second execution of a stored procedure or a prepared statement when the corresponding query executes a window function on a view, CTE, or derived table. ([MDEV-25565](https://jira.mariadb.org/browse/MDEV-25565))
* Server crashes possible when executing a prepared statement with a hanging recursive CTE. ([MDEV-26135](https://jira.mariadb.org/browse/MDEV-26135))
* Server crashes while executing query with a CTE in a prepared statement or stored procedure. ([MDEV-26025](https://jira.mariadb.org/browse/MDEV-26025))
* Server crashes while executing query with a recursive CTE that is indirectly used twice. ([MDEV-26202](https://jira.mariadb.org/browse/MDEV-26202))
* Server crashes due to infinite recursion while processing an embedded recursive CTE with missing `RECURSIVE`. ([MDEV-26095](https://jira.mariadb.org/browse/MDEV-26095))
* Server crashes in InnoDB deadlock checker under high load. ([MDEV-25594](https://jira.mariadb.org/browse/MDEV-25594))
* Server crashes when a virtual generated column has a prefix index. ([MDEV-26220](https://jira.mariadb.org/browse/MDEV-26220))
* Server crashes possible when using virtual generated columns. ([MDEV-18166](https://jira.mariadb.org/browse/MDEV-18166), [MDEV-18249](https://jira.mariadb.org/browse/MDEV-18249))
* Server crashes while executing [DELETE](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/delete.md) when a [YEAR](/docs/server/reference/sql-functions/date-time-functions/year.md) column is truncated. ([MDEV-17890](https://jira.mariadb.org/browse/MDEV-17890))
* Server crashes while executing [SET ROLE](/docs/server/reference/sql-statements/account-management-sql-statements/set-role.md) when a hostname cannot be resolved. ([MDEV-26081](https://jira.mariadb.org/browse/MDEV-26081))
* Server crashes when a subquery references an outer column in an `ORDER BY` clause. ([MDEV-25629](https://jira.mariadb.org/browse/MDEV-25629))
* Server crashes due to a stack overrun in the query optimizer while executing query with more than 32 equality conditions that compare columns of different tables (such as `tableX.colX=tableY.colY`). ([MDEV-17783](https://jira.mariadb.org/browse/MDEV-17783))
* Server crashes when a window function is the left expression of an `IN(SELECT ..`) subquery. ([MDEV-25630](https://jira.mariadb.org/browse/MDEV-25630))
* Possible deadlock on a Replica server using GTID Replication when [slave\_parallel\_mode=optimistic](/docs/server/ha-and-performance/standard-replication/replication-and-binary-log-system-variables.md) and [OPTIMIZE TABLE](/docs/server/ha-and-performance/optimization-and-tuning/optimizing-tables/optimize-table.md), [REPAIR TABLE](/docs/server/reference/sql-statements/table-statements/repair-table.md), or [ANALYZE TABLE](/docs/server/reference/sql-statements/table-statements/analyze-table.md) is executed. ([MDEV-17515](https://jira.mariadb.org/browse/MDEV-17515))
* Server crashes when [ALTER TABLE .. ADD FULLTEXT INDEX](/docs/server/reference/sql-statements/data-definition/alter/alter-table.md) fails on an InnoDB table. ([MDEV-25721](https://jira.mariadb.org/browse/MDEV-25721))
* Server crashes while executing [TRUNCATE](/docs/server/reference/sql-functions/numeric-functions/truncate.md) on an InnoDB table with a Full-Text Index. ([MDEV-25663](https://jira.mariadb.org/browse/MDEV-25663))
* Server crashes while executing [ALTER TABLE](/docs/server/reference/sql-statements/data-definition/alter/alter-table.md) on an InnoDB table with virtual generated columns that are indexed. ([MDEV-25872](https://jira.mariadb.org/browse/MDEV-25872))
* Server crashes while executing [CHECK TABLE](/docs/server/reference/sql-statements/table-statements/check-table.md) when [innodb\_read\_only](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#innodb_read_only) is enabled. ([MDEV-25886](https://jira.mariadb.org/browse/MDEV-25886))
* Server crashes when a connection is killed while executing [ALTER TABLE](/docs/server/reference/sql-statements/data-definition/alter/alter-table.md) after previously locking the table with [LOCK TABLE](/docs/server/reference/sql-statements/transactions/lock-tables.md). ([MDEV-17749](https://jira.mariadb.org/browse/MDEV-17749))
* Server crashes when the global value of the [system\_versioning\_asof](/docs/server/reference/sql-structure/temporal-tables/system-versioned-tables.md#system_versioning_asof) system variable is set using a stored function that reads the value of another global system variable. ([MDEV-16481](https://jira.mariadb.org/browse/MDEV-16481))
* Server crashes when [MariaDB Enterprise Audit](/docs/server/reference/plugins/mariadb-audit-plugin.md) is active and usernames longer than 256 characters are used. (MENT-1019)
* Server crashes when [MariaDB Enterprise Audit](/docs/server/reference/plugins/mariadb-audit-plugin.md) is active and audit log file rotation is triggered. (MENT-1207)
* Server crashes while executing query with a CTE that is used at least twice and that references an embedded recursive CTE. ([MDEV-26108](https://jira.mariadb.org/browse/MDEV-26108))
* Possible crash with transactions having changes for tables with no primary key to apply in parallel, when using MariaDB Enterprise Cluster. ([MDEV-25551](https://jira.mariadb.org/browse/MDEV-25551))
* Server crashes when executing [CREATE TABLE](/docs/server/server-usage/tables/create-table.md) to create a [Spider](/docs/server/server-usage/storage-engines/spider.md) table with a `COMMENT` value that does not contain embedded double quotes. ([MDEV-26139](https://jira.mariadb.org/browse/MDEV-26139))
* Server crashes when a client connects during shutdown. ([MDEV-18353](https://jira.mariadb.org/browse/MDEV-18353))
* Server crashes while concurrently executing [DROP TRIGGER](/docs/server/reference/sql-statements/data-definition/drop/drop-trigger.md). ([MDEV-25651](https://jira.mariadb.org/browse/MDEV-25651))
* Server hangs on Windows when [mariadb-upgrade](/docs/server/clients-and-utilities/deployment-tools/mariadb-upgrade.md) is executed and then the server is stopped. (MENT-1300)
* Server crashes while executing [SET](/docs/server/reference/sql-statements/administrative-sql-statements/set-commands/set.md) to set multiple variables at once. ([MDEV-25601](https://jira.mariadb.org/browse/MDEV-25601))
* Server crashes while calling [SPIDER\_DIRECT\_SQL](/docs/server/server-usage/storage-engines/spider/spider-functions/spider_direct_sql.md) without creating the required temporary table. (MENT-1318)
* MariaDB Enterprise Backup crashes when executed with the [--backup](/docs/server/server-usage/backup-and-restore/mariadb-backup/mariadb-backup-options.md#backup) and [--databases-exclude](/docs/server/server-usage/backup-and-restore/mariadb-backup/mariadb-backup-options.md#databases-exclude) options. ([MDEV-25815](https://jira.mariadb.org/browse/MDEV-25815))

### Can result in unexpected behavior

* When [CREATE OR REPLACE TABLE](/docs/server/server-usage/tables/create-table.md) fails after dropping the table, the `DROP TABLE` operation is not written into the binary log. ([MDEV-25595](https://jira.mariadb.org/browse/MDEV-25595))
* The [SHOW GRANTS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-grants.md) statement does not quote role names properly for `DEFAULT ROLE`. ([MDEV-26080](https://jira.mariadb.org/browse/MDEV-26080))
* The [innochecksum](/docs/server/clients-and-utilities/administrative-tools/innochecksum.md) utility reports errors for freed pages. ([MDEV-25361](https://jira.mariadb.org/browse/MDEV-25361))
* When an unknown column is referenced in the `WHERE` clause of a recursive CTE, the query sometimes succeeds instead of failing with an [ER\_BAD\_FIELD\_ERROR](/docs/server/reference/error-codes/mariadb-error-codes-1000-to-1099/e1054.md). ([MDEV-26189](https://jira.mariadb.org/browse/MDEV-26189))
* Reusing CTE inside a function fails with the [ER\_NO\_SUCH\_TABLE](/docs/server/reference/error-codes/mariadb-error-codes-1100-to-1199/e1146.md) error code. ([MDEV-23886](https://jira.mariadb.org/browse/MDEV-23886))
* Several fixes for MariaDB Enterprise Cluster (Galera) SST scripts. ([MDEV-20580](https://jira.mariadb.org/browse/MDEV-20580), [MDEV-25818](https://jira.mariadb.org/browse/MDEV-25818), [MDEV-25759](https://jira.mariadb.org/browse/MDEV-25759), [MDEV-25719](https://jira.mariadb.org/browse/MDEV-25719), [MDEV-15639](https://jira.mariadb.org/browse/MDEV-15639), [MDEV-15371](https://jira.mariadb.org/browse/MDEV-15371), [MDEV-18797](https://jira.mariadb.org/browse/MDEV-18797), MENT-1170, [MDEV-24979](https://jira.mariadb.org/browse/MDEV-24979), [MDEV-21192](https://jira.mariadb.org/browse/MDEV-21192))
* With MariaDB Enterprise Cluster, when [=mariadb-backup](/docs/galera-cluster/reference/galera-cluster-system-variables.md), MariaDB Enterprise Backup does not inherit server options set by the `Environment` systemd configuration parameter. ([MDEV-24962](https://jira.mariadb.org/browse/MDEV-24962))
* With MariaDB Enterprise Cluster, when [=rsync](/docs/galera-cluster/reference/galera-cluster-system-variables.md) is set and log-bin and/or log-bin-index are set to custom paths, the rsync SST does not copy the binary log index. ([MDEV-25978](https://jira.mariadb.org/browse/MDEV-25978))

As a result of this issue, a Joiner node writes the following error to the [MariaDB Error Log](/docs/server/server-management/server-monitoring-logs/error-log.md):

```
tail: cannot open 'mysql-bin.index' for reading: No such file or directory
```

* With MariaDB Enterprise Cluster, when [=rsync](/docs/galera-cluster/reference/galera-cluster-system-variables.md) is set, rsync for a new SST process may be killed rather than the rsync for the old SST process. ([MDEV-25880](https://jira.mariadb.org/browse/MDEV-25880))
* With MariaDB Enterprise Cluster, the WSREP threads could write warnings about foreign keys to the [MariaDB Error Log](/docs/server/server-management/server-monitoring-logs/error-log.md) when wsrep\_debug is not enabled. ([MDEV-26062](https://jira.mariadb.org/browse/MDEV-26062))
  * In prior releases, the following warning could be written to the log:

```
InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `schema`.`child_table`
```

* Starting with this release, the WSREP threads will only write warnings about foreign keys to the [MariaDB Error Log](/docs/server/server-management/server-monitoring-logs/error-log.md) when wsrep\_debug is enabled.
* The [CREATE INDEX](/docs/server/reference/sql-statements/data-definition/create/create-index.md) statement may check the wrong maximum column length. ([MDEV-26203](https://jira.mariadb.org/browse/MDEV-26203))
* The [Spider](/docs/server/server-usage/storage-engines/spider.md) storage engine handles ">=" as ">" in some cases, where multi-column indexes are used. ([MDEV-25985](https://jira.mariadb.org/browse/MDEV-25985))
* The [max\_password\_errors](/docs/server/server-management/variables-and-modes/server-system-variables.md#max_password_errors) system variable does not work correctly with the ed25519 authentication plugin. ([MDEV-25641](https://jira.mariadb.org/browse/MDEV-25641))
* The `"Condition pushdown into derived table"` optimization cannot be applied if the expression being pushed refers to a derived table column which is computed from an expression that has a stored function call, @session variable reference, or other similar construct. ([MDEV-25969](https://jira.mariadb.org/browse/MDEV-25969))
* A query that uses `ORDER BY .. LIMIT` clause and `"Range checked for each record"` optimization could produce incorrect results. ([MDEV-25858](https://jira.mariadb.org/browse/MDEV-25858))
* An aborted [OPTIMIZE TABLE](/docs/server/ha-and-performance/optimization-and-tuning/optimizing-tables/optimize-table.md) statement is logged in the binary log and replicates to the Replica server. ([MDEV-22530](https://jira.mariadb.org/browse/MDEV-22530))
* For system-versioned tables, the [SHOW INDEX](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-index.md) statement displays the system-invisible row\_end column as part of the primary key. ([MDEV-16857](https://jira.mariadb.org/browse/MDEV-16857))
* For system-versioned tables partitioned by `SYSTEM_TIME`, overflowing the partitions leads to incorrect results from [SELECT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select.md). result ([MDEV-22247](https://jira.mariadb.org/browse/MDEV-22247))
* For [Spider](/docs/server/server-usage/storage-engines/spider.md) tables, [SELECT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select.md) statements that use `CASE WHEN .. THEN` can result in syntax error. ([MDEV-24760](https://jira.mariadb.org/browse/MDEV-24760))
* For [Spider](/docs/server/server-usage/storage-engines/spider.md) tables, [SELECT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select.md) statements that use the [JSON\_EXTRACT()](/docs/server/reference/sql-functions/special-functions/json-functions/json_extract.md) function in the `WHERE` clause can result in a syntax error. ([MDEV-24517](https://jira.mariadb.org/browse/MDEV-24517))
* For [Spider](/docs/server/server-usage/storage-engines/spider.md) tables, [UPDATE](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/update.md) statements that call native functions using `remove_str` (such as [TRIM()](/docs/server/reference/sql-functions/string-functions/trim.md)) fail with the [ER\_WRONG\_PARAMCOUNT\_TO\_NATIVE\_FCT](/docs/server/reference/error-codes/mariadb-error-codes-1500-to-1599/e1582.md) error code. ([MDEV-24020](https://jira.mariadb.org/browse/MDEV-24020))
* For [Spider](/docs/server/server-usage/storage-engines/spider.md) tables, server-sided prepared statements (created by PREPARE and executed by EXECUTE) incorrectly turn unsigned integer literals into signed integers. ([MDEV-25808](https://jira.mariadb.org/browse/MDEV-25808))
* For Spider tables, statements that use the JSON\_REPLACE() function fail with the ER\_SP\_DOES\_NOT\_EXIST error code. ([MDEV-24523](https://jira.mariadb.org/browse/MDEV-24523))
* With [MariaDB Enterprise Audit](/docs/server/reference/plugins/mariadb-audit-plugin.md), the [CREATE PROCEDURE](/docs/server/server-usage/stored-routines/stored-procedures/create-procedure.md) and [DROP PROCEDURE](/docs/server/server-usage/stored-routines/stored-procedures/drop-procedure.md) statements are not logged to the audit log. (MENT-1169)
* With MariaDB Enterprise Backup, the [binary log](/docs/server/reference/data-types/string-data-types/binary.md) position written to the `xtrabackup_binlog_info` file during the backup is incorrect for replication. ([MDEV-23080](https://jira.mariadb.org/browse/MDEV-23080))
* With MariaDB Enterprise Cluster, when [=mariadb-backup](/docs/galera-cluster/reference/galera-cluster-system-variables.md), a typo in the SST script causes SST failure on the Donor node. ([MDEV-26117](https://jira.mariadb.org/browse/MDEV-26117))
* For [Spider](/docs/server/server-usage/storage-engines/spider.md) tables, [SELECT](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select.md) statements that use `DISTINCT` do not work properly in some cases. ([MDEV-26013](https://jira.mariadb.org/browse/MDEV-26013))
* When [mariadbd](/docs/server/server-management/starting-and-stopping-mariadb/mariadbd.md) is compiled with WolfSSL, the server fails to accept connections using TLS 1.3 and AES-GCM cipher. ([MDEV-22221](https://jira.mariadb.org/browse/MDEV-22221))
* Concurrent [CREATE TRIGGER](/docs/server/server-usage/triggers-events/triggers/create-trigger.md) statements can be written to the [binary log](/docs/server/reference/data-types/string-data-types/binary.md) in the wrong order and break replication. ([MDEV-25606](https://jira.mariadb.org/browse/MDEV-25606))
* When an [INSERT .. RETURNING](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insertreturning.md) statement is executed in batch mode (such as when the connector sets the `COM_STMT_BULK_EXECUTE` option), the wrong values can be inserted. ([MDEV-21916](https://jira.mariadb.org/browse/MDEV-21916))
* For [INSERT .. RETURNING](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insertreturning.md) statements, a qualified asterisk (such as `table_name.*`) is not supported in the RETURNING clause. ([MDEV-23178](https://jira.mariadb.org/browse/MDEV-23178))
* If a locking-read statement (`UPDATE or SELECT... FOR UPDATE`) contains an outer join with a constant inner table, warnings are written to the [MariaDB Error Log](/docs/server/server-management/server-monitoring-logs/error-log.md). ([MDEV-26106](https://jira.mariadb.org/browse/MDEV-26106))\
  Example warning:

```
[ERROR] InnoDB: Unlock row could not find a 3 mode lock on the record.
```

## Changes in Storage Engines

* This release incorporates MariaDB ColumnStore storage engine version 5.6.2.

## Interface Changes

* ER\_BLACKBOX\_ERROR error code error number changed from `4174` to `6000`
* [KEYWORDS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-keywords-table.md) information schema table added
* `mariadbd` --server-audit-load-on-error command-line option added
* [server\_audit\_load\_on\_error](/docs/server/server-management/variables-and-modes/server-system-variables.md) system variable added
* [SQL\_FUNCTIONS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-sql_functions-table.md) information schema table added
* [system\_versioning\_asof](/docs/server/reference/sql-structure/temporal-tables/system-versioned-tables.md#system_versioning_asof) system variable default value changed from DEFAULT to "" (empty)

## Platforms

In alignment with the [enterprise lifecycle](/docs/release-notes/enterprise-server/about/enterprise-server-lifecycle.md), MariaDB Enterprise Server 10.5.12-8 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 "[MariaDB Corporation Engineering Policies](https://mariadb.com/engineering-policies)".

## Installation Instructions

* [MariaDB Enterprise Server ](/docs/release-notes/enterprise-server/11.4/whats-new.md)[10](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-architecture/mariadb-enterprise-spider-topologies/federated-mariadb-enterprise-spider-topology)[.5](/docs/release-notes/enterprise-server/11.4/whats-new.md)
* [Enterprise Cluster Topology with MariaDB Enterprise Server ](/docs/server/architecture/topologies/galera-cluster.md)[10](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-architecture/mariadb-enterprise-spider-topologies/federated-mariadb-enterprise-spider-topology)[.5](/docs/server/architecture/topologies/galera-cluster.md)
* [Primary/Replica Topology with MariaDB Enterprise Server 10.5](/docs/server/architecture/topologies/primary-replica.md)
* [ColumnStore Object Storage Topology with MariaDB Enterprise Server 10.5](/docs/server/architecture/topologies/columnstore-object-storage.md) [and MariaDB ColumnStore 23.02](/docs/server/architecture/topologies/columnstore-object-storage.md)
* [ColumnStore Shared Local Storage Topology with MariaDB Enterprise Server 10.5](/docs/server/architecture/topologies/columnstore-shared-local-storage.md)[ and MariaDB ColumnStore 23.02](/docs/server/architecture/topologies/columnstore-shared-local-storage.md)
* [HTAP Topology with MariaDB Enterprise Server 10.5](/docs/server/architecture/topologies/htap.md)[ and MariaDB ColumnStore 23.02](/docs/server/architecture/topologies/htap.md)
* [Single-Node ColumnStore 23.02 with MariaDB Enterprise Server 10.5](/docs/server/architecture/topologies/single-node-topologies/enterprise-server-with-columnstore-object-storage.md)[and Object Storage](/docs/server/architecture/topologies/single-node-topologies/enterprise-server-with-columnstore-object-storage.md)
* [Single-Node ColumnStore 23.02 with MariaDB Enterprise Server 10.5](/docs/server/architecture/topologies/single-node-topologies.md)
* [Enterprise Spider Sharded Topology with MariaDB Enterprise Server 10.5](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-architecture/mariadb-enterprise-spider-topologies/sharded-mariadb-enterprise-spider-topology)
* [Enterprise Spider Federated Topology with MariaDB Enterprise Server 10.5](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-architecture/mariadb-enterprise-spider-topologies/federated-mariadb-enterprise-spider-topology)

## Upgrade Instructions

* [Upgrade to MariaDB Enterprise Server 10.5](/docs/server/server-management/install-and-upgrade-mariadb/upgrading/mariadb-community-server-upgrade-paths/upgrading-from-mariadb-10-5-to-mariadb-10-6.md)
* [Upgrade from MariaDB Community Server to MariaDB Enterprise Server 10.5](/docs/server/server-management/install-and-upgrade-mariadb/upgrading/platform-specific-upgrade-guides/upgrading-on-linux/upgrading-between-major-mariadb-versions.md)

<sub>*This page is: Copyright © 2026 MariaDB. All rights reserved.*</sub>

{% @marketo/form formid="4316" formId="4316" %}