Release Notes for MariaDB Enterprise Server 10.4.17-10

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)

Back port of a MariaDB Server 10.5 feature to not acquire record locks when covering table locks exist. (MENT-403)

Change by default. ()

One instant including multiple RENAME for indexes can corrupt the index cache. ()

A rolling upgrade for from 10.3 to 10.4 can result in data loss. ()

DELETE .. FOR PORTION OF statement accepts non-constant FROM .. TO clause. This contradicts the documentation and is inconsistent with the behavior of the statement. ()

Potential stack overflow in fulltext search with a complex MATCH .. AGAINST string. ()

mariadb-backup 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|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 on a table that contains indexed virtual columns. ()

Possible server crash for queries using the window function ()

Server crash can occur when is used. ()

Possible crash when using Spider Tables and partitions. ()

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)

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

Possible server crash with executed on a system versioned table, if variable system_versioning_asof was set to a value of type instead of . ()

Server crash when SELECT WSREP_LAST_SEEN_GTID() while Galera replication is not enabled (wsrep-on=OFF). ()

Server crash if function FORMAT(num, decimal_position[, locale]) is used with a decimal_position > 30. ([MDEV-23415](https://jira.mariadb.org/browse/MDEV-23415))

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 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 tables with foreign keys and running or on them. ()

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

UDF cannot be uninstalled if the UDF library file doesn't exist. ()

with type 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 innodb_flush_method O_DIRECT 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 fails with error message. (MENT-1016)

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

ErrorERROR 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 MIN(time_expr) and MAX(time_expr) with GROUP BY ()

Syntax error results in misleading message on about missing system table mysql.proc ()

FORMAT(num, decimal_position [, locale]) 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 ()

mariadb_es_repo_setup curl failed on Ubuntu Focal if ca-certificates is not installed. Now it will prompt an error about missing ca-certificates (MENT-971)

Debian 10

SUSE Linux Enterprise Server 12

SUSE Linux Enterprise Server 15

Ubuntu 16.04

Ubuntu 18.04

Ubuntu 20.04

Microsoft Windows