The Ultimate Guide to High Availability with MariaDB

Release Notes for MariaDB Enterprise Server 10.5.10-7

This seventh release of MariaDB Enterprise Server 10.5 is a maintenance release. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.10-7 was released on 2021-06-14.

Fixed Security Vulnerabilities

CVE (with cve.org link)CVSS base score
CVE-2021-21664.9
CVE-2021-21544.9

Notable Changes

Issues Fixed

Can result in data loss

  • Encrypted transactional Aria tables remain corrupt after crash recovery, automatic repair does not work. (MDEV-17913)
  • InnoDB recovery can fail with
    [ERROR] InnoDB: Not applying INSERT_REUSE_REDUNDANT due to corruption if innodb_change_buffering is set to a different value than none (MENT-1208)
  • InnoDB can report
    [ERROR] InnoDB: Flagged corruption of `..` in table ... in CHECK TABLE; Wrong count if innodb_change_buffering is set to a different value than none (MENT-1218)

Can result in a hang or crash

  • Server crashes in check_grant upon invoking function with userstat enabled. (MDEV-25242)
  • Possible Server crash when dropping a table. Only seen when using a table space per table and if the tablespace size is increased at the time of the drop. (MDEV-20648)
  • Index count mismatch due to aborted FULLTEXT INDEX (MDEV-25200)
  • Server crashes when InnoDB fails to add a new index on a new virtual column and a concurrent connection executes a query that accesses the freed virtual column. (MDEV-24971)
  • Server crashes in row_undo_mod_clust_low upon rollback of read-only transaction. (MDEV-25457)
  • Server crashes on the second execution of a stored procedure when the stored procedure uses an invalid multi-table UPDATE statement to update a view. (MDEV-24823)
  • Server crashes when InnoDB tries to fetch data from table containing a FULLTEXT INDEX and the table's tablespace was discarded. (MDEV-25536)
  • Potential hang in InnoDB purge when virtual indexed columns exist. (MENT-1203)
  • Crash with nested table value constructors. (MDEV-22786)
  • Server crashes when an aggregate function is called on a table value constructed with the VALUES() or VALUE() functions. (MDEV-24919)
  • Server crashes when a SELECT statement has an IN() clause that references the UNION of two table values constructed with the VALUES() or VALUE() functions. (MDEV-24840)
  • Possible memory corruption or crash if a table definition is evicted from the cache during a transaction commit. (MDEV-24811)
  • Server crashes when a FULLTEXT INDEX is added to an InnoDB table and the tablespace for the table was previously discarded. (MDEV-25070)
  • Server crashes when the optimizer incorrectly removes a GROUP BY from a subquery, because the column is specified in both the SELECT list and the GROUP BY list. (MDEV-24925)
  • Server crashes when a SELECT statement has a subquery in the FROM clause that contains a GROUP BY clause and multiple indexes are used: one index is used to resolve the GROUP BY clause and another index is used for the LATERAL DERIVED optimization. (MDEV-23723)
  • Server crashes when a column is dropped from an InnoDB table with the INSTANT algorithm. (MDEV-25057)
  • Server crashes when an ALTER TABLE statement is executed, wsrep_osu_method is set to NBO, and sql_mode is set to the empty string (''). (MENT-1134)
  • Shutdown crash during innodb.innodb_buffer_pool_resize_temporary (MDEV-25483)
  • Server hangs on early shutdown if InnoDB needs to purge indexed virtual columns. (MENT-1206)

Can result in unexpected behavior

  • SUM column from a derived table returns invalid values. (MDEV-23291)
  • Query returns wrong result when the [[|MIN|MIN()]] or MAX() aggregate functions are used and the aggregated column is indexed. (MDEV-25112)
  • Wrong result (extra rows and wrong values) with incremental block nested loop hash. (MDEV-21104)
  • Query returns wrong results when a JOIN is evaluated using the Block Nested Loop Hash (BLNH) optimization with a compound index. (MDEV-24767)
  • Server fails to start using mysqld_multi with mysqld_safe options. (MDEV-21039)
  • No error is returned when the optimizer removes a redundant part of a subquery that contains an unknown table alias. For example, if the optimizer removes a redundant GROUP BY clause from an IN() subquery, unknown table aliases in the redundant part are ignored. (MDEV-23449)
  • SSL connection fails when server and client certs are signed by same CA. (MDEV-23740)
  • Complex query in stored procedure returns wrong results. (MDEV-25182)
  • Incorrect name resolution for subqueries in ON expressions. (MDEV-25362)
  • When FLUSH LOGS is executed, a race condition between InnoDB group commit and binary log rotation causes the old binary log file to become obsolete before the InnoDB group commit has been written to it. (MDEV-24526)
  • Rows are wrongly omitted when an InnoDB index is read using Multiversion Concurrency Control (MVCC). (MDEV-25459)
  • The Replication Heartbeat binary log event (Heartbeat_log_event) uses 4 bytes to store the log position within the current binary log file, so the log position overflows when the binary log file size exceeds 4 GB. (MDEV-16146)
  • InnoDB spatial indexes miss large geometry fields. (MENT-1205)
  • Table alias from previous statement interferes with later commands. (MENT-1200)
  • EXPLAIN statement does not show details about sub-queries when the primary table is a table value constructed with the VALUES() or VALUE() functions. (MDEV-24936)
  • JOIN of a materialized derived table returns wrong result when the split_materialized optimization is enabled. (MDEV-25128)
  • Uninitialized value upon CREATE .. SELECT ... VALUE and variety of resulting errors with different engines. (MDEV-24710)
  • Sequence created by one connection remains invisible to another. (MDEV-24545)
  • JOIN of a derived table using an aggregation function returns incorrect results. (MENT-1210)
  • The SET PASSWORD statement fails with ER_MUST_CHANGE_PASSWORD when the statement is executed in a prepared statement and the user's password is expired. (MDEV-25197)
  • MariaDB Enterprise Spider returns The connect info 'tab' for table is too long when creating a Spider Table. (MDEV-22265)
  • garbd has connection issues. (MENT-1168)
  • Galera startup log shows mysql.server_audit_filters data load error when enabling server audit log through configuration file. (MENT-1196)
  • Upgrade to 10.5.9 breaks root user ability to GRANT (MDEV-25030)
  • Missing libsepol dependency on SLES 12 and SLES 15. (MENT-1163)

Changes in Storage Engines

  • This release incorporates MariaDB ColumnStore storage engine version 5.6.1 (before 2021-06-30).
  • This release incorporates MariaDB ColumnStore storage engine version 5.6.2 (after 2021-06-30).

Interface Changes

  • mariadb-backup --innodb-force-recovery command-line option added
  • mariadb_repo_setup --skip-check-installed command-line option added

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.5.10-7 is provided for:

  • CentOS 7
  • CentOS 8
  • Debian 9
  • Debian 10
  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • SUSE Linux Enterprise Server 12
  • SUSE Linux Enterprise Server 15
  • Ubuntu 18.04
  • Ubuntu 20.04
  • Microsoft Windows

Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see MariaDB Corporation Engineering Policies".

Installation Instructions

Upgrade Instructions

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.
Back to Top