Release Notes for MariaDB Enterprise Server 10.2.33-8

This eighth release of MariaDB Enterprise Server 10.2 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.2.33-8 was released on 2020-09-08.

Notable Changes

  • Limit innodb_encryption_threads to 255. (MDEV-22258)

  • Minimum value of max_sort_length raised to 8 (previously 4) so fixed size data types like DOUBLE and BIGINT are not truncated for lower values of max_sort_length. (MDEV-22715)

  • INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION requires PROCESS instead of SUPER privilege. (MDEV-23003)

  • Backport from MariaDB Server 10.5.4 of improvements to DROP TABLE for InnoDB. (MENT-636)

  • InnoDB updated to 5.7.29.

Bugs Fixed

Can result in data loss

  • InnoDB doublewrite recovery can corrupt data pages. (MDEV-11799)

  • InnoDB table can disappear when trying to change primary key after disabling Foreign Key checks and violating a Foreign Key constraint. (MENT-804)

  • InnoDB corruption in delete buffering. (MDEV-22497)

Can result in hang or crash

  • InnoDB deadlock in FLUSH TABLES .. FOR EXPORT (MDEV-22890)

  • InnoDB data file extension is not crash-safe. (MDEV-23190)

  • innodb_log_optimize_ddl=OFF is not crash safe. (MDEV-21347)

  • Deadlock involving parallel workers, STOP SLAVE, and FLUSH TABLES WITH READ LOCK (MDEV-23089)

  • Crashes when running a SQL query containing a specific subquery pattern. (MDEV-23221)

  • Dropping the adaptive hash index may cause DDL to lock up InnoDB (MDEV-22456)

  • RESET MASTER TO could result in a crash, when the value exceeds the max allowed 2147483647. (MDEV-22451)

  • Crash on WITH RECURSIVE large query. (MDEV-22748)

  • Crash with Prepared Statement with a ? parameter inside a re-used CTE. (MDEV-22779)

  • MariaDB could crash after changing the query_cache size. (MDEV-5924)

  • Crash in CREATE TABLE AS SELECT when the precision of returning type = 0 (MDEV-22502)

  • ENUM or SET in a CREATE TABLE statement, which has a 0x00 byte in one of the values could crash the server. (MDEV-22111)

  • InnoDB recovery can block server startup. (MENT-915)

Can result in unexpected behavior

  • Service shutdown fails if OS datetime has been updated backwards. (MDEV-17481)

  • ALTER TABLE .. ANALYZE PARTITION can run for hours for huge tables if engine-independent persistent statistics are enabled, due to reading and locking of all rows in the InnoDB table instead of for the partition. (MDEV-21472)

  • UPDATE can fail with privilege error when UPDATE privilege exists at database level but SELECT privilege exists at table level. (MDEV-23010)

  • Latency and throughput regression identified in write-heavy benchmarks for latest releases in MariaDB Server 10.2, 10.3, and 10.4. (MENT-909)

  • START SLAVE UNTIL .. file .. pos stops at an earlier position earlier than defined if the transaction that spans over the given stop position has to roll back due to conflicts. (MDEV-15152)

  • mariabackup --prepare does not stop on errors while applying InnoDB redo log. (MDEV-22354)

Install and Upgrade

  • UNINSTALL PLUGIN and UNINSTALL SONAME can't run if the library file doesn't exist. (MDEV-21258)

Interface Changes

  • ER_TRANSACTIONAL_ARIA_LOG_ENGINE error code added

  • max_sort_length system variable minimum value changed from 4 to 8

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.2.33-8 is provided for:

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 6

  • CentOS 8

  • CentOS 7

  • CentOS 6

  • Ubuntu 18.04

  • Ubuntu 16.04

  • Debian 10

  • Debian 9

  • Debian 8

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 12

  • Microsoft Windows