Release Notes for MariaDB Enterprise Server 10.5.25-19

MariaDB Enterprise Server 10.5.25-19 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.25-19 was released on 2024-06-11.

Fixed Security Vulnerabilities

Notable Changes

• Galera has been updated to 26.4.18

  • The GCS protocol version has been changed, preventing a downgrade of individual nodes of a MariaDB Enterprise Cluster

Changes in Storage Engines

This release incorporates MariaDB ColumnStore engine version 5.6.8.

Issues Fixed

Can result in data loss

• With --gtid-ignore-duplicate set a transaction can be double-applied from another replication source if at applying the transaction from the initial source required retrying in parallel execution. ()

• Backups of server with innodb_encrypt_tables=1 can become corrupted in mariadb-backup --prepare ()

• The TIMESTAMP value of '1970-01-01 00:00:00'

Can result in hang or crash

• Using current MariaDB Enterprise Backup against an older server can result in a crash, as the system variable @@aria_log_dir_path does not exist ()

• When using a non-default setting for "innodb_change_buffering", the server can crash ()

• When a fulltext search query with more than 4G inserted or updated rows is executed, the server can crash ()

• Assertion when user commits an empty transaction for DDL that was killed during certification: ()

• Graceful node shutdown can crash garbd and MariaDB Enterprise Cluster can go non-primary when SSL is used ()

Can result in unexpected behavior

• Wrong result sets are returned by the second execution of prepared statements from selects using mergeable derived tables pushed into external engine ()

• A query that uses a derived table that employs constructs with side-effects, like (SELECT @var:=... ) as derived_tbl, could produce wrong results ()

• ORDER BY COLLATE improperly applied to non-character columns which is resulting in an unordered result set ()

• CREATE TEMPORARY TABLE (without SELECT), INSERT ... SELECT, and CREATE ... LIKE are not affected by this bug

• A view created via JSON_ARRAYAGG returns an incorrect JSON object ()

• Mariadb-dump trusts the server and does not validate the data. A modified dump file can include system commands used by the mariadb-client. Dumps are now loaded in the sandbox mode by default, a system call will result in an error ()

• A wrong result on 2-nd execution of a prepared statement is possible when selecting from a view using a merged derived table ()

• Original IP not shown in network related error messages when proxy_protocol is in use ()

• Incorrect DEFAULT expression evaluated in UPDATE ()

Related to performance

• Table is getting rebuild with ALTER TABLE ADD COLUMN although it should be an instant operation not requiring a rebuild ()

• Aggregation functions fail to leverage uniqueness property ()

  • Generally, computing aggregate function with DISTINCT argument: aggregate_func(DISTINCT col1, col2, ...) requires producing a de-duplicated set of its arguments, which can be CPU-intensive

then the arguments are guaranteed not to have duplicates. Such cases are now detected allowing the optimizer to skip de-duplication.

Changelog

For the complete list of changes in this release, see the .

Platforms

• In alignment with the , MariaDB Enterprise Server 10.5.26-20 is provided for:

  • AlmaLinux 8 (x86_64, ARM64)

  • AlmaLinux 9 (x86_64, ARM64)

  • Debian 11 (x86_64, ARM64)

Installation Instructions

Upgrade Instructions