Release Notes for MariaDB Enterprise Server 10.4.8-3

Due to a race condition in InnoDB, an exclusive lock to an inserted record could be wrongly granted to multiple transactions when the INSERT transaction commits. This could lead to a server crash or data loss. (MDEV-15326)

INSERT...ON DUPLICATE KEY UPDATE, when there is more than one key, could result in inconsistent data between master and slave for replication mode MIXED and STATEMENT. This has been fixed for MIXED, but cannot be controlled by the replication for STATEMENT based replication.

Inconsistent Slaves need to be set up again from the Master. (MDEV-17614)

Wrong value on instantly added column can occur after DELETE and a following UPDATE of PRIMARY KEY. (MDEV-20066)

INSTANT DROP COLUMN on an indexed column can result in a crash or data corruption. (MDEV-20479)

Replication could hang for InnoDB transactions as InnoDB has its own concurrency control innodb_thread_concurrency. (MDEV-20247)

Fix potential crash in ON UPDATE CASCADE when the foreign table is system versioned. (MDEV-20311)

After setting SET foreign_key_checks=0 it is possible to drop indexes from referenced (parent) tables, which could cause InnoDB to behave as if table doesn't exist in engine (MDEV-17187)

Fix for corner case where MariaDB Backup could fail because encrypted data files could not be copied if created shortly before the backup was started. (MDEV-18128)

MariaDB Backup could fail in the prepare face if the redo log is bigger than 512GB. (MDEV-20060)

If user enables encryption for temporary table and uses full_crc32 format then temp table read may give error. (MDEV-20340)

Optimized scanning of the undo log versions while scanning the secondary index versions. (MDEV-20301)

Improved performance for mariabackup --prepare and InnoDB crash recovery, and the InnoDB write performance. (MENT-139)