The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2025-03-12. For the latest, interactive version please visit https://mariadb.com/kb/.

Release Notes for MariaDB Enterprise Server 10.6.14-9

MariaDB Enterprise Server 10.6.14-9 is a maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes. Users of MariaDB Enterprise Server 10.6.12-8 are encouraged to upgrade.

The next scheduled maintenance release for MariaDB Enterprise Server is 2023-09-11.

MariaDB Enterprise Server 10.6.14-9 was released on 2023-06-13.

Changes in Storage Engines

  • This release originally incorporated MariaDB ColumnStore engine version 23.02.3, and later contained 23.02.8 and 23.02.9.
  • This release now incorporates MariaDB ColumnStore engine version 23.02.10.

Notable Changes

  • InnoDB's internal performance has been improved. (MDEV-30567)
  • By default, mariadb-backup no longer prints messages about log scanning. (MDEV-25765)
    • In previous releases, messages like the following could be printed excessively:
       >> log scanned up to (LSN)
      Starting with this release, the messages about log scanning are only printed when --verbose is enabled.
  • Performance schema instruments are now available to monitor mutex contention in InnoDB's internal thread pool that is used for asynchronous data page I/O. (MDEV-31048)
    • Starting with this release, the wait/synch/mutex/innodb/tpool_cache_mutex instrument can be enabled to track contention on the internal tpool::cache::m_mtx mutex in read_slots and write_slots.
    • When performance_schema is enabled, you can enable the wait/synch/mutex/innodb/tpool_cache_mutex instrument by changing the ENABLED column for the instrument in the performance_schema.setup_instruments table: 
      UPDATE performance_schema.setup_instruments
   SET ENABLED='YES'
   WHERE NAME='wait/synch/mutex/innodb/tpool_cache_mutex';
    • When the instrument is enabled, details about mutex waits can be retrieved from other performance schema tables, such as performance-schema.events_waits_current, performance-schema.events_waits_history, and performance-schema.events_waits_history_long.
    • Enabling performance schema instrumentation can result in performance overhead, so extra care should be taken when enabling performance schema on production systems.
  • InnoDB page flushing speed has been improved. (MDEV-26827)
  • When InnoDB's purge thread encounters a cached undo page that has not yet been re-used, the page is freed. This approach avoids some page writes and improves backup and restore performance. It also prevents the system tablespace or temporary tablespace from growing unnecessarily when they store undo log pages. (MDEV-29593)

Issues Fixed

Can result in data loss

  • When system versioning is enabled for a table without a primary key, changes to the table are not properly replicated. (MDEV-30430)
  • 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. (MDEV-30072)
  • For some collations, when a unique constraint is defined with UNIQUE(..) USING HASH, duplicate values are accepted. (MDEV-30034)
  • When an InnoDB table with ROW_FORMAT=REDUNDANT is being rebuilt due to a DDL statement, the server can crash while trying to apply cached DML operations to the rebuilt table. (MDEV-26198)
  • Long uniques don't work correctly with Unicode collations. Equal strings (in terms of the collation) are compared as unequal if the length of the strings are different. (MDEV-27653, MDEV-28190)
  • When innodb_buffer_pool_filename is set to the empty string, the server tries to delete the datadir during shutdown. (MDEV-30453)
    • Starting with this release, the innodb_buffer_pool_filename system variable is read-only and can't be changed dynamically.
    • However, starting with MariaDB Community Server 10.9, the server rejects using numeric IDs to represent non-default character sets in binary logs. Replica servers using these newer versions would raise the following error message:
      Unknown character set: '224'
    • Starting with this release, the server writes the character_set_client value to the binary log as a string instead of as a numeric ID. This change allows MariaDB Community Server 10.9 and later to connect as replica servers.
  • With Galera, when a value is retrieved from an InnoDB sequence using the NEXTVAL() function, the server can crash due to metadata lock conflicts between WSREP threads. (MDEV-30413)
    • In previous releases, the following log message would be reported in the log prior to the crash: 
      [Note] WSREP: MDL BF-BF conflict
[ERROR] Aborting

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. (MDEV-30882)
  • With Galera, when wsrep_sst_method=mariabackup 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. (MDEV-30402)
    • In previous releases, SSTs could fail with the following error in the donor node's MariaDB error log if the version of socat installed is 1.7.4.0 or later: 
      E Failed to set SNI host ""
    • 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. (MDEV-31085)
  • 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. (MDEV-31102)
  • When a replica server connects to a primary server with MASTER_USE_GTID=slave_pos, if the primary server has encrypted binary logs that it can no longer decrypt, the primary server crashes due to a segmentation fault. (MDEV-28798)
    • In previous releases, the primary node would iterate over all of its binary logs to look for the requested GTID. When one of the binary logs could not be decrypted, the server would crash.
    • Starting with this release, when the primary node fails to decrypt a binary log in this scenario, it stops iterating over the binary logs and raises an error with the ER_MASTER_FATAL_ERROR_READING_BINLOG error code with the following error message:
      Got fatal error 1236 from master when reading data from binary log: 'Could not set up decryption for binlog.'
  • When EXPLAIN EXTENDED is executed for a single-table DELETE that contains an IN(..) predicand, the server can crash. (MDEV-31181)
  • When parallel replication is enabled by setting slave_parallel_threads greater than 0, the replica's parallel replication worker threads could hang after hitting an error. (MDEV-30780)

○ In previous releases, when the server was hung in this scenario, the output of SHOW SLAVE STATUS would show that an error occurred, but the output would indicate that both the I/O and SQL threads were running. 

SHOW SLAVE STATUS\G


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

○ 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:

SHOW PROCESSLIST;

+------+--------------+--------------------+------+--------------+-------+-----------------------------------------------+------------------+----------+
| Id   | User         | Host               | db   | Command      | Time  | State                                         | Info             | Progress |
+------+--------------+--------------------+------+--------------+-------+-----------------------------------------------+------------------+----------+
..
| 2394 | system user  |                    | NULL | Slave_worker | 50852 | closing tables                                | NULL             |    0.000 |
..
+------+--------------+--------------------+------+--------------+-------+-----------------------------------------------+------------------+----------+
  • When the optimizer chooses how to split a semi-join, the server can crash. (MDEV-31403)
  • With Galera, when CREATE TEMPORARY SEQUENCE is executed on a cluster node and binary logging is enabled, the server crashes. (MDEV-25045)
  • 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. (MDEV-27317)
    • In previous releases, when a write set failed certification and binary logging was enabled, a WSREP applier thread could sync the WSREP sequence number out-of-order, because the commit order could be released too early.
  • With Galera, when streaming replicating is enabled by setting the wsrep_trx_fragment_size system variable and CREATE TABLE .. SELECT is executed, the server can crash. The following assertion is written to the MariaDB error log during the crash: (MDEV-30862) 
    Assertion `mode_ == m_high_priority' failed in void wsrep::client_state::after_applying()
    • Starting with this release, the server prohibits CREATE TABLE .. SELECT in this scenario and raises the ER_NOT_ALLOWED_COMMAND error code with the following error message: 
      ERROR 42000: CREATE TABLE AS SELECT is not supported with streaming replication
  • With Galera, when a connection uses the handler interface to start a transaction on a table, the server can crash when the client disconnects. (MDEV-30955) 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: 
      void close_thread_table(THD*, TABLE**): Assertion `thd->mdl_context.is_lock_owner(MDL_key::TABLE, table->s->db.str, table->s->table_name.str, MDL_SHARED)' failed.
  • 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: 
      [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.
  • When a query is executed that uses DISTINCT and an aggregate function on a group, the server can crash. (MDEV-31113)
  • 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. (MDEV-31189)
  • When the InnoDB purge thread tries to use the change buffer for an uncommitted index, the server aborts with an assertion. (MDEV-30076)
  • When the rowid_filtering optimization is used with a partitioned table, the server aborts with an assertion. (MDEV-30596)
  • With Galera, a hang can occur in "starting" commit state due a deadlock between a KILL command and an abort issued by an applier. (MENT-1855)
    • Starting with this release, Total Order Isolation (TOI) is not used for the KILL command.
  • When a backup is prepared with mariadb-backup, the utility can hang due to a race condition between the thread flushing the buffer pool and the thread deleting the redo log file. (MDEV-30860)
  • With Galera, when a transaction changes multiple tables that use different storage engines, some of which support the server's internal 2-phase commit protocol and some of which don't support it, the node crashes with an assertion failure. (MDEV-30804)
    • In previous releases, the following assertion failure is written to the MariaDB error log during the crash in this scenario:
      int wsrep::transaction::ordered_commit(): Assertion `state() == s_committing' failed.
    • Starting with this release, when Galera is enabled, mixed transactions are rejected in with the following error message: 
      ERROR HY000: Transactional commit not supported by involved engine(s)
  • 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. (MDEV-30551)
  • When processing a query with the ROWNUM() function, if the query uses in its FROM list a reference to a mergeable view, defined as SELECT, for more than one table that contains an ORDER BY clause, the server can crash. (MDEV-31162)
  • When an InnoDB table uses ROW_FORMAT=COMPRESSED, the server can hang when splitting a page. (MDEV-31158)
  • When processing a query executing the ROWNUM() function on a mergeable view with ORDER BY, under certain conditions checked in the preparation phase, it may be decided to materialize the view rather than merging it. In this case, the derived field of the TABLE_LIST structure created for the view remained equal to 0. As a result, the guard condition preventing range parsing for materialized views did not work as expected, causing the server to crash. (MDEV-31143)
  • When DDL is performed on an InnoDB table, the server can hang due to a deadlock between the DDL operation and the purge of InnoDB history. (MDEV-31132)
  • When InnoDB tablespace encryption is enabled and DROP TABLE is executed, the server can crash due to a race condition between the background drop thread and the background encryption threads. (MDEV-29273)
  • With Galera, when XA transactions are used, the cluster node can crash. (MENT-1733, MENT-1737)
  • When creating a backup with mariadb-backup, the server can crash if the InnoDB system tablespace (default ibdata1) is very large. (MENT-1703)
  • ith Galera, when OPTIMIZE TABLE is executed on a node, the server can crash due to metadata lock conflicts between WSREP threads. (MDEV-30303)
    • In previous releases, the following log message would be reported in the log prior to the crash:
      [Note] WSREP: MDL BF-BF conflict
[ERROR] Aborting

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. (MDEV-31224)
  • When a query specifies DISTINCT and contains expressions using the SUM() function, the wrong results are returned. (MDEV-20057)
  • When a view's definition contains a HAVING clause, selecting from the view can fail with an error. (MDEV-28570)
    • In previous releases, queries could raise an error with the ER_VIEW_INVALID error code and the following error message:
      View 'test.v1' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
  • When a view's definition contains an aggregate function, selecting from the view can fail with an error. (MDEV-28571)
  • 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. (MDEV-28603)
    • In previous releases, queries could raise an error with the ER_VIEW_INVALID error code and the following error message:
      View 'test.v1' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
  • When a view's definition contains an aggregate function in an uncorrelated subquery, the wrong result is returned. (MDEV-29224)
  • 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. (MDEV-30586)
  • When an InnoDB tablespace has been discarded, selecting from information_schema.INNODB_SYS_INDEXES fails with an error. (MDEV-30615)
    • In previous releases, an error with the ER_UNKNOWN_ERROR error code is raised:
      ERROR 1105 (HY000): Unknown error
    • Starting with this release, no error is returned, and the results contain NULL for the PAGE_NO and SPACE columns for discarded tablespaces.
  • When innodb_undo_directory is set to a relative path, the path is not properly used by mariadb-backup --copy-back. (MDEV-28187)
    • In previous releases, the undo logs would be copied to the relative path compared to the current working directory.
    • Starting with this release, the undo logs are copied to the relative path compared to the datadir.
  • When UNIX_TIMESTAMP(CURRENT_TIME()) is executed, the incorrect value is returned. (MDEV-26765)
    • In previous releases, NULL is returned.
  • With Galera, when wsrep_sst_method='mariabackup' is set, systemd raises an error about a mismatched PID. (MDEV-25887)
    • In previous releases, systemd could raise the following error, where BACKUP_PID is the PID of MariaDB Enterprise Backup and SERVER_PID is the PID of MariaDB Enterprise Server: 
      Got notification message from PID BACKUP_PID, but reception only permitted for main PID SERVER_PID
  • When an UPDATE contains a WHERE clause that contains a range condition over a non-indexed VARCHAR column, an error is raised. (MDEV-20773)
  • In previous releases, an error with the ER_DATA_TOO_LONG error code is raised with the following error message:
    ERROR 1406 (22001): Data too long for column 'COLUMN_NAME' at row 1
  • When slave_parallel_threads is greater than 0 and SHOW SLAVE STATUS is executed, the connection can try to acquire an uninitialized mutex. (MDEV-30620)
    • 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 collation, which is intended for compatibility with older versions of MySQL, incorrectly sorts 'ß' after 's'. (MDEV-30746)
  • When EXPLAIN EXTENDED is executed with an INSERT, UPDATE, DELETE, or REPLACE, a warning containing the query text is not printed. (MDEV-30539)
  • The rowid_filtering optimization is applied incorrectly in some cases. (MDEV-30218)
  • When preparing a partial backup, MariaDB Enterprise Backup raises error messages about missing InnoDB tablespace files that are expected to be missing, because they were excluded from the backup. (MDEV-29050)
  • Parallel replication breaks if XA PREPARE fails updating replica GTID State (MDEV-31038)
  • When InnoDB has opened more data files than innodb_open_files, opening additional data files takes longer than expected due to a performance regression. (MDEV-30775)
  • With optimizer_switch='not_null_range_scan=on', when a LEFT JOIN is executed on an empty table, the results can be incorrect. (MDEV-30333)
  • When a query contains a GROUP BY clause and the query calls an aggregate function on a table's primary key, the results can be incorrect if the GROUP BY clause is evaluated using an index. (MDEV-30605)
  • With Galera, when a cluster node has the query cache enabled and the node has regular MariaDB replication configured, query cache entries are not properly invalidated when tables are changed due to replication. (MDEV-28641)
  • When a backup is created with mariadb-backup, the utility opens the aria_log_control file in read/write mode instead of in read-only mode. (MENT-1794)
  • When INSERT .. SELECT is executed with a full-text index present, all other commits during the commit hang. (MDEV-30996)
  • Incorrect memory management during a commit operation on tables that contain a full-text index. (MDEV-30341)
  • When SELECT DISTINCT .. WITH TIES is executed using index, it produces incorrect results. (MDEV-30324)
  • When a bulk insert into an InnoDB table is performed, the transaction savepoint is not released. (MDEV-29975)
  • When an UPDATE is executed on an InnoDB table, transactions can hang due to a race condition. (MDEV-27701)
  • With parallel replication, performance schema can contain inconsistent details about worker threads when the worker threads are starting up. (MDEV-26071)
  • When using the InnoDB storage engine, the execution of queries that use secondary indexes may slow down significantly. (MDEV-30357)
    • Prior to this release (starting with 10.6.8), the performance of queries using secondary indexes could be affected by code that implements locking reads from secondary indexes.
    • Starting with this release, the condition that was causing the performance degradation has been removed, so locking transactions that did not modify any persistent tables can have a transaction ID of 0
  • After writing to InnoDB temporary tables, space in the InnoDB temporary tablespace is not reclaimed. (MDEV-26782)
  • When creating a backup with mariadb-backup, the utility can fail to copy the Aria log file when there is a gap in logs. (MENT-1587)
    • In previous releases, the backup log could contain messages like the following:
Found aria log file: aria_log.00000001, current: 1, min: 1, max: 1
Found aria log file: aria_log.00000004, current: 4, min: 1, max: 4
Found 4 aria log files, minimum log number 1, maximum log number 4, last log number 4
Stop scanning aria tables.
..
error: cannot open file ./aria_log.00000002
Error: copy_file() failed.
Error on copying ./aria_log.00000002 aria log file.
Skip copying 3 aria log file due to error
Skip copying 4 aria log file due to error

Interface Changes

  • core_file system variable default value changed from None to OFF
  • mariadb-backup --aria-log-dir-path command-line option added.

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.14-9 is provided for:

  • CentOS 7 (x86_64)
  • Debian 10 (x86_64, ARM64)
  • Debian 11 (x86_64, ARM64)
  • Red Hat Enterprise Linux 7 (x86_64)
  • Red Hat Enterprise Linux 8 (x86_64, ARM64)
  • Red Hat Enterprise Linux 9 (x86_64, ARM64)
  • Rocky Linux 8 (x86_64, ARM64)
  • Rocky Linux 9 (x86_64, ARM64)
  • SUSE Linux Enterprise Server 12 (x86_64)
  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)
  • Ubuntu 20.04 (x86_64, ARM64)
  • Ubuntu 22.04 (x86_64, ARM64)

Windows packages are not currently available for this release.

Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see MariaDB Corporation Engineering Policies".

Installation Instructions

Upgrade Instructions

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.