14-day MaxScale Trial: Explore the latest version of our advanced database proxy!
Start Trial
Download MariaDBContact Us

Release Notes for MariaDB Enterprise Server 10.6.8-4

MariaDB Enterprise Server 10.6.8-4 is a maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes.

MariaDB Enterprise Server 10.6.8-4 was released on 2022-06-13.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE (with cve.org link)

CVSS base score

CVE-2022-27458

7.5

CVE-2022-27457

7.5

CVE-2022-27456

7.5

CVE-2022-27455

7.5

CVE-2022-27452

7.5

CVE-2022-27451

7.5

CVE-2022-27449

7.5

CVE-2022-27448

7.5

CVE-2022-27447

7.5

CVE-2022-27446

7.5

CVE-2022-27445

7.5

CVE-2022-27444

7.5

CVE-2022-27387

7.5

CVE-2022-27386

7.5

CVE-2022-27384

7.5

CVE-2022-27383

7.5

CVE-2022-27382

7.5

CVE-2022-27381

7.5

CVE-2022-27380

7.5

CVE-2022-27379

7.5

CVE-2022-27378

7.5

CVE-2022-27377

7.5

CVE-2022-27376

7.5

CVE-2022-21451

7.5

CVE-2022-32088

6.5

CVE-2022-32087

6.5

CVE-2022-32086

6.5

CVE-2022-32085

6.5

CVE-2022-32083

6.5

CVE-2021-46669

6.5

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:

Notable Changes

  • Galera updated to 26.4.12

  • Spider storage engine refuses attempts to create a temporary table since the engine cannot itself store data and cannot create temporary tables on a remote server. (MDEV-28225)

  • Status variables Innodb_encryption_key_rotation_list_length, Innodb_num_index_pages_written and Innodb_num_non_index_pages_written were unused and have been removed. (MDEV-28541, MDEV-28537)

  • Starting with this release, when wsrep_sst_method is set to rsync or mariadb-backup, the sst_max_binlogs SST option can be specified in the [sst] option group in configuration files. This parameter specifies the number of binary log files to be sent to the joiner node during SST. (MDEV-27524)

    • The default value is 0:

      • If a binlog exists, it will be transferred.

      • If a binlog does not exist, no binlog will be transferred.

  • Server error messages are available in Chinese. (MDEV-28227)

  • Xpand storage engine support is discontinued for MariaDB Enterprise Server 10.6. (MENT-1499)

  • Ubuntu 22.04 LTS support added. (MENT-1441)

Issues Fixed

Can result in data loss

  • When the parser converts a string from the binary character set to a multi-byte character set (such as utf32), an invalid string could be produced. (MDEV-23210)

  • When rows are inserted into an intermediate temporary table via the LOAD DATA INFILE statement ,and then the rows are copied from the temporary table to a persistent table, the rows are not written to binary log if binlog_format=MIXED is set, which prevents the operation from properly replicating to replica servers. (MDEV-24667)

  • When innodb_disallow_writes=ON is set, mariadb-admin shutdown can hang. (MDEV-25975)

  • When a replica server's I/O thread receives an incomplete event group from the primary server, the replica server continues writing events to the relay log and does not raise an error. (MDEV-27697)

  • If a primary is shutdown during an active semi-sync connection during the period when the primary is awaiting an ACK, the primary hard kills the active communication thread and does not ensure the transaction was received by a replica. This can lead to an inconsistent replication state. (MDEV-11853)

  • InnoDB page corruption on btrfs filesystem with innodb_use_native_aio=1 (MDEV-27900)

  • Semisync-replica server recovery fails to rollback a prepared transaction. (MDEV-28461)

Can result in a hang or crash

  • 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 SELECT statement 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 innochecksum 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. (MDEV-27835)

  • When an invalid CREATE SEQUENCE .. RESTART statement is used inside of a CREATE PROCEDURE or CREATE FUNCTION statement, the server can crash while parsing the statement. (MDEV-28220)

  • When a table contains a virtual generated column that is defined using the IF() and DATE_FORMAT() functions, inserting a row into the table can cause the server to crash with a segmentation fault. (MDEV-24176)

  • 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. (MDEV-21028)

  • When a UNION of decimal types is performed in an ORDER BY clause, the server can crash with a segmentation fault. (MDEV-25994)

  • 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. (MDEV-27212)

    • Querying views can result in mergeable derived tables.

    • Using subqueries with outer references can result mergeable derived tables.

  • When ANALYZE FORMAT=JSON is executed with a query that contains a subquery, the server can crash. (MDEV-28268)

  • When a query using a window function with an OVER (PARTITION BY ..) or OVER (ORDER BY ..) clause is executed, the server can crash with a segmentation fault. (MDEV-19398)

    • If the query also uses WITH ROLLUP, this crash is more likely.

    • If the query's OVER (PARTITION BY ..) or OVER (ORDER BY ..) clause uses an aggregate function, this crash is more likely.

  • 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. (MDEV-28437)

  • 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. (MDEV-28583)

    • This issue is confirmed to happen with wsrep_sst_method set to rsync, but it might also occur with other SST/IST methods.

  • Online DDL fails while checking for instant alter condition (MDEV-28060)

  • With MariaDB Enterprise Cluster (Galera), parallel async replication hangs on a Galera node when slave-parallel-threads is greater than 1 (MDEV-27568)

  • With MariaDB Enterprise Cluster (Galera), possible crash after a conflict of the applier thread with a stored procedure call triggered by the event scheduler. (MDEV-27713)

  • Server crashes when executing a shutdown statement after starting an XA transaction. (MDEV-26575)

  • Possible server crash during mariadbd initialization, if the number of GTIDs added since that last purge of the mysql.gtid_slave_pos tables is greater than or equal to the --gtid-cleanup-batch-size value. (MDEV-26473)

  • 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. (MDEV-28578)

  • Running a grouping query over non-blob columns that take more than 65535 bytes (for example, VARCHAR(16383) CHARACTER SET UTF32) could cause a crash. (MDEV-24560)

  • Possible crash after or during DROP TABLE when the InnoDB buffer pool size has been changed. (MDEV-27891)

  • InnoDB crash on multiple concurrent SHOW TABLE STATUS (MDEV-26551)

  • Shutdown hangs after altering an InnoDB partition when innodb_fast_shutdown=0 (MDEV-28079)

