Release Notes for MariaDB Enterprise Server 10.5.10-7

Improved TLS/SSL error reporting. ()

New field LEVEL exists in table to differentiate between column-level and table-level CHECK constraints. ()

Remove useless counter ()

Possible corruption in online for with ()

may delete current data on . ()

Encrypted transactional tables remain corrupt after crash recovery, automatic repair does not work. ()

Killing server during may lose transaction. ()

recovery can fail with [ERROR] InnoDB: Not applying INSERT_REUSE_REDUNDANT due to corruption if is set to a different value than none (MENT-1208)

can report [ERROR] InnoDB: Flagged corruption of .. in table ... in CHECK TABLE; Wrong count if is set to a different value than none (MENT-1218)

crashes when is set and is undefined. ()

Possible Server crash when . Only seen when using a table space per table and if the tablespace size is increased at the time of the drop. ()

Possible server hang with and indexed virtual columns after an error with , , on virtual columns. ()

conflict resolution issues. ()

Index count mismatch due to aborted FULLTEXT INDEX ()

node crashes when inserting a row into a table that contains a virtual column and does not have a primary key. ()

Server crashes when fails to add a new index on a new virtual column and a concurrent connection executes a query that accesses the freed virtual column. ()

subquery with correlation in ON expression crashes. ()

Server crashes in row_undo_mod_clust_low upon rollback of read-only transaction. ()

Server crashes on the second execution of a stored procedure when the stored procedure uses an invalid multi-table statement to update a view. ()

startup hangs when a recovered transaction exists for the or system tables and a DDL transaction needs to be rolled back. ()

Server crashes when tries to fetch data from table containing a FULLTEXT INDEX and the table's tablespace was discarded. ()

Server crashes on when a WHERE condition references a derived table. ()

Potential hang in purge when virtual indexed columns exist. (MENT-1203)

Crash with nested table value constructors. ()

Server crashes when an aggregate function is called on a table value constructed with the or functions. ()

Server crashes when a statement has a subquery that references a table value constructed with the or functions. ()

Server crashes when a statement has an IN() clause that references the UNION of two table values constructed with the or functions. ()

Possible memory corruption or crash if a table definition is evicted from the cache during a transaction commit. ()

Server crashes when the function is called on a column. (, , )

Server crashes when a statement queries an table and uses a JOIN ()

Server crashes in optimize_schema_tables_memory_usage after from ()

Server crashes when a FULLTEXT INDEX is added to an table and the tablespace for the table was previously discarded. ()

Server crashes when the optimizer incorrectly removes a GROUP BY from a subquery, because the column is specified in both the list and the GROUP BY list. ()

Server crashes when a 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. ()

Crash with with non-existing field in ON condition. ()

Server crashes due to an assertion with multi-master workloads on when is disabled and a conflicting transaction is aborted for a higher priority transaction. ()

Possible hang when or is used with and a multi-master setup. ()

Possible memory corruption when streaming replication is used for . ()

node crashes when the system table is truncated. ()

node crashes when set to NULL ()

Server crashes when a column is dropped from an table with the INSTANT algorithm. ()

node crashes when CREATE TABLE t1 ( .. ) SELECT .. FROM t2 is executed where t1 is an table and t2 is a non-InnoDB table. ()

node crashes when an uncommitted transaction is replicated using streaming replication while is enabled and the transaction is committed while is disabled. ()

Server crashes with when a non-InnoDB table is locked with the statement and a concurrent connections executes that references the same table. ()

Possible server crash after failing instant on secondary indexes. ()

Server crash in thd_clear_errors() ()

crashes when called without parameters on Windows. ()

Server crashes when an statement is executed, is set to NBO, and sql_mode is set to the empty string (''). (MENT-1134)

can crash when total order isolation (TOI) is used for Galera and is executed with ENGINE= using an unknown engine. Only happens with (no engine substitution). ()

crashes during . ()

Server crashes when , , or is executed on an table and is set to a value other than none ()

Server hangs during checkpoint when is executed. ()

conflict resolution issues. (, , )

Shutdown crash during innodb.innodb_buffer_pool_resize_temporary ()

crashes after with multiple tables. Only seen if (MENT-1144)

Server hangs on early shutdown if InnoDB needs to purge indexed virtual columns. (MENT-1206)

