Release Notes for MariaDB Enterprise Server 10.5.18-13
MariaDB Enterprise Server 10.5.18-13 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.5, released on 2022-12-21
MariaDB Enterprise Server 10.5.18-13 is a maintenance release of MariaDB Enterprise Server 10.5. This release includes a variety of fixes.
MariaDB Enterprise Server 10.5.18-13 was released on 2022-12-21.
Backported Features
MariaDB Enterprise Server enables a predictable development and operations experience through an enterprise lifecycle. These new features have been backported after reaching maturity in MariaDB Community Server:
The new is available to set the maximum execution time for queries on replica nodes. (MENT-1566, )
When a query takes more than slave_max_statement_time seconds to run on the replica (slave) node, the query is aborted, and replication stops with an error.
The system variable can be set to a decimal value, where the decimal component has microsecond precision.
Notable Changes
The view shows details about the InnoDB temporary tablespace, which is the tablespace where InnoDB temporary tables are stored. ()
Starting with this release, the details about the InnoDB temporary tablespace can be shown by querying for the name innodb_temporary:
When a table's default collation is set to the default collation for the table's character set, shows the COLLATE clause. ()
In previous releases, MariaDB Enterprise Server reduced the size of SHOW CREATE TABLE output by excluding the COLLATE clause if the table's default collation was set to the default collation for the table's character set.
Issues Fixed
Can result in data loss
When a column is renamed in a partitioned table with using the , the table can be corrupted. ()
When the InnoDB storage engine performs change buffer operations, the can overflow, which can cause table corruption. (MENT-1661, )
Can result in a hang or crash
When a query contains an IN/ALL/ANY predicand and the subquery contains a GROUP BY clause with an IN/ALL/ANY predicand with a single-value subquery as the left operand, the server can crash. ()
If an InnoDB table contains a foreign key constraint and the child table's DATABASE_NAME/TABLE_NAME.ibd is longer than 330 characters, when the parent table is renamed, the server can crash. ()
When the Spider storage engine's ODBC foreign data wrapper is used with MariaDB Connector/ODBC 3.1.10 and later, the server can crash. (MENT-1415)
If the InnoDB change buffer is corrupted, the server can hang during shutdown. (MENT-1673, )
When an InnoDB tablespace is in the non-canonical format from a previous operation that used the , InnoDB can fail to apply changes to the table during crash recovery and while preparing a backup with . ()
When a prepared statement is used to execute an containing a subquery, the server can crash: ()
Can result in unexpected behavior
In the presence of replication filters, revoking privileges from a non-existing user on a primary (master) breaks replication on the replica (slave). ()
When is set on a replica node, the replica node does not skip replicated statements. ()
When a Spider table has a prefix index, query results can be incorrect. ()
When an InnoDB table contains virtual generated columns that are indexed, InnoDB fails to purge secondary index records. ()
When using the InnoDB adaptive hash index, non-locking reads can return wrong results due to a potential ACID violation. (, , )
When is used on a temporary table, an empty result set is returned. ()
When a tablespace file was originally built with MariaDB Enterprise Server 10.4 and earlier, InnoDB would refuse to add a column to the table using the . ()
In previous releases, the operation would fail with the following error message:
Related to install and upgrade
When is executed, spurious errors about table rebuilds are logged. ()
In previous releases, the following messages would be logged, even though the tool already mitigated the issues itself:
Changes in Storage Engines
This release incorporates MariaDB ColumnStore storage engine version 5.6.8.
Interface Changes
error code added
error code added
error code added
Platforms
In alignment with the , MariaDB Enterprise Server 10.5.18-13 is provided for:
AlmaLinux 8 (x86_64, ARM64)
AlmaLinux 9 (x86_64, ARM64)
Debian 11 (x86_64, ARM64)
Debian 12 (x86_64, ARM64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".
When renaming a table to a long name, the server can crash. (MDEV-29258)
When an causes InnoDB to rebuild a table with a spatial index, the server can crash. (MDEV-29520)
When an InnoDB temporary table contains a spatial index, the server can crash if the temporary table is dropped due to DROP TEMPORARY TABLE or client disconnect. (MDEV-29507)
When querying a partitioned table using the PARTITION syntax, if the WHERE clause results in an index merge, the server can crash. (MDEV-21134)
When detecting CTE dependencies of nested CTEs that includes one or more recursive CTEs, infinite recursion can occur until the server crashes. (MDEV-29361)
When the is configured to use the bundled wsrep_notify.sh script, the server can hang during startup. (MDEV-27682)
When selecting from InnoDB's (such as , , and ), if connections with open XA transactions are disconnected or killed at the same time, the server can crash. (MDEV-29575)
For some queries that involve tables with different but convertible character sets for columns taking part in the query, a repeatable execution of such queries in the prepared statement mode or as part of a stored routine can crash the server. (MDEV-16128)
When executing a SELECT .. UNION .. SELECT or EXPLAIN EXTENDED statement, the server can crash. (MDEV-23160)
When is set and a view that includes a subquery is queried, the server crashes. (MDEV-16549)
When an application-time period with an empty name is added to a table using , the server can crash. (MDEV-18873)
In previous releases, statements like the following could cause the server to crash:
When InnoDB tries to apply a INSERT_HEAP_DYNAMICrecord to a secondary index in a table with ROW_FORMAT=DYNAMIC during crash recovery, the operation can fail with an error. (MDEV-29559)
In previous releases, the could have errors like the following:
InnoDB can extend tablespace files when additional capacity is not required. (MDEV-13013)
When an InnoDB table is being rebuilt and a is updated during the online rebuild, a memory leak can occur. (MDEV-29600)
In previous releases, the following error would occur:
When a sequence is used as the default value in a table, rows inserted by an INSERT ... SELECT statement can be assigned the wrong values. (MDEV-29540)
When a column has both a and a , full-text search using MATCH(..) AGAINST(..) does not work properly. (MDEV-29778)
If the server is started with the enabled, but the TLS certificates and keys are not configured, the server will advertise the TLS support in the handshake, but will not actually be able to use it. (MDEV-29811)
With MariaDB Enterprise Cluster, when is configured, the joiner node ignores custom values for the innodb_buffer_pool_filename system variable, and the SST copies the buffer pool file to the default location instead. (MDEV-28968)
When a is filtered in a subquery inside the , the results can be incorrect. (MDEV-27101)
When the does not contain a port number, the shows 0 as the port number. (MDEV-28868)
When is enabled, performance is impacted if the rowid filter contains no elements. (MDEV-28846)
When a column is filtered in a subquery inside the , the results can be incorrect. (MDEV-27099)
When XA COMMIT is executed without an open XA transaction, the operation is still logged to the binary log. (MDEV-25616)
In previous releases, when a replica node tried to apply the event, it would fail with the ER_XAER_NOTA error code: