Release Notes for MariaDB Xpand 5.3.14

MariaDB Xpand is a distributed SQL database that is part of MariaDB Platform X5. This release of MariaDB Xpand is a maintenance release.

MariaDB Xpand 5.3.14 was released on 2021-03-15.

This release note pertains to MariaDB Xpand version 5.3.14 and the Xpand Storage Engine packaged with MariaDB Enterprise Server 10.5.9-6.

Notable Changes

  • Added support for TLS 1.1 and later.

  • Added support for SHOW COLUMNS/FIELDS WHERE.

  • Added global variable have_statement_timeout.

  • Added global variable net_read_timeout.

  • The global value of the binlog_format system variable is now changeable.

  • The output of the SHOW FIELDS statement now shows when a default value is NULL.

  • The output of the SHOW BINARY LOGS statement now matches the output in ES.

  • Values of several columns in the COLUMNS information schema table are now improved:

    • The PRIVILEGES column is no longer NULL.

    • The EXTRA column shows an empty string instead of NULL.

    • The column_key column is now filled out correctly.

Issues Fixed

Can result in data loss

  • In Xpand, upgrading from previous releases to 5.3.13 could cause binlogs to be unusable.

  • In Xpand, INSERT...SELECT incorrectly overwrote a value when the destination column is AUTO_UNIQUE.

  • In Xpand, datetime or timestamp columns that used ON UPDATE NOW(6) were not updated correctly.

Can result in a hang or crash

  • In the Xpand Storage Engine, a JOIN or subselect on an empty table with columns defined as NOT NULL could cause the Xpand nodes to crash.

Can result in unexpected behavior

  • In Xpand, casting strings to ENUMs resulted in a compiler error.

  • In Xpand, intermittent issue could prevent successful installation due to "Relation not found" error.

  • In Xpand, an issue could prevent SHA256 password authentication from working properly.

  • In the Xpand Storage Engine, accessing Foreign Key metadata could sometimes take a very long time.

  • In the Xpand Storage Engine, queries that required evaluating multiple index scans could hit an out of memory error.

  • In the Xpand Storage Engine, some ALTER TABLE statements could run into an error due to incorrectly using an Xpand specific optimization.