Query returns a error when a Common Table Expression (CTE) contains a UNION ()

Query returns wrong result when the [[|MIN|MIN()]] or aggregate functions are used and the aggregated column is indexed. ()

Wrong result (extra rows and wrong values) with incremental block nested loop hash. ()

Query returns wrong results when a JOIN is evaluated using the Block Nested Loop Hash (BLNH) optimization with a compound index. ()

Server fails to start using mysqld_multi with mysqld_safe options. ()

Duplicate key may be generated during configuration change. ()

State snapshot transfer (SST) for using fails when the option was set on the command-line with no value at server startup. ()

Race condition between persistent statistics and or [-TRUNCATE|TRUNCATE]] ()

Race condition between and STATS_AUTO_RECALC ()

Incorrect message about field length is written to the when is executed on an table. ()

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 subquery, unknown table aliases in the redundant part are ignored. ()

Selectivity shown with in field "filter" is incorrect for columns. ()

Histogram statistics are used even with =3 ()

shows nonsensical value for key_len with type=index ()

SSL connection fails when server and client certs are signed by same CA. ()

Wrong function name in error messages upon call. ()

fails --prepare on large backup. ()

State snapshot transfer (SST) for using fails when the password for the backup user is set via the MYSQL_PWD environment variable. ()

State snapshot transfer (SST) for using fails when the option was set on the command-line at server startup. ()

An extra warning is returned when the statement is executed in a prepared statement. ()

Complex query in stored procedure returns wrong results. ()

wrongly checks for field's default value if AFTER is used. ()

Incorrect name resolution for subqueries in ON expressions. ()

When is executed, a race condition between 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. ()

logs an error instead of a warning when it reads an invalid log block checksum during a . ()

Rows are wrongly omitted when an index is read using Multiversion Concurrency Control (MVCC). ()

aborts after failed into table with virtual column. ()

fails to fetch index type when index mismatch happens. ()

silently enables Monitor output and never disables it when a wsrep slave thread tries to perform a brute-force (BF) kill, but fails due to a long lock wait. ()

causes "Ignoring data file ... with space ID xxxx, since the redo log references ... with space ID xxxx." for . ()

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. ()

spatial indexes miss large geometry fields. (MENT-1205)

Table alias from previous statement interferes with later commands. (MENT-1200)

statement does not show details about sub-queries when the primary table is a table value constructed with the or functions. ()

JOIN of a materialized derived table returns wrong result when the split_materialized optimization is enabled. ()

Uninitialized value upon CREATE .. SELECT ... VALUE and variety of resulting errors with different engines. ()

Dropping primary key column from a always fails with ()

[ALTER TABLE](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/data-definition/alter/alter-table) .. ADD COLUMN .. AS ROW START returns misleading error. ()

Unexpected error when the Primary Key column is dropped from a . ()

doesn't work properly with semi-sync replication. ()

Sequence created by one connection remains invisible to another. ()

routine_definition in loses tablename if it starts with an _ and is not backticked. ()

JOIN of a derived table using an aggregation function returns incorrect results. (MENT-1210)

Server temporarily consumes extra 4 GB of memory every time the table is queried. ()

not replicated with . ()

The setting can result in unexpected warnings when using . ()

The statement fails with ER_MUST_CHANGE_PASSWORD when the statement is executed in a prepared statement and the user's password is expired. ()

FLUSH SSL command doesn't reload wsrep cert. (MENT-1089)

State snapshot transfer (SST) for using mariadb-dump causes shutdown of donor node to fail. ()

MariaDB Enterprise Spider returns The connect info 'tab' for table is too long when creating a Spider Table. ()

garbd has connection issues. (MENT-1168)

startup log shows mysql.server_audit_filters data load error when enabling server audit log through configuration file. (MENT-1196)

[ALTER TABLE](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/data-definition/alter/alter-table) .. IMPORT TABLESPACE fails after DROP INDEX ()

Upgrade to 10.5.9 breaks root user ability to GRANT ()

shows 0 for I/O statistics that were previously removed. ()

adaptive flushing fails to start when is exceeded. ()

Replica server fails with when DROP TABLE parent_table, child_table is executed on the primary server and is enabled. ()

Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

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 20.04 (x86_64, ARM64)