Release Notes for MariaDB Enterprise Server 10.4.21-13

When an ALTER TABLE ... ADD COLUMN statement is executed with ALGORITHM=INSTANT, a warning is not raised when the operation causes the default value of a DATE column to be truncated. (MDEV-25971)

Possible server crash when pushing a WHERE condition over a mergeable derived table / view / CTE DT into a grouping view / derived table / CTE V whose item list contained set functions with constant arguments. (MDEV-25635)

Server crashes on second execution of a stored procedure or a prepared statement when the corresponding query executes a window function on a view, CTE, or derived table. (MDEV-25565)

Server crashes possible when executing a prepared statement with a hanging recursive CTE. (MDEV-26135)

Server crashes while executing query with a CTE in a prepared statement or stored procedure. (MDEV-26025)

Server crashes while executing query with a recursive CTE that is indirectly used twice. (MDEV-26202)

Server crashes due to infinite recursion while processing an embedded recursive CTE with missing RECURSIVE. (MDEV-26095)

Server crashes in InnoDB deadlock checker under high load. (MDEV-25594)

Server crashes when a virtual generated column has a prefix index. (MDEV-26220)

Server crashes possible when using virtual generated columns. (MDEV-18166, MDEV-18249)

Server crashes while executing DELETE when a YEAR column is truncated. (MDEV-17890)

Server crashes while executing SET ROLE when a hostname cannot be resolved. (MDEV-26081)

Server crashes when a subquery references an outer column in an ORDER BY clause. (MDEV-25629)

Server crashes due to a stack overrun in the query optimizer while executing query with more than 32 equality conditions that compare columns of different tables (such as tableX.colX=tableY.colY). (MDEV-17783)

Server crashes when a window function is the left expression of an IN(SELECT ..) subquery. (MDEV-25630)

Possible deadlock on a Replica server using GTID Replication when slave_parallel_mode=optimistic and OPTIMIZE TABLE, REPAIR TABLE, or ANALYZE TABLE is executed. (MDEV-17515)

Server crashes when ALTER TABLE .. ADD FULLTEXT INDEX fails on an InnoDB table. (MDEV-25721)

Server crashes while executing TRUNCATE on an InnoDB table with a Full-Text Index. (MDEV-25663)

Server crashes while executing ALTER TABLE on an InnoDB table with virtual generated columns that are indexed. (MDEV-25872)

Server crashes while executing CHECK TABLE when innodb_read_only is enabled. (MDEV-25886)

Server crashes when a connection is killed while executing ALTER TABLE after previously locking the table with LOCK TABLE. (MDEV-17749)

Server crashes when the global value of the system_versioning_asof system variable is set using a stored function that reads the value of another global system variable. (MDEV-16481)

Server crashes when MariaDB Enterprise Audit is active and usernames longer than 256 characters are used. (MENT-1019)

Server crashes when MariaDB Enterprise Audit is active and audit log file rotation is triggered. (MENT-1207)

Server crashes while executing query with a CTE that is used at least twice and that references an embedded recursive CTE. (MDEV-26108)

Possible crash with transactions having changes for tables with no primary key to apply in parallel, when using MariaDB Enterprise Cluster. (MDEV-25551)

Server crashes when executing CREATE TABLE to create a Spider table with a COMMENT value that does not contain embedded double quotes. (MDEV-26139)

Server crashes when a client connects during shutdown. (MDEV-18353)

When CREATE OR REPLACE TABLE fails after dropping the table, the DROP TABLE operation is not written into the binary log. (MDEV-25595)

The SHOW GRANTS statement does not quote role names properly for DEFAULT ROLE. (MDEV-26080)

The innochecksum utility reports errors for freed pages. (MDEV-25361)

When an unknown column is referenced in the WHERE clause of a recursive CTE, the query sometimes succeeds instead of failing with an ER_BAD_FIELD_ERROR. (MDEV-26189)

Reusing CTE inside a function fails with the ER_NO_SUCH_TABLE error code. (MDEV-23886)

