Release Notes for MariaDB Enterprise Server 10.2.29-4

mariabackup --prepare --export ... could overwrite binary logs if certain conditions were present. (MDEV-20703)

Conditions which must be present to trigger this bug:

• mariabackup is executed on the MariaDB Server host, and

• Configuration files from the master are used, and

• Configuration files enable binary logging

If unable to upgrade to MariaDB Enterprise Server 10.2.29-4, where this bug is fixed, a workaround is available: use the --defaults option to mariabackup to avoid the bug-triggering conditions by specifying a different configuration file.

Prior removal of a FULLTEXT index from an InnoDB table can cause a hang on startup. (MDEV-19647)

Removal of a FULLTEXT index from an InnoDB table can cause a hang. (MDEV-19529)

Change to a InnoDB table containing a FULLTEXT index can cause Server to become unresponsive. (MDEV-20987)

Removal of a virtual column used by an index can result in a crash. (MENT-434)

CREATE INDEX, ALTER TABLE, or OPTIMIZE TABLE on an InnoDB table can cause Server to become unresponsive. (MDEV-20852)

Unnecessary logging of warnings to the error log regarding InnoDB maximum row size for DML statements which should be present only for DDL operations. (MENT-454)

After server restart, a SELECT using a FULLTEXT index on InnoDB tables can fail to return some data. (MDEV-19073)

MariaDB Enterprise Backup and MariaDB Backup, when using mbstream, recreated xtrabackup_info in the same directory as the backup file. Repeated extract of the backup could fail. (MDEV-18438)

mysqld_multi.sh script could not be launched and returned a syntax error. (MENT-433)

Though not supported on Microsoft Windows, the server_audit_output_type system variable for the Audit plugin accepted a SYSLOG value. (MDEV-19851)

Installing MariaDB Enterprise Server from repository failed on CentOS 7 due to package dependencies. (MENT-420)