Release Notes for MariaDB Enterprise Server 10.5.19-14


MariaDB Enterprise Server 10.5.19-14 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.

MariaDB Enterprise Server 10.5.19-14 was released on 2023-03-13.

Notable Changes

  • Output for the JSON_DETAILED() function has been optimized to reduce the number of lines needed. (MDEV-19160)

  • This release incorporates Galera library version 26.4.14

Issues Fixed

Can result in data loss

  • When executing a DELETE or UPDATE with a subselect, the server can crash. (MDEV-10087)

  • When performing an incremental backup, MariaDB Enterprise Backup does not reflect databases that have been dropped and created. (MDEV-23335)

  • innodb_undo_log_truncate=ON is not crash safe. This also can have effects for MariaDB Enterprise Backup for backup and restore. (MDEV-29999) (MDEV-30179) (MDEV-30438)

    • When innodb_undo_log_truncate=ON a backup for MariaDB Enterprise Server can return the error message:

      FATAL ERROR: ... failed to copy datafile.

Can result in a hang or crash

  • When DELETE HISTORY is executed for a system versioned table with full text index, the server can crash. (MDEV-25004)

  • When an ALTER TABLE statement causes InnoDB to rebuild a table with a spatial index, the server can crash. (MDEV-29856)

  • When using SPIDER with SPIDER_DIRECT_SQL and spider_udf_ds_use_real_table=1, the server can crash. (MDEV-29855)

  • When executing REPLACE INTO ... PARTITION(...), the server can crash. (MDEV-29636)

  • Galera SST doesn't properly handle undo* files from InnoDB. As a result, SST may terminate incorrectly when --innodb-undo-tablespaces is set to 3 or more. (MDEV-30157)

  • With a query containing nested WINDOW clauses, the server can crash. (MDEV-30052)

  • When executing a SELECT from complex a view with WHERE clause and with the setting derived_merge=on, the server can crash. (MDEV-30081)

  • Infinite sequence of recursive calls when processing embedded CTE, when such a reference has the same table name as the name of the CTE. (MDEV-30248)

  • When the query cache is enabled and a DROP DATABASE is called, the DROP DATABASE can hang and 100 percent CPU load can be seen. (MDEV-29760)

  • The execution of FLUSH TABLES .. FOR EXPORT can result in a server crash. (MDEV-30227)

  • When querying a Spider Table from a stored procedure inside a WHILE clause, the server can crash. The stored procedure needs to use two WHILE clauses which both query the Spider Table. (MDEV-30191)

  • Deadlock on Replica during BACKUP STAGE BLOCK_COMMIT on XA transactions. (MDEV-30423)

  • MariaDB Server can crash during recovery if an ALTER TABLE .. ROW_FORMAT=COMPRESSED has been executed before. (MDEV-30404)

  • With a cluster wide conflict, MariaDB Enterprise Cluster can hang if a binlog purging is running (such as in the case that binlog expiration is configured). (MDEV-29512)

  • mariadbd hangs when running with --wsrep-recover and options. (MDEV-30370)

  • A deadlock between InnoDB statistics updates and BLOB insert can result in a server hang. (MDEV-29883)

Can result in unexpected behavior

  • log_query_not_using_indexes=OFF is ignored when log_slow_filter is an empty string. (MDEV-21187)

  • MariaDB Enterprise Backup returns with an error when the option --galera-info is used for creating a backup of a MariaDB Server instance, which is not a MariaDB Enterprise Cluster node. Failed to get master wsrep state from SHOW STATUS (MDEV-30293)

  • When querying a table with virtual generated columns using full text search, these columns are not generated and are always NULL in the result set. (MDEV-29169)

  • Identifiers are not quoted for the output of SHOW GRANTS. Using the result to execute the grant statement results in a syntax error, if reserved keywords are used. (MDEV-30056)

  • Spider table with CHARSET utf32/utf16/ucs2 tries to set client CHARSET to unsupported value. (MDEV-29562)

  • Incorrect results are returned when using STDDEV_SAMP() with a view. (MDEV-19071)

  • A spurious error can be generated: ERROR 1292 (22007) at the line 15: Truncated incorrect DECIMAL value:# (MDEV-30342)

  • When running mariadb-binlog using the option --verbose, cannot read row events with compressed columns: Error: Don't know how to handle column type:... (MDEV-25277)

  • Incorrect results are returned with outer join, merged derived table, and view. (MDEV-28602)

  • Some DDL, such as ANALYZE, can be completed out of order on parallel replicas. (MDEV-30323)

  • Seconds_Behind_Master is incorrect for delayed parallel replicas. (MDEV-29639)

  • Calling DETERMINISTIC package functions from other SQL/PL stored routines can be slow. (MDEV-29370)

  • An upgrade to MariaDB Server 10.5 and MariaDB 10.6 incorrectly reports that a recovery is needed. (MDEV-24412)

  • Warning message when encryption is not available on recovery: InnoDB: We do not continue the crash recovery, because the table may become corrupt (MDEV-30068)

  • With MariaDB Enterprise Backup on Windows, an incremental prepare fails when innodb_undo_tablespaces > 0 is set. (MDEV-30144)

  • Changing the value of wsrep_gtid_domain_id for MariaDB Enterprise Cluster with full cluster restart can fail on nodes, which do not sync from the node where wsrep_gtid_domain_id was changed. (MDEV-29171)

  • Full backup is failing during the Aria log file copy process. An error like error: cannot open file ./aria_log.00000002 can be found in the log file. The file aria-log.00000002 might not exist, but one with a higher number might. (MENT-1587)

  • Long uniques don't work correctly with Unicode collations. Equal strings (in terms of the collation) are compared as unequal if the length of the strings are different. (MDEV-27653)

Interface Changes


In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.5.19-14 is provided for:

  • CentOS 7 (x86_64)

  • Debian 10 (x86_64, ARM64)

  • Debian 11 (x86_64, ARM64)

  • Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Red Hat Enterprise Linux 9 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • Rocky Linux 9 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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