Several fixes for MariaDB Enterprise Cluster (Galera) SST scripts. (MDEV-20580, MDEV-25818, MDEV-25759, MDEV-25719, MDEV-15639, MDEV-15371, MDEV-18797, MENT-1170, MDEV-24979, MDEV-21192)

With MariaDB Enterprise Cluster, when wsrep_sst_method=mariabackup, MariaDB Enterprise Backup does not inherit server options set by the Environment systemd configuration parameter. (MDEV-24962)

With MariaDB Enterprise Cluster, when wsrep_sst_method=rsync is set and log-bin and/or log-bin-index are set to custom paths, the rsync SST does not copy the binary log index. (MDEV-25978)

As a result of this issue, a Joiner node writes the following error to the MariaDB Error Log:

tail: cannot open 'mysql-bin.index' for reading: No such file or directory

With MariaDB Enterprise Cluster, when wsrep_sst_method=rsync is set, rsync for a new SST process may be killed rather than the rsync for the old SST process. (MDEV-25880)

With MariaDB Enterprise Cluster, the WSREP threads could write warnings about foreign keys to the MariaDB Error Log when wsrep_debug is not enabled. (MDEV-26062)

• In prior releases, the following warning could be written to the log:

  InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `schema`.`child_table`
  

• Starting with this release, the WSREP threads will only write warnings about foreign keys to the MariaDB Error Log when wsrep_debug is enabled.

The CREATE INDEX statement may check the wrong maximum column length. (MDEV-26203)

The Spider storage engine handles ">=" as ">" in some cases, where multi-column indexes are used. (MDEV-25985)

The max_password_errors system variable does not work correctly with the ed25519 authentication plugin. (MDEV-25641)

The "Condition pushdown into derived table" optimization cannot be applied if the expression being pushed refers to a derived table column which is computed from an expression that has a stored function call, @session variable reference, or other similar construct. (MDEV-25969)

A query that uses ORDER BY .. LIMIT clause and "Range checked for each record" optimization could produce incorrect results. (MDEV-25858)

An aborted OPTIMIZE TABLE statement is logged in the binary log and replicates to the Replica server. (MDEV-22530)

EXPLAIN shows an execution plan different from actually executed (MDEV-25682)

For system-versioned tables, the SHOW INDEX statement displays the system-invisible row_end column as part of the primary key. (MDEV-16857)

For system-versioned tables partitioned by SYSTEM_TIME, overflowing the partitions leads to incorrect results from SELECT. result (MDEV-22247)

For Spider tables, SELECT statements that use CASE WHEN .. THEN can result in syntax error. (MDEV-24760)

For Spider tables, SELECT statements that use the JSON_EXTRACT() function in the WHERE clause can result in a syntax error. (MDEV-24517)

For Spider tables, UPDATE statements that call native functions using remove_str (such as TRIM()) fail with the ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT error code. (MDEV-24020)

For Spider tables, server-sided prepared statements (created by PREPARE and executed by EXECUTE) incorrectly turn unsigned integer literals into signed integers. (MDEV-25808)

For Spider tables, statements that use the JSON_REPLACE() function fail with the ER_SP_DOES_NOT_EXIST error code. (MDEV-24523)

With MariaDB Enterprise Audit, the CREATE PROCEDURE and DROP PROCEDURE statements are not logged to the audit log. (MENT-1169)

With MariaDB Enterprise Backup, the binary log position written to the xtrabackup_binlog_info file during the backup is incorrect for replication. (MDEV-23080)

With MariaDB Enterprise Cluster, when wsrep_sst_method=mariabackup, a typo in the SST script causes SST failure on the Donor node. (MDEV-26117)

For Spider tables, SELECT statements that use DISTINCT do not work properly in some cases. (MDEV-26013)

When mariadbd is compiled with WolfSSL, the server fails to accept connections using TLS 1.3 and AES-GCM cipher. (MDEV-22221)