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 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.
CVE (with link)
CVSS base score
This release of MariaDB Enterprise Server includes features backported from MariaDB Enterprise Server 10.6.
allows database-specific and table-specific filters. (MENT-65) For example:
can be configured to not start the server if Audit Filters are invalid. (MENT-1243)
Added the new system variable.
To configure server startup to fail if Audit Filters are invalid, set to OFF and set to FORCE or FORCE_PLUS_PERMANENT.
Galera updated to 26.4.9
ARM64 is now supported for several .
The script wsrep_sst_mariadb-backup checks all server-related configuration groups when processing a configuration file. ()
Prior to this release, only the [mysqld] configuration group was checked when processing a configuration file.
MariaDB Enterprise Backup expects to stream a backup using the included mbstream utility. ()
InnoDB no longer acquires advisory file locks by default. ()
The table has been added and can be used to view details about SQL keywords. ()
The table has been added and can be used to view details about built-in functions. ()
When using data-at-rest encryption with the encryption plugin, InnoDB will automatically disable key rotation checks. ()
The encryption plugin does not support key rotation, so key rotation checks are not required.
In previous releases, unnecessary key rotation checks with the encryption plugin could reduce performance, unless they were explicitly disabled by setting .
Removed SSL ciphers RC4-MD5 and RC4-SHA for binaries compiled with WolfSSL. ()
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.
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. (, , , , )
The plugin has been upgraded to the "stable" maturity. ()
The plugin has been upgraded to the "stable" maturity. ()
When an 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. ()
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. ()
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. ()
Server crashes possible when executing a prepared statement with a hanging recursive CTE. ()
When fails after dropping the table, the DROP TABLE operation is not written into the binary log. ()
The statement does not quote role names properly for DEFAULT ROLE. ()
The utility reports errors for freed pages. ()
As a result of this issue, a Joiner node writes the following error to the :
With MariaDB Enterprise Cluster, when is set, rsync for a new SST process may be killed rather than the rsync for the old SST process. ()
With MariaDB Enterprise Cluster, the WSREP threads could write warnings about foreign keys to the when wsrep_debug is not enabled. ()
In prior releases, the following warning could be written to the log:
Starting with this release, the WSREP threads will only write warnings about foreign keys to the when wsrep_debug is enabled.
The statement may check the wrong maximum column length. ()
The storage engine handles ">=" as ">" in some cases, where multi-column indexes are used. ()
The system variable does not work correctly with the ed25519 authentication plugin. (
This release incorporates MariaDB ColumnStore storage engine version 5.6.2.
error code error number changed from 4174 to 6000
information schema table added
mariadbd --server-audit-load-on-error command-line option added
In alignment with the , 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)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
The default value of is ON, so the default behavior is the same as in prior releases.
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. (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 : (MENT-1062)
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 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.
Prior to this release, MariaDB Enterprise Backup expected --stream=xbstream, even though the xbstream utility had been renamed to mbstream.
For , specifying the option with no value would prevent the statements from being written to the output. (MDEV-25222)
Starting with this release, the option requires a value, and the always value has been removed.
Server crashes while executing query with a recursive CTE that is indirectly used twice. (MDEV-26202)
Server crashes due to infinite recursion while processing an embedded recursive CTE with missing RECURSIVE. (MDEV-26095)
Server crashes in InnoDB deadlock checker under high load. (MDEV-25594)
Server crashes when a virtual generated column has a prefix index. (MDEV-26220)
Server crashes possible when using virtual generated columns. (MDEV-18166, MDEV-18249)
Server crashes while executing when a column is truncated. (MDEV-17890)
Server crashes while executing when a hostname cannot be resolved. (MDEV-26081)
Server crashes when a subquery references an outer column in an ORDER BY clause. (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)
Server crashes when a window function is the left expression of an IN(SELECT ..) subquery. (MDEV-25630)
Possible deadlock on a Replica server using GTID Replication when and , , or is executed. (MDEV-17515)
Server crashes when fails on an InnoDB table. (MDEV-25721)
Server crashes while executing on an InnoDB table with a Full-Text Index. (MDEV-25663)
Server crashes while executing on an InnoDB table with virtual generated columns that are indexed. (MDEV-25872)
Server crashes while executing when is enabled. (MDEV-25886)
Server crashes when a connection is killed while executing after previously locking the table with LOCK TABLE. (MDEV-17749)
Server crashes when the global value of the system variable is set using a stored function that reads the value of another global system variable. (MDEV-16481)
Server crashes when is active and usernames longer than 256 characters are used. (MENT-1019)
Server crashes when 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)
Possible crash with transactions having changes for tables with no primary key to apply in parallel, when using MariaDB Enterprise Cluster. (MDEV-25551)
Server crashes when executing to create a table with a COMMENT value that does not contain embedded double quotes. (MDEV-26139)
Server crashes when a client connects during shutdown. (MDEV-18353)
Server crashes while concurrently executing . (MDEV-25651)
Server hangs on Windows when is executed and then the server is stopped. (MENT-1300)
Server crashes while executing to set multiple variables at once. (MDEV-25601)
Server crashes while calling without creating the required temporary table. (MENT-1318)
MariaDB Enterprise Backup crashes when executed with the --backup and --databases-exclude options. (MDEV-25815)
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. (MDEV-26189)
Reusing CTE inside a function fails with the ER_NO_SUCH_TABLE error code. (MDEV-23886)
Several fixes for MariaDB Enterprise Cluster (Galera) SST scripts. (MDEV-20580, MDEV-25818, MDEV-25759, MDEV-25719, MDEV-15639, MDEV-15371, MDEV-18797, MENT-1170, MDEV-24979, MDEV-21192)
With MariaDB Enterprise Cluster, when , MariaDB Enterprise Backup does not inherit server options set by the Environment systemd configuration parameter. (MDEV-24962)
With MariaDB Enterprise Cluster, when 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)
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)
A query that uses ORDER BY .. LIMIT clause and "Range checked for each record" optimization could produce incorrect results. (MDEV-25858)
An aborted statement is logged in the binary log and replicates to the Replica server. (MDEV-22530)
For system-versioned tables, the statement displays the system-invisible row_end column as part of the primary key. (MDEV-16857)
For system-versioned tables partitioned by SYSTEM_TIME, overflowing the partitions leads to incorrect results from . result (MDEV-22247)
For tables, statements that use CASE WHEN .. THEN can result in syntax error. (MDEV-24760)
For tables, statements that use the function in the WHERE clause can result in a syntax error. (MDEV-24517)
For tables, statements that call native functions using remove_str (such as ) fail with the ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT error code. (MDEV-24020)
For tables, server-sided prepared statements (created by PREPARE and executed by EXECUTE) incorrectly turn unsigned integer literals into signed integers. (MDEV-25808)
For Spider tables, statements that use the JSON_REPLACE() function fail with the ER_SP_DOES_NOT_EXIST error code. (MDEV-24523)
With , the and statements are not logged to the audit log. (MENT-1169)
With MariaDB Enterprise Backup, the position written to the xtrabackup_binlog_info file during the backup is incorrect for replication. (MDEV-23080)
With MariaDB Enterprise Cluster, when , a typo in the SST script causes SST failure on the Donor node. (MDEV-26117)
For tables, statements that use DISTINCT do not work properly in some cases. (MDEV-26013)
When is compiled with WolfSSL, the server fails to accept connections using TLS 1.3 and AES-GCM cipher. (MDEV-22221)
Concurrent statements can be written to the in the wrong order and break replication. (MDEV-25606)
When an 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)
For INSERT .. RETURNING statements, a qualified asterisk (such as table_name.*) is not supported in the RETURNING clause. (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 . (MDEV-26106)
Example warning:
information schema table added
system variable default value changed from DEFAULT to "" (empty)
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)
5.9
5.5
5.5
5.5
4.4
{
"connect_event" : "ALL",
"table_event" : ["READ","WRITE",{"ignore_tables" : "mysql.*"}],
"query_event" : ["DDL",{"tables" : "test.t2"}]
}tail: cannot open 'mysql-bin.index' for reading: No such file or directoryInnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `schema`.`child_table`[ERROR] InnoDB: Unlock row could not find a 3 mode lock on the record.This page is: Copyright © 2025 MariaDB. All rights reserved.