Release Notes for MariaDB Enterprise Server 10.4.8-3
This third release of MariaDB Enterprise Server 10.4 is a maintenance release, including a variety of fixes.
MariaDB Enterprise Server 10.4.8-3 was released on 2019-09-30.
Can result in data loss
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)
INSTANT DROP COLUMN on an indexed column can result in a crash or data corruption. (MDEV-20479)
Can result in crashes, hangs, stalls
Can result in unexpected behavior
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)
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.4.8-3 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".