MariaDB Enterprise Server 11.6.18-14 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6, released on 2024-06-11
MariaDB Enterprise Server 10.6.18-14 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6.
MariaDB Enterprise Server 10.6.18-14 was released on 2024-06-11.
CVE (with link)
CVSS base score
Galera has been updated to 26.4.18
The GCS protocol version has been changed, preventing a downgrade of individual nodes of a MariaDB Enterprise Cluster
Changes to the use of the variable optimizer_adjust_secondary_index_costs ()
This release originally incorporated MariaDB ColumnStore engine version 23.10.1.
This release now incorporates MariaDB ColumnStore engine version 23.10.2.
With --gtid-ignore-duplicate set a transaction can be double-applied from another replication source if at applying the transaction from the initial source required retrying in parallel execution. ()
Backups of server with innodb_encrypt_tables=1 can become corrupted in mariadb-backup --prepare ()
With multiple GTID domains, optimistic parallel slave conflicts involving XA-PREPARE event group could not be resolved correctly which might cause unnecessary stop of the slave serve. ()
Using current MariaDB Enterprise Backup against an older server can result in a crash, as the system variable @@aria_log_dir_path does not exist ()
When using a non-default setting for innodb_change_buffering, the server can crash ()
When a fulltext search query with more than 4G inserted or updated rows is executed, the server can crash ()
When replaying a binary log with mariadb-binlog, the tool can crash if the binary log includes statements related to sequences, like SELECT NEXTVAL(s) ()
MariaDB Enterprise Backup fails with the following error message if the prepare step of the backup encounters a data directory which happens to store wsrep xid position in TRX SYS page: ()
Assertion failure when a client disconnected during transaction that is in the XA PREPARE state or when incomplete transaction was recovered from undo logs on server startup and not yet rolled back ()
Failure with the following error message when streaming transaction in idle state is BF aborted: ()
Assertion when user commits an empty transaction for DDL that was killed during certification: ()
MDL lock conflict can occur if the transactions acquire explicit MDL locks from the InnoDB level when persistent statistics is re-read for a table and such a transaction is subject to BF-abort ()
Graceful node shutdown can crash garbd and MariaDB Enterprise Cluster can go non-primary when SSL is used ()
Wrong result sets are returned by the second execution of prepared statements from selects using mergeable derived tables pushed into external engine ()
IMPORT TABLESPACE fails with column count or index count mismatch: ()
A query that uses a derived table that employs constructs with side-effects, like (SELECT @var:=... ) as derived_tbl, could produce wrong results ()
ORDER BY COLLATE improperly applied to non-character columns which is resulting in an unordered result set ()
Inconsistent behaviors of UPDATE under Read Uncommitted & Read Committed isolation level ()
CREATE TEMPORARY TABLE (without SELECT), INSERT ... SELECT, and CREATE ... LIKE are not affected by this bug
Phantom rows caused by UPDATE of PRIMARY KEY ()
Mariadb-dump trusts the server and does not validate the data. A modified dump file can include system commands used by the mariadb-client. Dumps are now loaded in the sandbox mode by default, a system call will result in an error ()
A wrong result on 2-nd execution of a prepared statement is possible when selecting from a view using a merged derived table ()
Original IP not shown in network related error messages when proxy_protocol is in use ()
Incorrect DEFAULT expression evaluated in UPDATE ()
group by optimization incorrectly removing subquery where subject buried in a function (
Replication with XA events can show decreased performance. Adapt parallel slave's round-robin scheduling to XA events ()
Row locks for non-modified rows are not released at XA PREPARE ()
Optimizer is sometimes choosing an index for queries with GROUP BY when it shouldn't, resulting in decreased performance. To protect compatibility to the current behavior @@optimizer_adjust_secondary_key_costs="disable_forced_index_in_group_by" has to be set to enable the fix ()
then the arguments are guaranteed not to have duplicates. Such cases are now detected allowing the optimizer to skip de-duplication.
For the complete list of changes in this release, see the .
In alignment to the , MariaDB Enterprise Server 10.6.18-14 is provided for:
AlmaLinux 8 (x86_64, ARM64)
AlmaLinux 9 (x86_64, ARM64)
CentOS 7 (x86_64)
Debian 10 (x86_64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see
The default of the variable optimizer_adjust_secondary_index_costs changed from "0" to "" and is now of type ENUM
The variable can now be set to a combination of the following values separated by a ',':
adjust_secondary_key_cost: Update secondary key costs for ranges to be at least 5x of clustered primary key costs.
disable_max_seek: Disable 'max_seek optimization' for secondary keys and slight adjustment of filter cost.
disable_forced_index_in_group_by: Disable automatic forced index in GROUP BY and make GROUP BY cost based instead of rule based. ALL Sets all of the above values.
Without changes in configuration or using the old integer values 0, 1, 2 for optimizer_adjust_secondary_key_costs this system variable works as before. This is to ensure that we do not break any existing applications.
The TIMESTAMP value of '1970-01-01 00:00:00' can be inserted via a INSERT ...FROM ... SELECT in strict mode although it should result in an error (MDEV-34088)
Galera-replicated events can in some cases contain the wrong time when versioning is used (MDEV-18590)
wrong row targeted with insert ... on duplicate and replace, leading to data corruption (MDEV-30046)
InnoDB is holding shared dict_sys.latch while waiting for FOREIGN KEY child table lock on DDL (MDEV-32899)
InnoDB may hang when temporarily running out of buffer pool (MDEV-33613)
For encrypted table spaces an ALTER operation can hang when an encryption thread works on the same tablespace (MDEV-33770)
EXPLAIN statement that uses a subquery which has a query plan that A) will examine less than @@expensive_subquery_limit rows and B) will use join buffer could cause a crash. (MDEV-21102)
For a SPIDER table, when deleting partitions from a table, the server can crash (MDEV-33731)
After an unsuccessful ALTER TABLE on an ARIA table due to a full temp space, any subsequent query results in the following error if it involves using temp: (MDEV-33813)
When two transactions modify the data at the same time with isolation level REPEATABLE-READ, the latter transaction does take the change from the first transaction into account (MDEV-26642)
Spider/ODBC passed double quotes for names, in ANSI style (MENT-958)
Default charset doesn't work with PHP MySQLi extension (MDEV-32975)
Bad SEPARATOR value in GROUP_CONCAT on character set conversion can lead to a wrong result (MDEV-33772)
Spider returns parsing failure on valid left join select by translating the on expression to () (MDEV-33679)
When creating a temporary InnoDB table with CREATE TEMPORARY TABLE ... AS SELECT ... from an InnoDB table as a non SUPER / READ ONLY ADMIN user, the following error is shown instead of creating the table: (MDEV-33889)
Updating a case insensitive large unique key with an insensitive change of the value can result in a duplicate key error (MDEV-29345)
When setting binlog_annotate_row_events=1, an event of binlog file can be truncated (MDEV-9179)
Wrong result with semi-join and split-table derived table from queries with an IN subquery predicate in the WHERE clause and a derived table in the FROM clause to which split materialized optimization could be applied. (MDEV-23878)
With galera, correct transactions could not be committed with the following error when accessing system tables for read, and write to innodb tables in the same transaction: (MDEV-33828)
Table is getting rebuild with ALTER TABLE ADD COLUMN although it should be an instant operation not requiring a rebuild (MDEV-33214)
Semi-sync Wait Point AFTER_COMMIT Slow on Workloads with Heavy Concurrency (MDEV-33551)
Aggregation functions fail to leverage uniqueness property (MDEV-30660)
Generally, computing aggregate function with DISTINCT argument: aggregate_func(DISTINCT col1, col2, ...) requires producing a de-duplicated set of its arguments, which can be CPU-intensive
When we select from one table the argument list includes the table's PRIMARY (or UNIQUE) key:
Debian 12 (x86_64, ARM64)
Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)
Red Hat Enterprise Linux 7 (x86_64)
Red Hat Enterprise Linux 8 (x86_64, ARM64)
Red Hat Enterprise Linux 9 (x86_64, ARM64, PPC64LE)
Rocky Linux 8 (x86_64, ARM64)
Rocky Linux 9 (x86_64, ARM64)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
Ubuntu 22.04 (x86_64, ARM64)
4.9
ERROR 1021 (HY000): Disk full (./org/test1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")InnoDB: Crash recovery is broken due to insufficient innodb_log_file_sizeWSREP: Failed to apply write set with flags = (rollback | pa_unsafe)!wsrep_has_changes(thd) || (thd->lex->sql_command == SQLCOM_CREATE_TABLE && !thd->is_current_stmt_binlog_format_row()) || thd->wsrep_cs().transaction().state() == wsrep::transaction::s_abortedERROR 1808 (HY000): Schema mismatch (Number of columns don't match, table has x columns but the tablespace meta-data file has y columns)ERROR 1290 (HY000): The MariaDB server is running with the --read-only option so it cannot execute this statementTransactional commit not supported by involved engineSELECT aggregate_func(DISTINCT t1.primary_key, ...) FROM t1;This page is: Copyright © 2025 MariaDB. All rights reserved.