Release Notes for MariaDB Enterprise Server 10.4.11-5

A table could not be loaded after an instant ALTER ... ADD COLUMN or ALTER ... DROP COLUMN, if the primary key is a CHAR column with variable-length encoding like UTF8 (MDEV-21088)

In rare conditions commits could be applied in the wrong order if the replica is running in optimistic mode. (MDEV-20707)

Primary (master) could crash when it executes RESET MASTER and a replica (slave) reconnects having reset its connection status with the primary (e.g., CHANGE MASTER TO MASTER_USE_GTID = slave_pos). (MENT-19376)

"Out of memory" error could occur when accessing partitioned InnoDB tables. (MDEV-20611)

A crash could occur when ADD PRIMARY KEY was executed by a connection just after another connection issued an instant ADD COLUMN to the same InnoDB table and if DMLs were executed at the same time. (MDEV-21045)

A crash could occur when rowid filtering optimization is enabled using optimizer_switch='rowid_filter=on' (MDEV-20407)

Client received error SEC_E_INVALID_TOKEN when SSL is used and connecting to MariaDB Enterprise Server running on Microsoft Windows. (MDEV-13492)

The restore of Aria tables was not always possible if MariaDB Backup was using the parameters --prepare --incremental (MDEV-18310)

An incomplete result set was returned when sort_buffer_size was too small. (MDEV-21044)

A query with system versioning filters did not show an error when executed on not system versioned tables. (MDEV-18929)

CHECK TABLE erroneously reported error "Found a misplaced row" for system versioned tables with history partition. (MDEV-21011)

An instant operation could fail when adding a column and changing the collation on a non-indexed column. (MDEV-20190)