1 of 26

MariaDB Enterprise Server 10.5

Release notes for MariaDB Enterprise Server 10.5 series releases

Release Notes for MariaDB Enterprise Server 10.5.29-23

MariaDB Enterprise Server 10.5.29-23 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2025-06-11

MariaDB Enterprise Server 10.5.29-23 is a maintenance release of MariaDB Enterprise Server 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

CVE (with link)

CVSS base score

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 ()

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)

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 ()

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)

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

Release Notes for MariaDB Enterprise Server 10.5.28-22

MariaDB Enterprise Server 10.5.28-22 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2025-03-19

MariaDB Enterprise Server 10.5.28-22 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.28-22 was released on 19 Mar 2025.

Fixed Security Vulnerabilities

CVE (with link)

CVSS base score

Changes in Storage Engines

This release incorporates MariaDB ColumnStore engine version 5.6.9.

Notable changes

Galera protocol versions are now shown by show status - change available with installation of galera library 26.4.21+ ()
updated to
- NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated

Issues Fixed

Can result in data loss

Fix incorrect writing of timestamp into binary log, causing discrepancy upon binlog replaying ()
Fix trigger created with "CREATE TRIGGER table1_after_insert AFTER INSERT" which is adding rows to another table using "FOR EACH ROW insert into table2(id, name) values (NEW.id, NEW.name);" that did not work correctly when if bulk inserts are used by the application. Only the first row of the bulk insert would be added to the table (

Can result in hang or crash

Fix client crash the command after client sets character set to utf32 ()
Fix possible crash where server could not construct a geomery object from the input ()
Fix possible Spider thread hang in 'Update' state on 2nd INSERT ()

Can result in unexpected behaviour

Fix sporadic reporting of success when a deadlock error occurs under --ps-protocol BF aborted transaction ()
Fix rare cases where binlog entries could receive incorrect timestamps on secondary nodes of a Galera cluster, potentially impacting replication accuracy ()
For an authentication with the ed25519 authentication plugin the password of the CREATE USER statement is now masked in the audit log ()

Conditions with SP local variables are now pushed into derived table. Previous behaviour caused slow performance and table scans instead of using the pushed down condition ()
NULL-aware materialization with IN predicate and single column no longer skips building sorted Ordered_key structures ()
During an online table rebuild of an InnoDB statistics table, opt_search_plan_for_table() no longer sometimes degrades to full table scan ()

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)

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

Installation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.27-21

MariaDB Enterprise Server 10.5.27-21 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2024-12-10

MariaDB Enterprise Server 10.5.27-21 is a maintenance release of 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

Release Notes for MariaDB Enterprise Server 10.5.26-20

MariaDB Enterprise Server 10.5.26-20 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2024-09-09

MariaDB Enterprise Server 10.5.26-20 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.26-20 was released on 2024-09-09.

Backports

The JSON functions JSON_ARRAY_INTERSECT, JSON_OBJECT_TO ARRAY, and JSON_FILTER_KEYS have been backported from later MariaDB Community Server Release Series to enhance the JSON function coverage in this MariaDB Enterprise Server release series. (MENT-1897)
The new JSON function JSON_ARRAY_INTERSECT(, ) is used to find the intersection between two JSON arrays

Example:

The new JSON function JSON_OBJECT_TO_ARRAY(<json_doc>) is used to convert all JSON objects found in a JSON document to JSON arrays where each item in the outer array represents a single key-value pair from the object. Example:

Resulting arrays can be compared using JSON_ARRAY_INTERSECT():

The new JSON function JSON_OBJECT_FILTER_KEYS(<json_doc>,<array_keys>) returns key/value pairs from a JSON string for keys defined in <array_keys>. Example:

By using JSON_ARRAY_INTERSECT() and JSON_KEY() as arguments for JSON_OBJECT_FILTER_KEYS(), a comparison of two JSON strings is possible where only the same keys are compared, not the key/value pairs. Example (only show key/value pairs of json1 where the key exists in json2):

The new JSON function JSON_KEY_VALUE(<json_doc>,<json_path>) extracts key/value pairs from a JSON object. The JSON path parameter is used to only return key/value pairs for matching JSON objects. (MENT-1896)

Example:

The function JSON_KEY_VALUE() can be used as an argument to JSON_TABLE(), which allows adding the key to a result set. Example:

Notable Changes

A new global variable server_uid can be used to identify a server instance. This Server ID is also logged in the error log file on startup ()
Galera has been updated to 26.4.19
- 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

An ALTER TABLE, OPTIMIZE TABLE, or REPAIR TABLE on an Aria table of ROW_FORMAT=PAGE (default) can fail or possibly corrupt the table, if the data file is bigger than 4GB. ()
When executing an ALTER TABLE
CHECK PARTITION FOR UPGRADE on a table, which was created by the same server version, and therefore does not need an upgrade, a following ALTER TABLE for the same table will result in a server crash. ()
Can result in hang or crash
- When using SHOW CREATE DATABASE statement crashes the server with a database name containing Unicode characters, the server can crash (

Installation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.25-19

MariaDB Enterprise Server 10.5.25-19 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2024-06-11

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

Release Notes for MariaDB Enterprise Server 10.5.19-14

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.

Release Notes for MariaDB Enterprise Server 10.5.6-4

MariaDB Enterprise Server 10.5.6-4 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2020-10-07

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

Release Notes for MariaDB Enterprise Server 10.5.4-1

MariaDB Enterprise Server 10.5.4-1 is an internal release of MariaDB Enterprise Server 10.5, released on 2020-07-16

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.

Release Notes for MariaDB Enterprise Server 10.5.3-1

MariaDB Enterprise Server 10.5.3-1 is an internal release of MariaDB Enterprise Server 10.5, released on 2020-05-21

This release of 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 .

--quick

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..." ()
INSERT...SELECT on MyISAM or ARIA tables are replicated by MariaDB Enterprise Cluster (Galera) ()
SELECT MIN on Spider table returns more rows than expected ()
Can't selectively restore sequences using innodb tables from backup ()
LOAD DATA INFILE with geometry data fails ()
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 ()
Recovery fails to note some log corruption, resulting in "log sequence number in the future" error messages, and possibly adds more corruption ()
- 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 ()
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)

Replicas only read the first 41 characters of MASTER_PASSWORD from the master.info file. This leads to an access denied error for a replica on a server restart, if the password is > 41 characters long. (MDEV-23857)
mariadb-backup stores the password into the tool_command setting in the file xtrabackup_info, if the password is provided as command-line option (MDEV-34434)
The semi-sync binlog fail-over recovery process uses rpl_semi_sync_slave_enabled==TRUE as its condition to truncate a primary server's binlog, as it is anticipating the server to re-join a replication topology as a replica. However, for servers configured with both rpl_semi_sync_master_enabled=1, and rpl_semi_sync_slave_enabled=1, if a primary is just re-started (i.e., retaining its role as master), it can truncate its binlog to drop transactions which its replica(s) has already received, and executed. (MENT-2122)
- If this happens, when the replica reconnects, its gtid_slave_pos can be ahead of the recovered primary's gtid_binlog_pos, resulting in an error state where the replica's state is ahead of the primary's.
- Option --init-rpl-role will be used to define the initial role a server has. Possible options are MASTER and SLAVE, default MASTER . Setting it to SLAVE is now the condition for semi-sync recovery to truncate the binlog, This allows for both rpl_semi_sync_master_enabled, and rpl_semi_sync_slave_enabled to be set for a primary that is restarted, and no transactions will be lost, so long as --init-rpl-role is not set to SLAVE
Command-line option 'defaults-group-suffix=' cannot be used with the script mariadb-secure-installation ()
Grouping operators referring to column aliases in unions inside derived tables can cause name resolution problems with prepared statements. ()
Table mysql.gtid_slave_pos is replicated between two MariaDB Enterprise Cluster although wsrep_gtid_mode=OFF is set. ()
wsrep_sst_mariadb-backup is using /tmp dir during SST instead of an user defined tmpdir ()
The following misleading error message is shown with MariaDB Enterprise Cluster. Galera can mark user threads as high priority and so they can't be killed: ()

After changing the table definition for the system table 'mysql.servers', a following execution of CREATE SERVER would previously lead to a server crash. (MDEV-33783)

+-----------------------------------------------------------------------+
| result                                                                |
+-----------------------------------------------------------------------+
| [["a", [1, 2, 3]], ["b", {"key1": "val1", "key2": {"key3": "val3"}}]] |
+-----------------------------------------------------------------------+

SET @json1='{"a":[1,2,3],"b":{"key1":"val1","key2":{"key3":"val3"}}}';
SET @json2='{"a":[1,2,3]}';
SELECT JSON_OBJECT_TO_ARRAY(@json1) INTO @array1;
SELECT JSON_OBJECT_TO_ARRAY(@json2) INTO @array2;
SELECT JSON_ARRAY_INTERSECT(@array1,@array2) AS result;

