Release Notes for MariaDB Enterprise Server 10.5.27-21

Using group_concat with a compressed or GIS column can lead to a server crash and potential data corruption for users performing group_concat operations on tables containing these data types (MDEV-16699)

A query could cause a crash if it has a HAVING clause with a construct tblX.column=column_or_constant and the optimizer was able to infer that table tblX is a constant table. Note that HAVING clause may be from the original query or may come from Condition Pushdown optimization) (MDEV-23983)

Calling a UDF for the engine SPIDER results in a crash if the SPIDER storage engine plugin could not be loaded (MDEV-34682)

Under Windows Subsystem for Linux, InnoDB crashes on ALTER TABLE or OPTIMIZE TABLE (MDEV-34938)

Server crashes when setting wsrep_cluster_address after adding invalid value to wsrep_allowlist table (MDEV-31173)

mariadbd hangs on startup when --init-file target does not exist (MDEV-34814)

Possible server crash in cases where the function DEFAULT() is part of a query (MDEV-35276)

Possible unique hash index corruption for system-versioned tables after DML including DELETE HISTORY statement. This can lead to data corruption, crashes, and incorrect query results (MDEV-33470)

• Possible error log entry

[ERROR] InnoDB: Record in index `c` of table `test`.`t` was not found on update...

In some situations, where a MariaDB Enterprise cluster (Galera) node crashes, some threads are still working. This is visible via the error log, which is still getting errors written by the node. As the node stops interacting correctly with other cluster nodes and is blocking them from taking over the primary state, the whole cluster hangs (MDEV-32363)

When a user runs mariadb-binlog with --stop-position, they would expect the output to contain events up to that event. If the output did not contain events up to that event, this may result in various unexpected behaviors, e.g., an incomplete database state if they piped the output to the mariadb client and expected certain transactions to have executed in the database, yet never were run (MDEV-27037)

Changing a data type of a field used in a foreign key constraint fails with Error "Cannot change column '...': used in a foreign key constraint '...'" (MDEV-34392)

• This ALTER only fails if the type of field is changed in a multi-ALTER statement, where types of of other fields are changed with the ALTER

Creation of a view with UNION and SELECT ... FOR UPDATE in the definition fails with error "ER_PARSE_ERROR (1064): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near..." (MDEV-29537)

INSERT...SELECT on MyISAM or ARIA tables are replicated by MariaDB Enterprise Cluster (Galera) (MDEV-34647)

SELECT MIN on Spider table returns more rows than expected (MDEV-26345)

Can't selectively restore sequences using innodb tables from backup (MDEV-32350)

LOAD DATA INFILE with geometry data fails (MDEV-34883)

Executing an UPDATE statement in prepared statement mode having positional parameter bound with an array can result in an incorrect number of updated rows in case there is a BEFORE UPDATE trigger that executes yet another UPDATE statement to change a table (MDEV-34718)

Recovery fails to note some log corruption, resulting in "log sequence number in the future" error messages, and possibly adds more corruption (MDEV-34802)

• When log corruption is noted, the server can now only be started when using the option innodb_force_recovery

Unexpected error "Row size too large (> 8123)..." for a correct INSERT after a instantly dropped BLOB column (MDEV-35122)

Wrong binlog timestamps on secondary nodes of MariaDB Enterprise Cluster (MENT-2164)

When the MariaDB Enterprise Audit Plugin is configured to log ACL queries, a statement CREATE USER .. IDENTIFIED VIA ed25519 USING PASSWORD(...) is logged including the password (MENT-2181)

When the MariaDB Enterprise Audit Plugin is configured to log ACL queries, passwords are masked for CREATE USER .. IDENTIFIED BY, but not for CREATE OR REPLACE USER, or SET STATEMENT ... FOR CREATE USER (MENT-2188)

Unnecessary copying of log records by MariaDB Enterprise Backup when further transaction commits are blocked by BACKUP STAGE BLOCK_COMMIT (MENT-2133)

• It also would cause further effort of rolling back incomplete transactions after the backup is restored

Aria internal temporary tables unnecessarily write all changed blocks to disk when the table is closed at end of query (MENT-2182)