The most recent release of MariaDB Enterprise Server 10.6 is: 10.6.27-23
Download Enterprise Server 10.6.27-23
{% endhint %} MariaDB Enterprise Server 10.6.8-4 is a Stable (GA) maintenance release of [MariaDB Enterprise Server](https://mariadb.com/docs/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](https://www.cve.org/) link) | CVSS base score | | ------------------------------------------------------------------------------- | --------------- | | [CVE-2022-27458](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27458) | 7.5 | | [CVE-2022-27457](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27457) | 7.5 | | [CVE-2022-27456](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27456) | 7.5 | | [CVE-2022-27455](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27455) | 7.5 | | [CVE-2022-27452](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27452) | 7.5 | | [CVE-2022-27451](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27451) | 7.5 | | [CVE-2022-27449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27449) | 7.5 | | [CVE-2022-27448](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27448) | 7.5 | | [CVE-2022-27447](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27447) | 7.5 | | [CVE-2022-27446](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27446) | 7.5 | | [CVE-2022-27445](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27445) | 7.5 | | [CVE-2022-27444](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27444) | 7.5 | | [CVE-2022-27387](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27387) | 7.5 | | [CVE-2022-27386](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27386) | 7.5 | | [CVE-2022-27384](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27384) | 7.5 | | [CVE-2022-27383](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27383) | 7.5 | | [CVE-2022-27382](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27382) | 7.5 | | [CVE-2022-27381](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27381) | 7.5 | | [CVE-2022-27380](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27380) | 7.5 | | [CVE-2022-27379](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27379) | 7.5 | | [CVE-2022-27378](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27378) | 7.5 | | [CVE-2022-27377](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27377) | 7.5 | | [CVE-2022-27376](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27376) | 7.5 | | [CVE-2022-21451](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21451) | 7.5 | | [CVE-2022-32088](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32088) | 6.5 | | [CVE-2022-32087](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32087) | 6.5 | | [CVE-2022-32086](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32086) | 6.5 | | [CVE-2022-32085](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32085) | 6.5 | | [CVE-2022-32083](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32083) | 6.5 | | [CVE-2021-46669](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46669) | 6.5 | ## Backported Features MariaDB Enterprise Server enables a predictable development and operations experience through an [enterprise lifecycle](/docs/release-notes/enterprise-server/about/enterprise-server-lifecycle.md). These new features have been backported after reaching maturity in MariaDB Community Server: * [mariadb-dump option --as-of](/docs/server/clients-and-utilities/backup-restore-and-import-clients/mariadb-dump.md) reads data as of specific timestamp from system-versioned tables. (MENT-1457) * Added [JSON\_EQUALS() function](/docs/server/reference/sql-functions/special-functions/json-functions/json_equals.md) to check JSON equality. (MENT-1452) * Added [JSON\_NORMALIZE() function](/docs/server/reference/sql-functions/special-functions/json-functions/json_normalize.md) to normalize JSON values. (MENT-1456) * Added [password\_reuse\_check password validation plugin](/docs/server/reference/plugins/password-validation-plugins/password-reuse-check-plugin.md). (MENT-1451) ## 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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-28541), [MDEV-28537](https://jira.mariadb.org/browse/MDEV-28537)) * Starting with this release, when [wsrep\_sst\_method](/docs/galera-cluster/reference/galera-cluster-system-variables.md#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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-23210)) * When rows are inserted into an intermediate temporary table via the [LOAD DATA INFILE statement](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/load-data-into-tables-or-index/load-data-infile.md) ,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](/docs/server/ha-and-performance/standard-replication/replication-and-binary-log-system-variables.md) is set, which prevents the operation from properly replicating to replica servers. ([MDEV-24667](https://jira.mariadb.org/browse/MDEV-24667)) * When [innodb\_disallow\_writes=ON](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#innodb_disallow_writes) is set, [mariadb-admin shutdown](/docs/server/clients-and-utilities/administrative-tools/mariadb-admin.md) can hang. ([MDEV-25975](https://jira.mariadb.org/browse/MDEV-25975)) * Starting with this release, the [innodb\_disallow\_writes system variable](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#innodb_disallow_writes) has been removed. * 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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-11853)) * InnoDB page corruption on btrfs filesystem with `innodb_use_native_aio=1` ([MDEV-27900](https://jira.mariadb.org/browse/MDEV-27900)) * Semisync-replica server recovery fails to rollback a prepared transaction. ([MDEV-28461](https://jira.mariadb.org/browse/MDEV-28461)) ### Can result in a hang or crash * With MariaDB Enterprise Cluster, powered by Galera, when [wsrep\_sst\_method](/docs/galera-cluster/reference/galera-cluster-system-variables.md#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](https://jira.mariadb.org/browse/MDEV-27524)) * When a window function is used in the global ORDER BY clause of a [SELECT statement](/docs/server/reference/sql-statements/data-manipulation/selecting-data/select.md) with a `UNION`, the statement should be rejected, but the server executes the statement and crashes with a segmentation fault. ([MDEV-15208](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-26009)) * When [innochecksum](/docs/server/clients-and-utilities/administrative-tools/innochecksum.md) is executed on an encrypted tablespace file using the [--page-type-summary or -S option](/docs/server/clients-and-utilities/administrative-tools/innochecksum.md#options), `innochecksum` crashes with a segmentation fault unless the [--page-type-dump or -D option](/docs/server/clients-and-utilities/administrative-tools/innochecksum.md#options) is also specified. ([MDEV-27835](https://jira.mariadb.org/browse/MDEV-27835)) * When an invalid [CREATE SEQUENCE .. RESTART statement](/docs/server/reference/sql-structure/sequences/create-sequence.md) is used inside of a [CREATE PROCEDURE](/docs/server/server-usage/stored-routines/stored-procedures/create-procedure.md) or [CREATE FUNCTION](/docs/server/reference/sql-statements/data-definition/create/create-function.md) statement, the server can crash while parsing the statement. ([MDEV-28220](https://jira.mariadb.org/browse/MDEV-28220)) * When a table contains a virtual generated column that is defined using the [IF()](/docs/server/reference/sql-statements/programmatic-compound-statements/if.md) and [DATE\_FORMAT()](/docs/server/reference/sql-functions/date-time-functions/date_format.md) functions, inserting a row into the table can cause the server to crash with a segmentation fault. ([MDEV-24176](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-27212)) * Querying views can result in mergeable derived tables. * Using subqueries with outer references can result mergeable derived tables. * When [ANALYZE FORMAT=JSON](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/analyze-format-json.md) is executed with a query that contains a subquery, the server can crash. ([MDEV-28268](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-28583)) * This issue is confirmed to happen with [wsrep\_sst\_method](/docs/galera-cluster/reference/galera-cluster-system-variables.md#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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-27713)) * Server crashes when executing a shutdown statement after starting an XA transaction. ([MDEV-26575](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-24560)) * Possible crash after or during `DROP TABLE` when the InnoDB buffer pool size has been changed. ([MDEV-27891](https://jira.mariadb.org/browse/MDEV-27891)) * InnoDB crash on multiple concurrent `SHOW TABLE STATUS` ([MDEV-26551](https://jira.mariadb.org/browse/MDEV-26551)) * Shutdown hangs after altering an InnoDB partition when `innodb_fast_shutdown=0` ([MDEV-28079](https://jira.mariadb.org/browse/MDEV-28079)) ### Can result in unexpected behavior * When [OPTIMIZE TABLE](/docs/server/ha-and-performance/optimization-and-tuning/optimizing-tables/optimize-table.md) is executed on a [sequence](/docs/server/reference/sql-structure/sequences.md), the server raises an ER\_BINLOG\_UNSAFE\_STATEMENT warning, even if [binlog\_format](/docs/server/ha-and-performance/standard-replication/replication-and-binary-log-system-variables.md) is set to ROW or MIXED. ([MDEV-24617](https://jira.mariadb.org/browse/MDEV-24617)) * The warning can appear in the [MariaDB Error Log](/docs/server/server-management/server-monitoring-logs/error-log.md) as the following: ``` [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 ``` * When an [UPDATE](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/update.md) or [DELETE](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/delete.md) statement uses an [OR](/docs/server/reference/sql-structure/operators/logical-operators/or.md) clause, the server raises an ER\_UPDATE\_WITHOUT\_KEY\_IN\_SAFE\_MODE error. ([MDEV-18304](https://jira.mariadb.org/browse/MDEV-18304)) * The error can appear on the client as the following: ``` 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](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/update.md) uses a subquery inside an [IN() clause](/docs/server/reference/sql-structure/operators/comparison-operators/in.md), 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](https://jira.mariadb.org/browse/MDEV-22377)) * When a table contains multiple [ENUM](/docs/server/reference/data-types/string-data-types/enum.md) columns with identical values, the values could become corrupt if multi-byte character sets are used. ([MDEV-28078](https://jira.mariadb.org/browse/MDEV-28078)) * When [DECIMAL](/docs/server/reference/data-types/numeric-data-types/decimal.md) columns are read from [information\_schema.PROCESSLIST](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-processlist-table.md), the server could incorrectly raise an ER\_BAD\_DATA warning. ([MDEV-28131](https://jira.mariadb.org/browse/MDEV-28131))\ The warning can appear on the client as the following after executing `SHOW WARNINGS`: ``` Encountered illegal value '' when converting to DECIMAL ``` * With [sql\_mode=ORACLE](/docs/server/server-management/variables-and-modes/sql_mode.md), the parser allows functions to be called using `PACKAGE_NAME.FUNCTION_NAME()`, but the parser raises a ER\_PARSE\_ERROR error if the function is called using `DATABASE_NAME.PACKAGE_NAME.FUNCTION_NAME()`. ([MDEV-28166](https://jira.mariadb.org/browse/MDEV-28166)) * When a view is used to update multiple rows of a [temporal table](/docs/server/reference/sql-structure/temporal-tables.md) in a single [UPDATE statement](/docs/server/reference/sql-statements/data-manipulation/changing-deleting-data/update.md), the server incorrectly raises a ER\_WARN\_VIEW\_WITHOUT\_KEY warning. ([MDEV-22973](https://jira.mariadb.org/browse/MDEV-22973)) * The warning can appear on the client as the following after executing [SHOW WARNINGS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-warnings.md): ``` View being updated does not have complete key of underlying table in it ``` * When using [mariadb-binlog](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog.md) with [--raw](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog.md#-raw) and [--stop-never](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog.md#-stop-never), events from the primary server's currently active log file are not written to their respective log file specified by [--result-file](/docs/server/clients-and-utilities/logging-tools/mariadb-binlog.md#-result-file). ([MDEV-14608](https://jira.mariadb.org/browse/MDEV-14608)) * When a prepared statement is used to execute [EXPLAIN](/docs/server/reference/sql-statements/administrative-sql-statements/analyze-and-explain-statements/explain.md), a different query plan can be returned on the second execution. ([MDEV-19631](https://jira.mariadb.org/browse/MDEV-19631)) * When [slave\_compressed\_protocol](/docs/server/ha-and-performance/standard-replication/replication-and-binary-log-system-variables.md) 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](https://jira.mariadb.org/browse/MDEV-25580)) * The server and [MariaDB Enterprise Backup](/docs/server/server-usage/backup-and-restore/mariadb-enterprise-backup.md) can raise unnecessary warnings about tablespace IDs in some scenarios. ([MDEV-27343](https://jira.mariadb.org/browse/MDEV-27343)) * The warning can appear as the following: ``` InnoDB: Allocated tablespace ID TABLESPACE_ID for DATABASE_NAME/TABLE_NAME, old maximum was 0 ``` * This warning can be written to standard output (stdout) when preparing a backup with [MariaDB Enterprise Backup](/docs/server/server-usage/backup-and-restore/mariadb-enterprise-backup.md). * This warning can be written to the [MariaDB Error Log](/docs/server/server-management/server-monitoring-logs/error-log.md) when InnoDB performs crash recovery at startup. * With MariaDB Enterprise Cluster, the joiner node fails to complete an SST when [innodb\_log\_group\_home\_dir](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#innodb_log_group_home_dir) specifies a directory different than [datadir](/docs/server/server-management/variables-and-modes/server-system-variables.md#datadir). ([MDEV-27740](https://jira.mariadb.org/browse/MDEV-27740)) * When a non-partitioned table using the `DATA DIRECTORY` clause is converted to a partitioned table, the `DATA DIRECTORY` clause is silently ignored, and the partitioned table is moved to the default directory. ([MDEV-27065](https://jira.mariadb.org/browse/MDEV-27065)) * Starting with this release, the server will raise the WARN\_OPTION\_IGNORED warning. * When a table contains an invisible column, [mariadb-dump](/docs/server/clients-and-utilities/backup-restore-and-import-clients/mariadb-dump.md) does not produce the correct [CREATE TABLE statement](/docs/server/server-usage/tables/create-table.md) in the backup file. ([MDEV-28253](https://jira.mariadb.org/browse/MDEV-28253)) * When a Spider table is queried using `IF(COUNT() ..)`, the server can raise an ER\_BAD\_FIELD\_ERROR error. ([MDEV-25116](https://jira.mariadb.org/browse/MDEV-25116)) * With MariaDB Enterprise Cluster, State Snapshot Transfers (SSTs) can fail on the donor node when binary logs are enabled. ([MDEV-26201](https://jira.mariadb.org/browse/MDEV-26201)) * With MariaDB Enterprise Cluster, when [wsrep\_node\_address](/docs/galera-cluster/reference/galera-cluster-system-variables.md#wsrep_node_address) contains an IPv6 address and [wsrep\_sst\_receive\_address](/docs/galera-cluster/reference/galera-cluster-system-variables.md#wsrep_sst_receive_address) is set to the default value of `AUTO`, State Snapshot Transfers (SST) can fail. ([MDEV-26171](https://jira.mariadb.org/browse/MDEV-26171)) * With [temporal tables](/docs/server/reference/sql-structure/temporal-tables.md), replication can break if a system versioned table has been created on the replica via mariadb-dump, if the original table was altered before. ([MDEV-28254](https://jira.mariadb.org/browse/MDEV-28254)) * `mariadb-backup` does not detect multi-source replication primary. ([MDEV-21037](https://jira.mariadb.org/browse/MDEV-21037)) * `Master_SSL_Crl` shows `Master_SSL_CA` value in `SHOW REPLICA STATUS` output. ([MDEV-28428](https://jira.mariadb.org/browse/MDEV-28428)) * MariaDB Audit plugin produces corrupted log entries for `CONNECT` events. (MENT-1438) * `mariadb-dump` does not create a dump where the `sql_mode` is set correctly for SQL/PL packages. ([MDEV-27816](https://jira.mariadb.org/browse/MDEV-27816)) * Missing binlog data for [INSERT .. ON DUPLICATE KEY UPDATE](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert.md) ([MDEV-28310](https://jira.mariadb.org/browse/MDEV-28310)) * `mariadb-backup prepare` fails for incremental backups if a new schema is created after full backup. ([MDEV-28446](https://jira.mariadb.org/browse/MDEV-28446)) * Optimizer uses all partitions during an `UPDATE` and ignores partitioning filters. ([MDEV-28246](https://jira.mariadb.org/browse/MDEV-28246)) * When [INSERT .. ON DUPLICATE KEY UPDATE](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert.md) is executed and `binlog_format` is set to `MIXED`, the server raises an ER\_BINLOG\_UNSAFE\_STATEMENT warning even though the statement is written to the binary log in row-based format. ([MDEV-21810](https://jira.mariadb.org/browse/MDEV-21810)) * The warning can appear in the [MariaDB Error Log](/docs/server/server-management/server-monitoring-logs/error-log.md) as the following: ``` [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](/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/insert.md) is executed and `binlog_row_image` is set to `FULL`, the server does not write unchanged columns to the binary log. ([MDEV-21810](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-26322)) * "Error" is shown instead of NULL in performance schema table `P_S.THREADS_CONNECTION_TYPE` for background threads. ([MDEV-28255](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-28490)) * Crash recovery fails if the configured server ID does not match the server ID in the crashed data directory. ([MDEV-27342](https://jira.mariadb.org/browse/MDEV-27342)) * The `innochecksum -w` option was inadvertently removed. ([MDEV-28181](https://jira.mariadb.org/browse/MDEV-28181)) * Poor scaling with InnoDB and `utf8mb3` ([MDEV-27767](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-27919)) * Upsert during `ALTER TABLE` results in `Duplicate entry` error. ([MDEV-15250](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-27274)) * Query performance degradation when using many tables. ([MDEV-28073](https://jira.mariadb.org/browse/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](https://jira.mariadb.org/browse/MDEV-27437)) * On Windows, MSI installer does not install client shared libraries. ([MDEV-28581](https://jira.mariadb.org/browse/MDEV-28581)) * When the [hashicorp\_key\_management encryption plugin](/docs/server/security/encryption/data-at-rest-encryption/key-management-and-encryption-plugins/hashicorp-key-management-plugin.md) is loaded, [mariadb-dump](/docs/server/clients-and-utilities/backup-restore-and-import-clients/mariadb-dump.md) 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](/docs/server/security/encryption/data-at-rest-encryption/key-management-and-encryption-plugins/hashicorp-key-management-plugin.md) 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](https://csm.mariadb.com). * 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\'' exists and is not empty`. ([MDEV-27828](https://jira.mariadb.org/browse/MDEV-27828)) * On Windows, error during installation: `InnoDB: innodb_page_size=65536 requires innodb_buffer_pool_size >= 20MiB current 10MiB` ([MDEV-28471](https://jira.mariadb.org/browse/MDEV-28471)) ## Changes in Storage Engines * This release originally incorporated [MariaDB ColumnStore storage engine version 6.3.1](/docs/release-notes/columnstore/old-releases/mariadb-columnstore-6-release-notes/mariadb-columnstore-6-3-1-release-notes.md). * This release later incorporated [MariaDB ColumnStore storage engine version 6.4.1](/docs/release-notes/columnstore/old-releases/mariadb-columnstore-6-release-notes/mariadb-columnstore-6-4-1-release-notes.md). * This release later incorporated [MariaDB ColumnStore storage engine version 6.4.2](/docs/release-notes/columnstore/old-releases/mariadb-columnstore-6-release-notes/mariadb-columnstore-6-4-2-release-notes.md). * This release later incorporated [MariaDB ColumnStore storage engine version 6.4.4](/docs/release-notes/columnstore/old-releases/mariadb-columnstore-6-release-notes/mariadb-columnstore-6-4-4-release-notes.md). * This release now incorporates [MariaDB ColumnStore storage engine version 6.4.6](/docs/release-notes/columnstore/old-releases/mariadb-columnstore-6-release-notes/mariadb-columnstore-6-4-6-release-notes.md). ## Interface Changes * hashicorp\_key\_management\_check\_kv\_version system variable added * `innochecksum` --write (-w) command-line option added * [innodb\_disallow\_writes](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#innodb_disallow_writes) system variable removed * [Innodb\_encryption\_key\_rotation\_list\_length](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#Innodb_encryption_key_rotation_list_length) status variable removed * [Innodb\_num\_index\_pages\_written](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#Innodb_num_index_pages_written) status variable removed * [Innodb\_num\_non\_index\_pages\_written](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md#Innodb_num_non_index_pages_written) status variable removed * [JSON\_EQUALS()](/docs/server/reference/sql-functions/special-functions/json-functions/json_equals.md) function added * [JSON\_NORMALIZE()](/docs/server/reference/sql-functions/special-functions/json-functions/json_normalize.md) function added * `mariadb-backup` --sst-max-binlogs command-line option added * `mariadb-dump` --as-of command-line option added * `mariadbd` --hashicorp-key-management-check-kv-version command-line option added * `mariadbd` --password-reuse-check command-line option added * `mariadbd` --password-reuse-check-interval command-line option added * `password_reuse_check password_reuse_check.so` plugin added * [password\_reuse\_check\_history](/docs/server/reference/plugins/password-validation-plugins/password_reuse_check_interval.md) system table added * [password\_reuse\_check\_interval](/docs/server/reference/plugins/password-validation-plugins/password_reuse_check_interval.md) system variable added ## Platforms In alignment to the [enterprise lifecycle](/docs/release-notes/enterprise-server/about/enterprise-server-lifecycle.md), 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".](https://mariadb.com/engineering-policies) #### Note This is the final release for Debian 9. ## Installation Instructions * [Deploy MariaDB Enterprise with Repositories](/docs/server/server-management/install-and-upgrade-mariadb/mariadb-package-repository-setup-and-usage.md) * [Deploy MariaDB Enterprise with Package Tarballs](/docs/server/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/package-tarballs.md) * [Deploy MariaDB Enterprise with Docker](/docs/server/server-management/automated-mariadb-deployment-and-administration/docker-and-mariadb/deploy-mariadb-enterprise-server-with-docker.md) ## Upgrade Instructions * [Upgrade to MariaDB Enterprise Server 10.6](/docs/server/server-management/install-and-upgrade-mariadb/upgrading/upgrade-paths/mariadb-enterprise-server-10.6/upgrade-to-mariadb-enterprise-server-10.6.md) *This page is: Copyright © 2026 MariaDB. All rights reserved.* {% @marketo/form formid="4316" formId="4316" %}