+-----------------------------------------------------------------------------+
| JSON_KEY_VALUE('[[1, {"key1":"val1", "key2":"val2"}, 3], 2, 3]', '$[0][1]') |
+-----------------------------------------------------------------------------+
| [{"key": "key1", "value": "val1"}, {"key": "key2", "value": "val2"}]        |
+-----------------------------------------------------------------------------+

SELECT jt.* FROM JSON_TABLE(
JSON_KEY_VALUE('[[1, {"key1":"val1", "key2":"val2"}, 3], 2, 3]', '$[0][1]'),'$[*]'
COLUMNS (
k VARCHAR(20) PATH '$.KEY',
v VARCHAR(20) PATH '$.value',
id FOR ORDINALITY )) AS jt;

Release Notes for MariaDB Enterprise Server 10.5.23-17

MariaDB Enterprise Server 10.5.23-17 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2023-12-12

MariaDB Enterprise Server 10.5.23-17 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.23-17 was released on 2023-12-12.

Fixed Security Vulnerabilities

CVE (with link)

CVSS base score

Changes in Storage Engines

This release incorporates MariaDB Enterprise ColumnStore 5.6.8-2.

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. ()
Race condition between page write completion and log checkpoint on crash recovery. This may break crash recovery in case of an operating system crash or abrupt loss of power or storage connectivity. ()
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. ()

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

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 ()
Replication stops when there exists an exclusive lock on an InnoDB supremum record in prepared transactions on the replica. (

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 an NetApp storage with NFS access ()

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.23-17 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 "".

Installation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.5-3

MariaDB Enterprise Server 10.5.5-3 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2020-09-08

This third release of MariaDB Enterprise Server 10.5 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.5.5-3 was released on 2020-09-08.

Note

With MariaDB Enterprise Server 10.5 "mysql" command names are replaced with "mariadb" command names. Symbolic links are in place to maintain backward compatibility with the old names and prevent disruption. (MDEV-21303)

Fixed Security Vulnerabilities

Notable Changes

UPDATE privilege for system user mariadb.sys removed for system table mysql.global_priv ()
Deprecated InnoDB configuration parameters: ()
- innodb_thread_concurrency
- innodb_commit_concurrency

Issues Fixed

Can result in data loss

doublewrite recovery can corrupt data pages. ()
table can disappear when trying to change primary key after disabling Foreign Key checks and violating a Foreign Key constraint. (MENT-804)
Possible data inconsistency when executing ADD PRIMARY KEY with concurrent DML transactions. ()

Can result in a hang or crash

deadlock in ()
data file extension is not crash-safe. ()
is not crash safe. ()
Deadlock involving parallel workers, , and ()

Can result in unexpected behavior

Service shutdown fails if OS datetime has been updated backwards. ()
ALTER TABLE .. ANALYZE PARTITION can run for hours for huge tables if engine-independent persistent statistics are enabled, due to reading and locking of all rows in the table instead of for the partition. ()
can fail with privilege error when privilege exists at database level but privilege exists at table level. ()

and can't run if the library file doesn't exist. ()

Changes in Storage Engines

This release includes Enterprise (plugin version 1.5.3.2).
This release includes , including ODBC Wrapper support.

Interface Changes

system variable default value changed from 150000 to 0 (now deprecated)
system variable default value changed from 5000 to 0 (now deprecated)
system variable default value changed from 10000

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.5-3 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 "".

Note

MariaDB Enterprise Server 10.5 removes support for Red Hat Enterprise Linux (RHEL) 6 and CentOS 6.

Installation Instructions

Upgrade Instructions

.

0

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >'
what(): remote_endpoint: Transport endpoint is not connected
[ERROR] mysqld got signal 6 ;

0

Release Notes for MariaDB Enterprise Server 10.5.18-13

MariaDB Enterprise Server 10.5.18-13 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2022-12-21

MariaDB Enterprise Server 10.5.18-13 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.18-13 was released on 2022-12-21.

Backported Features

MariaDB Enterprise Server enables a predictable development and operations experience through an enterprise lifecycle. These new features have been backported after reaching maturity in MariaDB Community Server:

The new is available to set the maximum execution time for queries on replica nodes. (MENT-1566, )
- When a query takes more than slave_max_statement_time seconds to run on the replica (slave) node, the query is aborted, and replication stops with an error.
- The system variable can be set to a decimal value, where the decimal component has microsecond precision.
- When set to 0, there is no timeout.

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 the Spider storage engine's ODBC foreign data wrapper is used with MariaDB Connector/ODBC 3.1.10 and later, the server can crash. (MENT-1415)
If the InnoDB change buffer is corrupted, the server can hang during shutdown. (MENT-1673, )
When an InnoDB tablespace is in the non-canonical format from a previous operation that used the , InnoDB can fail to apply changes to the table during crash recovery and while preparing a backup with . ()

When a prepared statement is used to execute an containing a subquery, the server can crash: ()

Can result in unexpected behavior

In the presence of replication filters, revoking privileges from a non-existing user on a primary (master) breaks replication on the replica (slave). ()
When is set on a replica node, the replica node does not skip replicated statements. ()
When a Spider table has a prefix index, query results can be incorrect. ()
InnoDB can extend tablespace files when additional capacity is not required. (

When an InnoDB table contains virtual generated columns that are indexed, InnoDB fails to purge secondary index records. ()
When using the InnoDB adaptive hash index, non-locking reads can return wrong results due to a potential ACID violation. (, , )
When is used on a temporary table, an empty result set is returned. ()
When a sequence is used as the default value in a table, rows inserted by an

When a tablespace file was originally built with MariaDB Enterprise Server 10.4 and earlier, InnoDB would refuse to add a column to the table using the . ()
- In previous releases, the operation would fail with the following error message:

When is executed, spurious errors about table rebuilds are logged. ()
- In previous releases, the following messages would be logged, even though the tool already mitigated the issues itself:

Changes in Storage Engines

This release incorporates MariaDB ColumnStore storage engine version 5.6.8.

Interface Changes

error code added
error code added
error code added
error code added

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.18-13 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 "".

Installation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.24-18

MariaDB Enterprise Server 10.5.24-18 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2024-03-11

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

MariaDB Enterprise Server 10.5.24-18 was released on 2024-03-11.

Changes in Storage Engines

This release incorporates MariaDB ColumnStore engine version 5.6.8-2.

Notable Changes

Galera has been updated to 26.4.17
AlmaLinux 8 and 9 are now officially supported. RHEL 8 and 9 packages are used for AlmaLinux

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

A shutdown of the server with innodb_fast_shutdown=0 can hang after the server failed to start up ()
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 ()

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

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

if the table includes an AUTO_INCREMENT column ()

CHECK TABLE shows a MyISAM/Aria table as corrupted, as a unique hash key on column prefix is computed incorrectly ()
mysql.slow_log reports time when the query finished, not the start time ()
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 ()

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 ()
innodb_undo_log_truncate=ON prevents fast shutdown ()

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.24-18 is provided for:
- AlmaLinux 8 (x86_64, ARM64)
- AlmaLinux 9 (x86_64, ARM64)
- Debian 11 (x86_64, ARM64)

Installation Instructions

Upgrade Instructions

When InnoDB tries to apply a INSERT_HEAP_DYNAMICrecord to a secondary index in a table with ROW_FORMAT=DYNAMIC during crash recovery, the operation can fail with an error. (MDEV-29559)

INSERT ... SELECT

LeakSanitizer

rec_copy_prefix_to_buf_old

is missing the WITH GRANT privilege for roles. (MDEV-24289)
mysqld_safe log messages are missing in the error log file. (MDEV-21367)
CHECK_CLAUSE field in truncates check constraints expressions. (MDEV-24139)
Unexpected error message when selecting from view that uses mergeable derived table. ()
Permission denied error message is returned on users with permissions for nested CTEs. ()
Regression: SELECT .. UNION .. with inconsistent column names fails. ()
Race condition between and transaction commit with . ()
Plugin system variables and activation options can break for . ()
SELECT INTO OUTFILE used permission 666 where 644 should be used to limit the privileges to change the file. ()
Syntax error on correct syntax for that includes X is null = 0 ()
Altered connection limits for user have no effect. ()
Syntax error when using COLLATE for creating virtual columns. ()
Auto purge of relaylogs stops when relay-log-file is slave-relay-log.999999 and is enabled. ()
ORDER BY in view definition leads to wrong result with GROUP BY on query using view. ()
column from a derived table returns invalid values. ()
doesn't respect filters for PROXY_CONNECT events. ()
plugin doesn't consider proxy users in and ()
With ALTER USER .. IDENTIFIED BY command, password isn't replaced by asterisks in audit log. (MENT-1128)
does not insert history row for or application period based tables if the row has not changed. ()
Wrong duplicate primary key error between the history row generated on referential action and the history row on evaluating foreign referential action for self-reference in a table. (, )
Wrong number of decimal digits in certain UNION or subquery constellations, like union of unsigned and NULL type. ()
[CREATE TABLE](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/data-definition/create/create-table) .. SELECT FROM does not create table if is not using a scalar value. ()
InnoDB may report incorrect binlog position information after ()
Sequences which are used as default by a table are not dumped in right order by ()
generates invalid SQL for user where password expiry and account lock set. ()
Garbd of can't initiate SST ()
Misleading error message from might be interpreted as a point in time recovery is not possible. ()
High memory usage in the optimizer when a query is using SELECT .. FROM tbl .. WHERE unique_key not in (long-list) AND .. unique_key not in (long-list) AND .. ()
for tables with CHECK CONSTRAINTS returns with Out of Memory error. ()
Alter rename table does not remove table from when using algorithm=copy ()
Persistent statistics are lost for table after ()
The default setting of has effects on with results in a performance regression. ()
Accessing may break innodb_open_files logic. ()
reports garbage. ()
S3, same-backend replication: Dropping a table on primary causes error on replica. ()
privilege is missing from ()
Flushing starts only when 90% (srv_max_buf_pool_modified_pct) pages are modified. ()
Quick memory exhaustion with extended_keys=on on queries having multiple or using InnoDB. ()

wsrep::transaction::before_rollback(): 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

Release Notes for MariaDB Enterprise Server 10.5.21-15

MariaDB Enterprise Server 10.5.21-15 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2023-06-13

MariaDB Enterprise Server 10.5.21-15 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.21-15 was released on 2023-06-13.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

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

Notable Changes

For compatibility, has been added as an alias to JSON_DETAILED(). ()
InnoDB's internal performance has been improved. ()
The is added as read-only. ()
The default value for the has been changed from None to OFF. ()

Starting with this release, the must be configured in a configuration file prior to starting up the server:

The is added as read-only. ()
- The --aria-log-dir-path command-line option is added to mariadb-backup.
By default, no longer prints messages about log scanning. ()

Starting with this release, the messages about log scanning are only printed when is enabled.

Issues Fixed

Can result in data loss

When a backup is created with and is configured, the Aria logs are not copied to the backup. ()
When system versioning is enabled for a table without a primary key, changes to the table are not properly replicated. ()
When a partitioned table contains a prefix index on a column that uses a NOPAD collation, queries with ORDER BY can return rows in the wrong order. ()

When a index includes a PERIOD in its definition, a duplicate key error can be incorrectly raised when the table uses the . ()

Can result in a hang or crash

When an UPDATE or DELETE is rolled back from an InnoDB table with ROW_FORMAT=COMPRESSED, the server can crash. ()
When the function is called on a string that has no character set defined, the server can crash. ()
With Galera, when is set and encrypt=4 is enabled for State Snapshot Transfers (SSTs), SSTs can fail if the version of socat installed on the donor node is 1.7.4.0 or later. ()

Starting with this release, when the SST script starts the socat listener on the donor node, the error is prevented by setting no-sni=1 if the version of socat installed is 1.7.4.0 or later.
When optimizer trace is enabled, if a view is part of a multi-table update, the server can crash. ()
When a view definition contains a UNION and the view is queried using server-side prepared statements, if the optimizer pushes down a condition into the execution of the view, the server can crash during character set conversions. (

With Galera, when streaming replicating is enabled by setting the , the server can crash when certain fragment sizes are specified. ()
When EXPLAIN EXTENDED is executed for a single-table DELETE that contains an IN(..) predicand, the server can crash. ()
When parallel replication is enabled by setting greater than 0, the replica's parallel replication worker threads could hang after hitting an error. ()

In this scenario, this issue causes one of the parallel replication worker threads to hang in the closing tables state, so the output of SHOW PROCESSLIST would show one worker thread in that state indefinitely:

When the optimizer chooses how to split a semi-join, the server can crash. ()
With Galera, when CREATE TEMPORARY SEQUENCE is executed on a cluster node and binary logging is enabled, the server crashes. ()
With Galera, when a write set fails certification and binary logging is enabled, the WSREP sequence numbers (cluster-wide transaction IDs) used by a WSREP applier thread can become out of sync with the node's XIDs (internal transaction IDs) due to a race condition, which can cause the node to crash. ()

Starting with this release, the server prohibits CREATE TABLE .. SELECT in this scenario and raises the with the following error message:

With Galera, when a connection uses the handler interface to start a transaction on a table, the server can crash when the client disconnects. () In previous releases, when the client disconnected, the server would rollback the transaction and release all locks, including the locks that the handler interface expected to survive after the transaction ended, which would cause the server to crash.
- In previous releases, the following assertion is written to the MariaDB error log during the crash:

With Galera, when an SST donor changes to the non-primary state, the SST is not terminated properly, and the donor node crashes. (MENT-1708)
- In previous releases, the following error message and assertion is written to the MariaDB error log during the crash:

When a query is executed that uses DISTINCT and an aggregate function on a group, the server can crash. ()
When a server-side prepared statement is used to execute a query that references views and contains a HAVING clause, the server can crash upon second execution of the query. ()
When the InnoDB purge thread tries to use the change buffer for an uncommitted index, the server aborts with an assertion. ()

Starting with this release, when Galera is enabled, mixed transactions are rejected in with the following error message:

When InnoDB uses a lot of memory during crash recovery, the server can hang due to a race condition between the thread flushing the buffer pool and the thread performing the recovery. ()
With Galera, when streaming replicating is enabled by setting the , the server can crash when backup locks or user-level locks are released. ()
With Galera, when one session is terminated using the and another session's transaction is aborted by the WSREP applier threads due to a conflict, the two operations use a conflicting mutex locking order, which can cause the node to hang. ()

Can result in unexpected behavior

When EXPLAIN EXTENDED is executed for a multi-table UPDATE that uses the system join type, the output can be incorrect. ()
When a query specifies DISTINCT and contains expressions using the SUM() function, the wrong results are returned. ()
When a view's definition contains a HAVING clause, selecting from the view can fail with an error. (

When a view's definition contains an aggregate function, selecting from the view can fail with an error. ()
- In previous releases, queries could raise an error with the and the following error message:

When a view's definition contains a table-value constructor (TVC) as a single-value subquery, selecting from the view can fail with an error. ()
- In previous releases, queries could raise an error with the and the following error message:

When a view's definition contains an aggregate function in an uncorrelated subquery, the wrong result is returned. ()
When a DELETE statement contains a subquery with a HAVING clause or an aggregate function in the WHERE clause, the statement can fail with an error. ()
- In previous releases, queries could raise an error with the ER_INVALID_GROUP_FUNC_USE

When an InnoDB tablespace has been discarded, selecting from fails with an error. ()
- In previous releases, an error with the is raised:

Starting with this release, no error is returned, and the results contain NULL for the PAGE_NO and SPACE columns for discarded tablespaces.
When is set to a relative path, the path is not properly used by . ()
- In previous releases, the undo logs would be copied to the relative path compared to the current working directory.

When an UPDATE contains a WHERE clause that contains a range condition over a non-indexed VARCHAR column, an error is raised. ()
- In previous releases, an error with the is raised with the following error message:

When slave_parallel_threads is greater than 0 and SHOW SLAVE STATUS is executed, the connection can try to acquire an uninitialized mutex. ()
- In previous releases, a race condition could cause the mutexes of parallel replication worker threads to be acquired before they are initialized.
The ucs2_general_mysql500_ci

Changes in Storage Engines

This release incorporates MariaDB ColumnStore engine version 5.6.8-2.

Interface Changes

system variable added.
system variable default value changed from None to OFF
system variable dynamic changed from Yes to No
For compatibility, has been added as an alias to JSON_DETAILED().

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.21-15 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 "".

Installation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.15-10

MariaDB Enterprise Server 10.5.15-10 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2022-03-14

MariaDB Enterprise Server 10.5.15-10 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.15-10 was released on 2022-03-14.

Fixed Security Vulnerabilities

CVE (with link)

CVSS base score

Notable Changes

Galera updated to 26.4.11
The maximum values for and have been changed from 80000000 to 1099511627776 (1 TB). (MENT-1428)
On Windows, core_file is enabled by default. ()

Crash recovery improvements for InnoDB (, , , )
The default value of has been changed to none. ()

Issues Fixed

Can result in data loss

Columns in some INFORMATION_SCHEMA tables are erroneously declared with DEFAULT clauses, which is not compliant with the SQL standard. ()
- Consequently, when sql_mode=EMPTY_STRING_IS_NULL is set, queries like CREATE TABLE .. SELECT .. FROM INFORMATION_SCHEMA... could encounter replication errors like the following:

When an statement changes the order of indexes in a MyISAM or Aria table using the INPLACE algorithm, the table can become corrupt. ()
When is written to the binary log, the statement is not flagged as DDL, which causes the replica servers to execute the statement in an unsafe way if parallel replication is enabled. ()
After upgrading from or earlier, the names of some triggers can appear empty, and the trigger can't be dropped. ()

Can result in a hang or crash

When a FULLTEXT index is added to an InnoDB table with ALGORITHM=INPLACE and the indexed column uses the tis620 character set, the server can crash with a segmentation fault (signal 11). ()
When MariaDB Server is used on the ARM architecture, which uses a weak memory model, an internal hash table implementation can cause the server to crash with a segmentation fault (signal 11). ()
When and are set with MariaDB Enterprise Cluster, powered by Galera, the joiner node fails to perform an SST. (

When is set, MariaDB Enterprise Backup can hang on lock acquisitions due to a deadlock. ()
When a stored procedure is defined with a query that contains a set function, and the set function's only argument is an outer reference to a column of a mergeable view, a derived table, or a CTE, the second execution of the stored procedure can cause the server to crash. ()
When a derived table is created for certain queries that use subqueries over Views or CTEs, the server can crash with a segmentation fault (signal 11). ()

With MariaDB Enterprise Cluster, when a statement that defines a Foreign Key constraint is replicated to other cluster nodes, the nodes could apply the statement in parallel with other DML statements that affect the Foreign Key constraint, which causes the node to fail with an assertion failure. ()
With MariaDB Enterprise Cluster, when two transactions delete a row from two separate InnoDB tables in parallel and a foreign key causes a delete to cascade for both transactions to the same row in a third table, the server can crash with an assertion failure. (, )
- In previous releases, this issue could be avoided by setting .

When and are set, the server could crash with an assertion failure. ()
- In the MariaDB error log, the following message about the assertion failure could be written:

When InnoDB does not use RAM disk for storage, the server can occasionally hang during a log checkpoint. ()
When using , the server can crash due to memory corruption. ()
When is executed, the server could try to lock the Aria control file. ()
- In the MariaDB error log, the following error messages could be written about this:

When an index is dropped and re-adding to a table in a different position using the INPLACE algorithm and the table uses the MEMORY storage engine, the server can crash. ()

`Can result in unexpected behavior`

When a multi-byte character set is used, the last character of a column can be truncated, which makes it appear as a question mark ('?). ()
Subquery using the ALL keyword on columns produces a wrong result. ()
Subquery using the ALL keyword on columns produces a wrong result. ()

With MariaDB Enterprise Audit, prepared statements can't be used to enable audit logging. (MENT-379)
- In previous releases, using a prepared statement to set the system variable would fail with the following error message:

When a proxy user is used for authentication, the server checks the proxy user account for the following security controls: ()
- SSL/TLS requirements
- Account locking
- Password expiration

When the mysql.AddGeometryColumn and mysql.DropGeometryColumn stored procedures use the old default DEFINER = 'root@localhost', does not alter them to use the new default DEFINER = 'mariadb.sys@localhost'. ()
When MariaDB Server is upgraded from 10.2, 10.3, or 10.4, InnoDB upgrades the redo log format in a manner that is not crash-safe. ()

Changes in Storage Engines

This release incorporates MariaDB ColumnStore storage engine version 5.6.5.

`Interface Changes`

error code added
system variable minimum value changed from 5242880 to 2097152
system variable dynamic changed from No to Yes

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.15-10 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 "".

Installation Instructions

Upgrade Instructions

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 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 link)

CVSS base score

Backported Features

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.

Notable Changes

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

Issues Fixed

Can result in data loss

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

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

Can result in unexpected behavior

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. (

Changes in Storage Engines

This release incorporates MariaDB ColumnStore storage engine version 5.6.2.

Interface Changes

error code error number changed from 4174 to 6000
information schema table added
mariadbd --server-audit-load-on-error command-line option added

Platforms

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 "".

Installation Instructions

Upgrade Instructions

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.

*************************** 1. row ***************************
                Slave_IO_State: Waiting for master to send event
..
              Slave_IO_Running: Yes
             Slave_SQL_Running: Yes
..
                    Last_Errno: 1062
                    Last_Error: Could not execute Write_rows_v1 event on table TABLE_NAME; Duplicate entry 'VALUE' for key 'KEY_NAME', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log LOG_FILE, end_log_pos END_LOG_POS
..

+------+--------------+--------------------+------+--------------+-------+-----------------------------------------------+------------------+----------+
| Id   | User         | Host               | db   | Command      | Time  | State                                         | Info             | Progress |
+------+--------------+--------------------+------+--------------+-------+-----------------------------------------------+------------------+----------+
..
| 2394 | system user  |                    | NULL | Slave_worker | 50852 | closing tables                                | NULL             |    0.000 |
..
+------+--------------+--------------------+------+--------------+-------+-----------------------------------------------+------------------+----------+

[Warning] WSREP: server: NODE_NAME unallowed state transition: connected -> joined
void wsrep::server_state::state(wsrep::unique_lock<wsrep::mutex>&, wsrep::server_state::state): Assertion `0' failed.

[ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 0 seconds
[ERROR] Plugin 'Aria' init function returned error.
[ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.

With MariaDB Enterprise Cluster, powered by Galera, when wsrep_sst_method is set to rsync or mariadb-backup, the donor node does not transfer the correct binary logs to the joiner node with some configurations. (MDEV-27524)
When a window function is used in the global ORDER BY clause of a with a UNION, the statement should be rejected, but the server executes the statement and crashes with a segmentation fault. (MDEV-15208)
When a stored procedure queries a view and uses a for loop, the server can crash with a segmentation fault when the stored procedure is called twice in the same session. (MDEV-26009)
When is executed on an encrypted tablespace file using the --page-type-summary or -S option, innochecksum crashes with a segmentation fault unless the --page-type-dump or -D option is also specified. ()
When an invalid statement is used inside of a or statement, the server can crash while parsing the statement. ()
When a table contains a virtual generated column that is defined using the and functions, inserting a row into the table can cause the server to crash with a segmentation fault. ()
When a non-updateable view is defined with ALGORITHM=TEMPTABLE, selecting data from the view can cause the server to crash with a segmentation fault. ()
When a UNION of decimal types is performed in an ORDER BY clause, the server can crash with a segmentation fault. ()
When a stored procedure executes a query that results in a mergeable derived table, the server can crash with a segmentation fault when the stored procedure is called twice in the same session. ()
- Querying views can result in mergeable derived tables.
- Using subqueries with outer references can result mergeable derived tables.
When is executed with a query that contains a subquery, the server can crash. ()
When a query using a window function with an OVER (PARTITION BY ..) or VER (ORDER BY ..) clause is executed, the server can crash with a segmentation fault. ()
- If the query also uses WITH ROLLUP, this crash is more likely.
- If the query's OVER (PARTITION BY ..) or OVER (ORDER BY ..)
When a query contains an outer join expression and a non-correlated subquery that the optimizer determines is low cost, executing the query can cause the server to crash if the optimizer also determines that the inner join expression can be eliminated. ()
With MariaDB Enterprise Cluster, a joiner node's binary logs could be deleted during an Incremental State Transfer (IST), which causes the node to fail to start, because it can not read the binary logs. ()
- This issue is confirmed to happen with set to rsync, but it might also occur with other SST/IST methods.
Online DDL fails while checking for instant alter condition. ()
With MariaDB Enterprise Cluster (Galera), parallel async replication hangs on a Galera node when slave-parallel-threads greater than 1 is used. ()
With MariaDB Enterprise Cluster (Galera), possible crash after a conflict of the applier thread with a stored procedure call triggered by the event scheduler. ()
Server crashes when executing a shutdown statement after starting an XA transaction. ()
Possible server crash during mariadbd initialization if the number of GTIDs added since the last purge of the mysql.gtid_slave_pos tables is greater than or equal to the --gtid-cleanup-batch-size value. ()
Possible server crash if an INSERT .. SELECT or REPLACE .. SELECT statement contains an ON expression in the top-level select and this expression used a subquery with a column reference. ()

Galera snapshot transfer fails to upgrade between some major versions. (MDEV-27437)
On Windows, MSI installer does not install client shared libraries. (MDEV-28581)
When the is loaded, should be used to take a logical backup before all minor and major upgrades due to changes that are not backward-compatible:
- Starting with this release, the rejects encryption keys that contain non-digit characters in the hex notation.
- If a database is encrypted with encryption keys that only contain digit characters in the hex notation, the encryption keys will continue to work with the new version.
- If a database is encrypted with encryption keys that are no longer valid, it is recommended to upgrade by installing the new version to a clean system and restoring a logical backup of the data. However, another alternative is to migrate the system to a new encryption key that only contains digit characters in the hex notation prior to the upgrade. If the alternative route is taken, extra care must be taken to ensure that all encrypted data uses the new encryption key. For help with this process, contact .
- When performing minor and major upgrades on Debian and Ubuntu, a logical backup must be taken before upgrading the server and plugin packages. When the old packages are upgraded, a message about plugin incompatibility is printed, but the server and plugin packages are upgraded anyway.
- When performing minor upgrades on CentOS, RHEL, Rocky Linux, and SUSE, a logical backup can be taken before or after upgrading the server package. When the old packages are upgraded, a message about plugin incompatibility is printed, and the server package is upgraded, but the plugin package is not. The old plugin package must be manually removed, and then the new plugin package can be installed.
- When performing major upgrades on CentOS, RHEL, Rocky Linux, and SUSE, a logical backup must be taken before upgrading the server and plugin packages. The old server and plugin packages must be manually removed, and then the new server and plugin packages can be installed.
- When the plugin package is manually removed, the plugin configuration file can also be removed, so it is recommended to backup the file.

What's New in MariaDB Enterprise Server 10.5?

An overview of changes, improvements, and what's new in MariaDB Enterprise Server 10.5

MariaDB Enterprise Server 10.5 introduces the new features listed below.

Notable Features

Enterprise ColumnStore Storage Engine

The is a columnar storage engine that provides distributed, columnar storage for scalable analytical processing and smart transactions.

MariaDB Enterprise Server 10.5 includes an enterprise version of the as a plugin:

It includes MariaDB Enterprise ColumnStore 5, which has many improvements.
The installation process has been massively simplified.
The multi-node implementation has been completely rebuilt to use a REST API for orchestration.
See ? for more details.

Other Features

Embracing the MariaDB Name

MariaDB Enterprise Server 10.5 uses the "MariaDB" name in more places:

It uses MariaDB in many error messages that previously referred to MySQL.
It uses DBD::MariaDB for bundled Perl scripts that previously used DBD::mysql.
It uses new MariaDB-based names as the primary names for many executables. The old names are still supported for backward compatibility using symbolic links. The new MariaDB-based names were first introduced in MariaDB Enterprise Server 10.4. However, in that version, the old names were still the primary names for the executables, and the new names were supported using symbolic links. See below for the new MariaDB-based names:

Old Executable Name

New Executable Name

Packaging

MariaDB Enterprise Server 10.5 includes some packaging improvements:

It includes a new mariadb-conv command-line tool to encode/decode MariaDB-encoded file system names.
Binary tarball packages have the following changes:
- Embedded server (libmysqld) has been removed.

InnoDB Storage Engine

The is an ACID-compliant storage engine that is very performant and reliable for general purpose transactional workloads.

MariaDB Enterprise Server 10.5 includes many significant improvements to the :

It implements a new thread pool for InnoDB background tasks, which allows for InnoDB to use system resources more efficiently.
- It reduces semaphore contention in several areas to help the system perform better under high concurrency:
- It reduces semaphore contention when accessing the buffer pool.
- It removes the ability to configure multiple buffer pool instances, since it does not reduce contention.

Spider Storage Engine

The allows you to build complex and powerful distributed databases using federated and sharded tables.

MariaDB Enterprise Server 10.5 contains several enhancements for the storage engine:

It adds support for an . This feature has beta maturity.
It adds the table.

Aria Storage Engine

The is a crash-safe storage engine that is incredibly fast for read-only workloads.

MariaDB Enterprise Server 10.5 contains several enhancements for the :

It handles the statement by blocking commits to Aria tables, which allows for safer backups with .
It increases the index length limit for Aria tables from 1000 bytes to 2000 bytes.

S3 Storage Engine

MariaDB Enterprise Server 10.5 contains several enhancements to the :

The S3 storage engine allows tables to be archived in S3-compatible storage.
Tables can be archived in S3 by executing .
After the table has been archived, it becomes read-only.
The S3 storage engine supports partitioning.

Privileges Comparison ES10.4 and ES10.5.8-5

MariaDB Enterprise Server 10.5 adds privileges that allow operations that previously required the . The following table is a summary of the changes between MariaDB Enterprise Server 10.4 and MariaDB Enterprise Server 10.5.8-5. More specific detail is found in , and in .

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements
Allows the user to the following system variables:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

privilege is an alias for this new privilege, but the capabilities have changed
Unlike legacy REPLICATION CLIENT privilege, can no longer execute SHOW SLAVE STATUS, SHOW REPLICA STATUS in ES10.5
BINLOG MONITOR allows the user to execute statements
BINLOG MONITOR allows the user to execute statements

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements, which are output by
Allows the user to execute statements when is set to replication
Allows the user to set the session values of several system variables that are usually included in statements:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Skips the execution of when the user connects
Ignores when the user connects
Ignores when the user connects
Ignores when the user connects

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to execute statements

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to write data even if the system variable is enabled
Allows the user to execute statements even if the system variable is enabled
Allows the user to execute statements even if the system variable is enabled
Allows the user to set system variables:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

REPLICA MONITOR is a new privilege in ES10.5.8-5 and was not present in earlier releases
REPLICA MONITOR can execute:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Replaced by in 10.5
REPLICATION CLIENT can be used as an alias for BINLOG MONITOR but the capabilities for BINLOG MONITOR are different than those of legacy REPLICATION CLIENT
- Unlike legacy REPLICATION CLIENT privilege, can no longer execute SHOW SLAVE STATUS, SHOW REPLICA STATUS in ES10.5
- REPLICATION CLIENT as an alias for BINLOG MONITOR:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to set system variables:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Added in ES10.5 as an alias for

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Can be used as an alias for
In ES10.5 REPLICATION SLAVE can no longer execute SHOW RELAYLOG EVENTS. In ES10.5 versions earlier than ES10.5.8-5, SHOW RELAYLOG EVENTS requires . In ES10.5.8-5, SHOW RELAYLOG EVENTS requires
In ES10.5 REPLICATION SLAVE can no longer execute . SHOW BINLOG EVENTS requires
If a user upgrades from ES10.4 or earlier to ES10.5.8-5 or later, any users with REPLICATION CLIENT or REPLICATION SLAVE privileges will automatically be granted the REPLICA MONITOR privilege. This privilege upgrade happens upon server startup, so mysql_upgrade is not required

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Alias for
Capabilities changed in ES10.5.8-5 with the following abilities removed from REPLICATION SLAVE ADMIN and now granted with :

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Alias for see for details

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to set the definer of views, triggers, stored procedures, stored functions, and events
Allows the user to view the definer of an object, even if the user account no longer exists. |

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

SLAVE MONITOR is a new privilege in ES10.5.8-5 and was not present in earlier releases
SLAVE MONITOR can execute:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

The SUPER privilege is present in ES10.4 and ES10.5 but the capabilities have changed. New privileges have been added in ES10.5 to provide finer grained control and reduce the need to grant SUPER privileges
With the addition of the new privileges in ES10.5, SUPER:
- no longer executes SHOW MASTER STATUS, SHOW BINLOG STATUS, and SHOW BINARY LOGS. Those require BINLOG MONITOR in ES10.5
- no longer sets the definer for views, triggers, functions, procedures, and events in ES10.5. Those capabilities require SET USER in ES10.5

Privileges Comparison ES10.4 and ES10.5 before ES10.5.8-5

MariaDB Enterprise Server 10.5 adds privileges that allow operations that previously required the . The following table is a summary of the changes between MariaDB Enterprise Server 10.4 and MariaDB Enterprise Server 10.5 before MariaDB Enterprise Server 10.5.8-5. More specific detail is found in , and in .

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements
Allows the user to the following system variables:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Legacy privilege is an alias for this new privilege, but the capabilities have changed
Unlike legacy REPLICATION CLIENT privilege, can no longer execute SHOW SLAVE STATUS, SHOW REPLICA STATUS in ES10.5
BINLOG MONITOR allows the user to execute statements
BINLOG MONITOR allows the user to execute statements

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements, which are output by
Allows the user to execute statements when is set to replication
Allows the user to set the session values of several system variables that are usually included in statements:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Skips the execution of init_connect when the user connects
Ignores max_connections when the user connects
Ignores max_user_connections when the user connects
Ignores max_password_errors when the user connects

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to execute statements

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to write data even if the system variable is enabled
Allows the user to execute statements even if the system variable is enabled
Allows the user to execute statements even if the system variable is enabled
Allows the user to set system variables:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Replaced by in 10.5
REPLICATION CLIENT can be used as an alias for BINLOG MONITOR but the capabilities for BINLOG MONITOR are different than those of legacy REPLICATION CLIENT
Unlike legacy REPLICATION CLIENT privilege, can no longer execute SHOW SLAVE STATUS, SHOW REPLICA STATUS in ES10.5
REPLICATION CLIENT as an alias for BINLOG MONITOR:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to set system variables:

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Added in ES10.5 as an alias for

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Can be used as an alias for
In ES10.5 REPLICATION SLAVE can no longer execute SHOW RELAYLOG EVENTS. In ES10.5 versions earlier than ES10.5.8-5, SHOW RELAYLOG EVENTS requires . In ES10.5.8-5, SHOW RELAYLOG EVENTS requires
In ES10.5 REPLICATION SLAVE can no longer execute . SHOW BINLOG EVENTS requires
If a user upgrades from ES10.4 or earlier to ES10.5.8-5 or later, any users with REPLICATION CLIENT or REPLICATION SLAVE privileges will automatically be granted the REPLICA MONITOR privilege. This privilege upgrade happens upon server startup, so mysql_upgrade is not required

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Alias for REPLICATION SLAVE ADMIN
Capabilities changed in ES10.5.8-5 with the following abilities removed from REPLICATION SLAVE ADMIN and now granted with :

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Alias for see for details

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

Allows the user to set the definer of views, triggers, stored procedures, stored functions, and events
Allows the user to view the definer of an object, even if the user account no longer exists.

Present in ES10.4?

Present in ES10.5.8-5?

Notes:

The SUPER privilege is present in ES10.4 and ES10.5 but the capabilities have changed. New privileges have been added in ES10.5 to provide finer grained control and reduce the need to grant SUPER privileges
With the addition of the new privileges in ES10.5, SUPER:
- no longer executes SHOW MASTER STATUS, SHOW BINLOG STATUS, and SHOW BINARY LOGS. Those require BINLOG MONITOR in ES10.5
- no longer sets the definer for views, triggers, functions, procedures, and events in ES10.5. Those capabilities require SET USER in ES10.5

MariaDB Replication

MariaDB Enterprise Server 10.5 improves :

It allows extended table metadata to be written to the binary log by configuring the system variable.
It changes the default parallel replication mode from conservative to optimistic.
It renames the REPLICATION CLIENT privilege to BINLOG MONITOR, but it still supports the old name.

BINLOG MONITOR (formerly REPLICATION CLIENT)

Newly Granted Operations:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to execute statements
Allows the user to execute statements

BINLOG ADMIN

** Granted Operations:**

Allows the user to execute PURGE BINARY LOGS statements
Allows the user to set system variables:

BINLOG REPLAY

Granted Operations:

Allows the user to execute statements, which are output by
Allows the user to execute statements when is set to replication
Allows the user to set the session values of several system variables that are usually included in statements:

REPLICATION MASTER ADMIN

Granted Operations:

Allows the user to execute SHOW REPLICA HOSTS statements
Allows the user to execute SHOW SLAVE HOSTS statements
Allows the user to set system variables:

REPLICATION SLAVE ADMIN

Granted Operations:

Allows the user to execute statements, which are output by
Allows the user to execute statements
Allows the user to execute statements
Allows the user to execute statements

Statement Aliases

It adds aliases for statements that contain the word SLAVE that also allow the word REPLICA:

Statement

New Statement Alias

It adds the shutdown_wait_for_slaves system variable to control whether a replication-aware shutdown is the default shutdown behavior.

MariaDB Enterprise Cluster

MariaDB Enterprise Server 10.5 improves support for :

It allows Galera Cluster to be configured to prohibit DDL replication to only the storage engines that support Galera Cluster by configuring the system variable.
It adds full GTID support to Galera Cluster.
It adds an inconsistency voting protocol to mitigate the harm of inconsistencies by choosing very carefully which inconsistent nodes need to abort.
It adds support for when is set to NBO, including:

Temporal Data

MariaDB Enterprise Server 10.5 improves support for :

It allows that are partitioned on an interval of SYSTEM_TIME to be configured with a specific start date and time, which can make partition management more user-friendly.
It allows to be configured to prohibit overlapping time periods.

SQL Functionality

MariaDB Enterprise Server 10.5 improves SQL functionality in several areas:

It changes the behavior of the statement to forcefully drop the table, even if the storage engine can't find the table.
It changes the behavior of the statement, so that it no longer flushes the table definition cache, so that it performs better under concurrency.
It changes the behavior of the statement to SHOW the time spent checking the WHERE clause.
It adds support for statements.

Security

MariaDB Enterprise Server 10.5 includes several improvements:

It allows a server to be configured to by configuring the system variable.
- If this mode is enabled, then all TCP connections must use TLS.
- Local connections that connect using a Unix socket or a named pipe are also allowed.
It adds the CONNECTION_TYPE

BINLOG MONITOR (formerly REPLICATION CLIENT)

Newly Granted Operations:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to execute statements
It adds new privileges to allow operations that previously required the SUPER privilege.

Granted Operations:

Allows the user to execute statements
Allows the user to set system variables:

Granted Operations:

Allows the user to execute BINLOG statements, which are output by mariadb-binlog
Allows the user to execute SET TIMESTAMP statements when secure_timestamp is set to replication
Allows the user to set the session values of several system variables that are usually included in BINLOG statements:

CONNECTION ADMIN

Granted Operations:

Skips the execution of init_connect when the user connects
Ignores max_connections when the user connects
Ignores max_user_connections when the user connects
Ignores max_password_errors when the user connects

FEDERATED ADMIN

Granted Operations:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to execute statements

READ ONLY ADMIN

Granted Operations:

Allows the user to write data even if the system variable is enabled
Allows the user to execute DROP TRIGGER statements even if the system variable is enabled
Allows the user to execute START TRANSACTION READ WRITE statements even if the system variable is enabled
Allows the user to set system variables:

REPLICATION MASTER ADMIN

Granted Operations:

Allows the user to execute statements
Allows the user to execute statements
Allows the user to set system variables:

REPLICATION SLAVE ADMIN

Granted Operations:

Allows the user to execute statements, which are output by
Allows the user to execute statements
Allows the user to execute STATUS statements
Allows the user to execute statements

SET USER

Granted Operations:

Allows the user to set the definer of views, triggers, stored procedures, stored functions, and events.○ Allows the user to view the definer of an object, even if the user account no longer exists

HashiCorp Vault Encryption Plugin

MariaDB Enterprise Server 10.5 introduces an encryption plugin to support for :

It allows HashiCorp Vault to manage encryption keys for .
It communicates with the remote KMS using TLS.
It supports key rotation.

Performance Schema

MariaDB Enterprise Server 10.5 includes several improvements:

It adds support for some of the instrumentation and tables included in MySQL 5.7.
It adds the CONNECTION_TYPE column to the threads table, which can be used to determine which connections are using TLS.
It adds new instrumentation for the following:

Information Schema

MariaDB Enterprise Server 10.5 includes several improvements:

It adds the GLOBAL_VALUE_PATH column to the table, which can be used to determine which configuration file a variable's global value was read from.
It adds new tables to monitor the internals of the thread pool on Linux:

Thread Pool

MariaDB Enterprise Server 10.5 includes several thread pool improvements:

It improves how it calculates the number of currently active threads, which can help prevent deadlocks.
It improves performance under very bursty workloads by basing the thread creation rate and the throttling interval on the values of the and system variables.
It adds new tables to monitor the internals of the thread pool on Linux:

Protocol

MariaDB Enterprise Server 10.5 includes several protocol improvements:

It adds protocol support for the new Data Type API.
It adds protocol support for the data type.
It adds protocol support for the data type.

XA Transactions

MariaDB Enterprise Server 10.5 includes some XA transaction improvements:

It allows prepared XA transactions to be properly recovered after a client disconnects.

Internals

MariaDB Enterprise Server 10.5 includes some internal improvements:

Its internal regular expression library has been upgraded from PCRE to PCRE2.
It adds support for a new Data Type API, so that plugins can define custom data types.

For a complete list of changes, see .

Release Notes for MariaDB Enterprise Server 10.5.22-16

MariaDB Enterprise Server 10.5.22-16 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2023-09-11

MariaDB Enterprise Server 10.5.22-16 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.22-16 was released on 2023-09-11.

Backports

has been backported. (MENT-1853)
- The JSON_OVERLAPS() function can be used to compare two JSON documents to determine if they have any key-value pairs or array elements in common.

has been backported. (MENT-1796)
- The JSON_SCHEMA_VALID() function can be used to validate a JSON document against a JSON schema, as documented by the .
- This function can also be used in a CHECK constraint to verify that JSON documents are only stored in the database if they include required items and that the values are within a given range and length.

Notable Changes

The package for the cracklib_password_check plugin includes an SELinux policy, allowing the plugin to work with SELinux. ()
With Optimizer Trace, a sel_arg_alloc_limit_hit record is written when MAX_SEL_ARGS is reached. ()
- MAX_SEL_ARGS

ANALYZE FORMAT=JSON output includes InnoDB statistics. ()
- For example:

Slow query log output includes InnoDB engine information. ()
- InnoDB engine information output is enabled with --log-slow-verbosity=innodb
- Sample output:

For the Spider storage engine, the default values and behavior of some system variables has changed: ()
- Prior to this release:
  - These variables used a value of -1 (the default) to indicate that Spider would use the default table value, and this value was not user visible.

Issues Fixed

Can result in data loss

With InnoDB storage engine, when innodb_undo_log_truncate=ON, performing a recovery can result in a corrupted undo log. ()
With InnoDB storage engine, when database encryption is enabled only on a replica, InnoDB pages can be corrupted. (, )
With InnoDB storage engine, when innodb_undo_log_truncate=ON, backup and recovery can fail. ()

Can result in a hang or crash

With Aria storage engine, when Aria encryption is enabled and used but an encryption plugin is not loaded, the server can crash. ()
With Galera Cluster, when wsrep_sst_donor and wsrep_cluster_address are set to NULL rather than an empty string, the server can crash. ()
When optimizer_switch='optimize_join_buffer_size=off' is set, the server can crash. (

Can result in unexpected behavior

For a System Versioned table with non-versioned columns, if the initial INSERT includes a versioned column, an "on duplicate key update" for the non-versioned column generates a history record. ()
With Spider storage engine, setting a system variable overrides the value set as a table parameter. ()
The "pam_user_map" module does not correctly handle usernames or group names containing the "@" character. ()
With some Unicode collations, JSON functions can return incorrect results. (

With partitioning, possible slow down of queries. ()
With InnoDB storage engine, linear read-ahead (controlled by the innodb_read_ahead_threshold system variable) does not work as expected. This can impact performance of mariadb-dump and some queries that perform a full table scan. ()

Interface Changes

system variable maximum value changed from 9223372036854775807 to 1152921504606846975 ()
system variable minimum value changed from 4096 to 16376 ()
error code added (MENT-1796)
error code added (MENT-1796)

Spider Storage Engine

system variable default value changed from -1 to 0 ()
system variable default value changed from -1 to 2 ()
system variable default value changed from -1 to 0 ()
system variable default value changed from -1 to 100 ()

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.22-16 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 "".

Installation Instructions

Upgrade Instructions

[Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: OPTIMIZE TABLE SEQUENCE_NAME

[Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO TABLE_NAME VALUES (..) ON DUPLICATE KEY UPDATE KEY_NAME = KEY_VALUE

WHERE

A new privilege has been introduced with this version to fix a problem when upgrading to 10.5. A replica user couldn't run . Upgrades from 10.4 to 10.5 now adjust the privileges automatically. The new privilege needs to be added manually for a replica user when updating from an earlier 10.5 version. For more information on MariaDB Enterprise Server 10.5 privileges, see "Privileges Comparison ES10.4 and ES10.5.8-5".
- Users of MariaDB MaxScale's MariaDB Monitor upgrading from a prior version of MariaDB Enterprise Server 10.5 who have used the new 10.5 privileges must ensure the updated privilege has been granted to the MaxScale user and Replication user. For detailed privilege information, see Configuring MariaDB Monitor's User Account.
Galera wsrep library updated to 26.4.6 in .
The (not MariaDB Enterprise Audit) did not log proxy users. The new plugin version 2.0.3 introduces an event sub-type PROXY_CONNECT for event type CONNECT. ()
- On connect, if a proxy user is used, an extra line will be logged: TIME,HOSTNAME,user,localhost,ID,0,PROXY_CONNECT,test,plug_dest@%,0
Better MariaDB GTID support for the option. ()
New global variable ()
The new parameter --include-unsupported for the script mariadb_es_repo_setup can be used to enable a repository of unsupported packages in the repository configuration. The repository currently includes the CONNECT Storage Engine. The storage engine can be installed by yum install MariaDB-connect-engine or apt-get install mariadb-plugin-connect-engine (MENT-1003)
MariaDB Enterprise Audit did not log proxy users. The new plugin version 2.0.3 introduces an event sub-type PROXY_CONNECT for event type CONNECT. (MENT-977)
- On connect, if a proxy user is used, an extra line will be logged: TIME,HOSTNAME,user,localhost,ID,0,PROXY_CONNECT,test,plug_dest@%,0
- The event type can also be used in filters "connect_event": ["CONNECT","DISCONNECT","PROXY_CONNECT"]
Performance improvements for comparisons of temporal data types with temporal literals. ()
Performance improvements for comparisons of temporal data types. ()
For MariaDB Enterprise Server on MS Windows, NTFS file metadata on NTFS is not flushed anymore, reducing the write workload I/O. ()
Improved write performance for InnoDB. (, )
The now allows you to specify a port () to connect to and to force to use HTTP (). So it is now possible to connect to other solutions which provide the same open API used for Amazon S3. ()
Performance improvements for conversions from temporal data types to string. ()
Performance improvements for handling numeric data. ()
Default changed from 1 to 0 for command line option . Benchmarking showed that the old default causes a heavy mutex contention. ()

persistent stats analyze forces full scan which results in a lock crash. (MENT-1024)
hang on with error message Semaphore wait has lasted > 300 seconds. (MENT-1007)
Server crash can happen on filesort with a setting for to a value lower than the default of 64 (MDEV-24033)
Potential stack overflow in fulltext search with a complex MATCH .. AGAINST string. ()
can hang if the server goes idle after a particular kind of redo log write. ()
A server crash can occur when encryption is enabled for temporary tables () and queries use window functions. ()
A crash of MariaDB Server is possible when binary logging is activated, caused by improper raising of an error or replication checksum. ()
assertion on after [ALTER TABLE](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/data-definition/alter/alter-table) .. DISCARD TABLESPACE ()
Server crashes after failed attempt to create unique key on virtual column. ()
Possible server crash when using an index on a spatial data type with InnoDB. ()
Possible server crash when a string function is used for a column of type and the string function is used in a subquery which is returning a row. ()
node can crash on high , , or load from many connections executed on the same table with foreign keys. ()
Server crashes if a query is executed on an table with a foreign key where the foreign key was removed while using . This case should result in an SQL error. ()
Recursive procedure call ends with a crash instead of SQL error. ()
fails to open the table during removal of VIRTUAL column DDL while using , due to lack of referenced index. ()
Server crash when altering a table after its tablespace has been discarded already. ()
caused a variety of non-determinism failures if the given position did not exist. ()
SET GLOBAL replicate_do_db = DEFAULT causes a crash. ()
JSON_MERGE_PATCH(json_doc, json_doc [, json_doc] ...) can crash if the first parameter is set to NULL and the second is not valid JSON. ()
Server crashes after with ON DELETE SET NULL for foreign key and a virtual column in index. ()
Server can crash on a prepared statement executed via . ()
Crash on SELECT on a table that contains indexed virtual columns. ()
Possible server crash for queries using the window function NTH_VALUE() ()
Possible crash when using Tables and partitions. ()
MariaDB Enterprise Audit crashes. (MENT-1011)
node crash with Galera message Assertion server_state_.rollback_mode() == wsrep::server_state::rm_async' failed`. in the error log. (MENT-937)
node crashes or hangs during IST if the connection between donor and joiner is unstable or if cluster configuration changes take place at the same time. (MENT-514)
crash if bulk updates are executed on Galera. ()
Server crash when while replication is not enabled (wsrep-on=OFF). ()
Server crash if function is used with a decimal_position > 30. ()
Multiple calls to a Stored Procedure from another Stored Procedure crashes server. ()
Server crash when an invalid is set. ()
Server hang if TABLE LOCK is used after BACKUP LOCK was used. ()
Server crash on table updates using FOR PORTION OF ()
Assertion on executing with a prepared statement using when is on and wsrep_osu_method is TOI ()
Server crash if a transaction is started with SET SESSION wsrep_on=1, but the global is 0 ()
crash when used with sharding and XA, and (default). ()
node can crash with an error message WSREP: MDL BF-BF conflict in the error log. The error is related to running or on tables with foreign keys. ()
If resizing the redo log to be triggered immediately before a server shutdown is initiated, and if innodb_flush_sync=0 (non default setting), the shutdown may hang because the page cleaner thread fails to finish its job. (MENT-1031)
hangs with (MENT-992)
Crash recovery fails with Error InnoDB: Missing FILE_CHECKPOINT at ... between the checkpoint ... and the end ... after restart, if the redo log size has been changed with SET GLOBAL (MENT-795)
Replica crashes upon rename of a view. ()
The server can crash when an is executed on a HEAP table using WITHOUT OVERLAPS, and the is done for a value of a compound key which is included in the WITHOUT OVERLAPS definition. ()

can return incorrect event information from the binary log, prepended with set , ;
Defining a view with SQL syntax ISNULL(ID)=0 incorrectly returns a syntax error. (MENT-1015)
MariaDB Enterprise Backup reports an error that it cannot find an log file './aria_log.00000000' (MENT-907)
failure for incremental backups. ()
Aborting a query on an table with does not show an SQL error message, if the query could not be aborted. ()
Optimizer has chosen an inefficient plan, if a multi-component index, a second index, and a WHERE or ON clause with conditions over these indexes are used. ()
Some rounding has been done in an unexpected way for decimal numbers. ()
Server crashes after changing at runtime via a statement. ()
Creating a view removes parentheses on expressions from the , which results in wrong results. ()
mysql_tzinfo_to_sql under InnoDB is slow. ()
UDF cannot be uninstalled if the UDF library file doesn't exist. ()
with type DECIMAL can return an unexpected result, if the given value for "expr" includes many leading zeros. ()
replication broken if only one timezone is loaded. ()
SST donation fails, FLUSH TABLES WITH READ LOCK times out. ()
Memory leaks possible after with FOREIGN KEY ()
SST fails for if data-directory has lost+found directory. ()
caused a variety of non-determinism failures if the given position did not exist. ()
Linux AIO returned OS error 22 if parameters set to and (default). ()
CREATE OR REPLACE TRIGGER in not replicating, if a trigger with the same name already exists. ()
mysqld_multi no longer works with different server binaries. ()
Possible error for incremental backup for encrypted tablespaces. ()
Possible slow server start and stop if full text indexes are used. ()
The parentheses in a VIEW can be defined incorrectly for a combination of = and BETWEEN ()
ER_BASE64_DECODE_ERROR upon replaying binary log. ()
Several IPv6 issues with powered by Galera. (, , , , )
Subquery on information_schema fails with an error message. (MENT-1016)
AUTO_INCREMENT does not increment with compound primary key on partitioned table. (MENT-997)
CREATE TEMPORARY TABLE .. LIKE () returns error if unique index is defined in the table. ()
CREATE .. SELECT can result in empty result on join versioned table. ()
Error ERROR 4142 (HY000): SYSTEM_TIME partitions in table t1 does not support historical query upon querying a view, when that view is selecting from the versioned table with partitions. It only happens if the view itself was created using FOR SYSTEM_TIME ALL ()
Disk space not reused for Blob in data file. ()
will not dump sequence definition details on --no-data dump. ()
fails to validate corruption on a table that was corrupted by a bug related to instant ADD or DROP (fixed in MariaDB Enterprise Server 10.3.17, 10.4.7). ()
Subquery execution not terminated after LIMIT ROWS EXAMINED is exceeded. ()
Deadlock between BACKUP STAGE BLOCK_COMMIT and parallel replication. ()
Possible memory leak in galera library. ()
Wrong result of and with GROUP BY ()
Syntax error results in misleading message on about missing system table mysql.proc ()
where decimal position is 0 or 38 and num is DECIMAL(38,38) returns incorrect results. ()
A query result includes a data row twice depending on the WHERE clause used, if partitioning is used. ()
Assertion after ROLLBACK AND CHAIN ()
Replica user can't run after upgrade to 10.5. (MENT-995)
galera_new_cluster starts server as standalone instance with no warnings or errors when , although the expectation is to bootstrap a cluster. (MENT-979)
Wrong value #wsrep_provider_options="gcache.size=1024Mb" in server.cnf for wsrep_provider_options The server would not start after removing the comment. (MENT-970)
Wrongly reported SQL Error (1038): Out of sort memory for queries, where dependent subqueries use the ORDER BY clause. ()
An [ALTER TABLE](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/data-definition/alter/alter-table) .. RENAME to change a column to uppercase doesn't work. ()
IN-to-subquery conversion is not visible in optimizer trace. ()
is not replicated in with Galera Replication. ()

Release Notes for MariaDB Enterprise Server 10.5.10-7

MariaDB Enterprise Server 10.5.10-7 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2021-06-14

This seventh release of MariaDB Enterprise Server 10.5 is a maintenance release. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.10-7 was released on 2021-06-14.

Fixed Security Vulnerabilities

CVE (with link)

CVSS base score

Notable Changes

New function calculates the spherical distance between two geometries (point or multipoint) on a sphere. ()
updated to 26.4.8
Issue deprecation warnings for values none, innodb, strict_none, strict_innodb ()

Issues Fixed

Can result in data loss

fails to rename a column in table and causes server to crash. table is not accessible after restart. ()
Table corruption or after on table with foreign key. ()
[[]] deletes the current source file after a No space left on device error, before exiting. Only the incomplete target file is still available. ()

Can result in a hang or crash

Possible hang when or is used with and a multi-master setup. ()
Possible memory corruption with when inserting values bigger than 4096 bytes into variable-length fields (, , , and related types). ()
fails on compressed tables. ()

Can result in unexpected behavior

SUM column from a derived table returns invalid values. ()
returns an incorrect result. ()
Incorrect behavior of when it is executed as a prepared statement. ()
Query returns a

Missing libsepol dependency on SLES 12 and SLES 15. (MENT-1163)

Changes in Storage Engines

This release incorporates MariaDB ColumnStore storage engine version 5.6.1 (before 2021-06-30).
This release incorporates MariaDB ColumnStore storage engine version 5.6.2 (after 2021-06-30).

Interface Changes

information schema table schema adds LEVEL column
mariadb-backup --innodb-force-recovery command-line option added
mariadb_repo_setup --skip-check-installed command-line option added
function added

Platforms

In alignment with the , MariaDB Enterprise Server 10.5.10-7 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 "".

Installation Instructions

Upgrade Instructions

"table": {
 "table_name": "t1",
 ...
 "r_engine_stats": {
 "pages_accessed": integer,
 "pages_updated" : integer,
 "pages_read_count" : integer,
 "pages_read_time_ms" : double_val,
 "old_rows_read" : integer,
 },

Server crashes in check_grant upon invoking function with userstat enabled. (MDEV-25242)

MariaDB Enterprise Server 10.5

Release Notes for MariaDB Enterprise Server 10.5.29-23

Fixed Security Vulnerabilities

Changes in Storage Engines

Notable changes

Issues Fixed

Can result in data loss

Can result in hang or crash

Can result in unexpected behaviour

Unexpected results

Changelog

Platforms

Release Notes for MariaDB Enterprise Server 10.5.28-22

Fixed Security Vulnerabilities

Changes in Storage Engines

Notable changes

Issues Fixed

Can result in data loss

Can result in hang or crash

Can result in unexpected behaviour

Related to performance

Changelog

Platforms

Installation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.27-21

Notable Changes

Release Notes for MariaDB Enterprise Server 10.5.26-20

Backports

Notable Changes

Changes in Storage Engines

Issues Fixed

Can result in data loss

Installation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.25-19

Fixed Security Vulnerabilities

Release Notes for MariaDB Enterprise Server 10.5.19-14

Release Notes for MariaDB Enterprise Server 10.5.6-4

Fixed Security Vulnerabilities

Release Notes for MariaDB Enterprise Server 10.5.4-1

Release Notes for MariaDB Enterprise Server 10.5.3-1

MariaDB Enterprise Server 10.5

Release Notes for MariaDB Enterprise Server 10.5.29-23

Fixed Security Vulnerabilities

Changes in Storage Engines

Notable changes

Issues Fixed

Can result in data loss

Can result in hang or crash

Can result in unexpected behaviour

Unexpected results

Changelog

Platforms

Release Notes for MariaDB Enterprise Server 10.5.27-21

Notable Changes

Changes in Storage Engines

Issues Fixed

Can result in data loss

Can result in hang or crash

Can result in unexpected behavior

Related to performance

Changelog

Platforms

nstallation Instructions

Upgrade Instructions

Release Notes for MariaDB Enterprise Server 10.5.19-14

Release Notes for MariaDB Enterprise Server 10.5.4-1

Release Notes for MariaDB Enterprise Server 10.5.25-19

Fixed Security Vulnerabilities

Release Notes for MariaDB Enterprise Server 10.5.3-1

Notable Changes

Changes in Storage Engines

Issues Fixed

Can result in data loss

Can result in hang or crash

Can result in unexpected behavior

Related to performance

Changelog

Platforms