Can result in unexpected behavior

[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
You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column

  • When an UPDATE statement uses a subquery inside an IN() clause, the optimizer could incorrectly choose to perform a full table scan (with type: ALL) when a range scan (with type: range) would be more efficient. (MDEV-22377)

  • When a table contains multiple ENUM columns with identical values, the values could become corrupt if multi-byte character sets are used. (MDEV-28078)

  • When DECIMAL columns are read from information_schema.PROCESSLIST, the server could incorrectly raise an ER_BAD_DATA warning. (MDEV-28131) The warning can appear on the client as the following after executing SHOW WARNINGS:

Encountered illegal value '' when converting to DECIMAL
View being updated does not have complete key of underlying table in it

  • When using mariadb-binlog with --raw and --stop-never, events from the primary server's currently active log file are not written to their respective log file specified by --result-file. (MDEV-14608)

  • When a prepared statement is used to execute EXPLAIN, a different query plan can be returned on the second execution. (MDEV-19631)

  • When slave_compressed_protocol is enabled with semi-synchronous replication, the numbering on packet headers can become out of sync between the primary and replica servers, but the inconsistency does not have any negative impact with release builds of MariaDB Enterprise Server. (MDEV-25580)

  • The server and MariaDB Enterprise Backup can raise unnecessary warnings about tablespace IDs in some scenarios. (MDEV-27343)

    • The warning can appear as the following:

InnoDB: Allocated tablespace ID TABLESPACE_ID for DATABASE_NAME/TABLE_NAME, old maximum was 0
[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

  • When INSERT .. ON DUPLICATE KEY UPDATE is executed and binlog_row_image is set to FULL, the server does not write unchanged columns to the binary log. (MDEV-21810)

  • PAM v2 plugin (auth_pam) produces zombie processes. (MENT-1443)

  • With MariaDB Enterprise Cluster (Galera), wsrep_incoming_addresses does not include address details. (MENT-1527)

  • With HashiCorp key management (hashicorp_key_management), dynamic changes to hashicorp_key_management_cache_timeout and hashicorp_key_management_cache_version_timeout system variables are ignored. (MENT-1512)

  • With Enterprise Spider, "Error while parsing DSN" can be returned when connecting to an ODBC source. (MENT-1316)

  • Last binlog file and position are "empty" in mariadb-backup --prepare output. (MDEV-26322)

  • "Error" is shown instead of NULL in performance schema table P_S.THREADS_CONNECTION_TYPE for background threads. (MDEV-28255)

  • With Enterprise Spider, login to ODBC resources fails if the password contains a semicolon. (MENT-805)

  • When setting group_concat_max_len to 1 GB or more and using GROUP_CONCAT() in a subquery, the result gets truncated. (MDEV-28490)

  • Crash recovery fails if the configured server ID does not match the server ID in the crashed data directory. (MDEV-27342)

  • The innochecksum -w option was inadvertently removed. (MDEV-28181)

  • Poor scaling with InnoDB and utf8mb3 (MDEV-27767)

  • mariadb-backup --log-copy-interval is measured in milliseconds in MariaDB Enterprise Server 10.5 and in microseconds in MariaDB Enterprise Server 10.6. (MDEV-27919)

  • Upsert during ALTER TABLE results in Duplicate entry error. (MDEV-15250)

  • After a failed IMPORT TABLESPACE fails to delete files, DROP TABLE on the table can result in ERROR 1005 (HY000): Can't create table test.t2 (errno: 184 "Tablespace already exists") (MDEV-27274)

  • Query performance degradation when using many tables. (MDEV-28073)

  • JSON_TABLE doesn't allow one to extract a JSON ""subdocument"" into a JSON column. (MENT-1497)

  • With MariaDB Enterprise Cluster, no shared cipher warning when starting without encryption config. The warning should be about a missing ssl_cert configuration. (MENT-1462)

Related to install and upgrade

  • 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 hashicorp_key_management encryption plugin is loaded, mariadb-dump 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 hashicorp_key_management encryption plugin 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 MariaDB Support.

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

  • On Windows, error during upgrade from 10.6.5 to 10.6.7: Installation directory ''C:\Program Files\[MariaDB 10.6](../../mariadb-community-server-release-notes/release-notes-mariadb-10-6-series/what-is-mariadb-106.md)\'' exists and is not empty. (MDEV-27828)

  • On Windows, error during installation: InnoDB: innodb_page_size=65536 requires innodb_buffer_pool_size >= 20MiB current 10MiB (MDEV-28471)

Changes in Storage Engines

Interface Changes

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.8-4 is provided for:

  • CentOS 7 (x86_64)

  • Debian 9 (x86_64, ARM64)

  • Debian 10 (x86_64, ARM64)

  • Debian 11 (x86_64, ARM64)

  • Microsoft Windows (x86_64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

Note

This is the final release for Debian 9.

Installation Instructions

Upgrade Instructions

This page is: Copyright © 2025 MariaDB. All rights reserved.

PreviousRelease Notes for MariaDB Enterprise Server 10.6.9-5NextRelease Notes for MariaDB Enterprise Server 10.6.7-3

Last updated

Was this helpful?