Release Notes for MariaDB Enterprise Server 10.4.19-12

This twelfth release of MariaDB Enterprise Server 10.4 is a maintenance release. This release includes a variety of fixes.

MariaDB Enterprise Server 10.4.19-12 was released on 2021-06-14.

Fixed Security Vulnerabilities

CVE (with cve.org link)	CVSS base score
CVE (with cve.org link)	CVSS base score
CVE-2021-2166	4.9
CVE-2021-2154	4.9

Notable Changes

• New function ST_DISTANCE_SPHERE() calculates the spherical distance between two geometries (point or multipoint) on a sphere. (MDEV-13467)

• Galera updated to 26.4.8

• Issue deprecation warnings for innodb_checksum_algorithm values none, innodb, strict_none, strict_innodb (MDEV-25106)

• MariaDB Enterprise Cluster avoids unnecessary rollbacks with streaming replication. (MDEV-25553)

• Improved TLS/SSL error reporting. (MDEV-21730)

Issues Fixed

Can result in data loss

• ALTER TABLE fails to rename a column in InnoDB table and causes server to crash. InnoDB table is not accessible after restart. (MDEV-24763)

• Table corruption ER_NO_SUCH_TABLE_IN_ENGINE or ER_CRASHED_ON_USAGE after ALTER on InnoDB table with foreign key. (MDEV-24532)

• MariaDB Enterprise Backup deletes the current source file after a No space left on device error, before exiting. Only the incomplete target file is still available. (MDEV-25221)

• Possible corruption in online ALTER TABLE for InnoDB with ROW_FORMAT=REDUNDANT (MDEV-24730)

• DELETE HISTORY may delete current data on system-versioned table. (MDEV-25468)

• Encrypted transactional Aria tables remain corrupt after crash recovery, automatic repair does not work. (MDEV-17913)

Can result in a hang or crash

• Possible hang when KILL CONNECTION or KILL QUERY is used with MariaDB Enterprise Cluster and a multi-master setup (MDEV-18874)

• Possible memory corruption with MariaDB Enterprise Cluster when inserting values bigger than 4096 bytes into variable-length fields (BLOB, TEXT, VARCHAR, and related types). (MDEV-24978)

• innodb_flush_method=O_DIRECT fails on compressed tables. (MDEV-25121)

• Server crashes in check_grant upon invoking function with userstat enabled. (MDEV-25242)

• MariaDB Client crashes when --default-character-set is set and --character-sets-dir is undefined. (MDEV-24879)

• 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)

• Possible server hang with InnoDB and indexed virtual columns after an error with UPDATE, INSERT, REPLACE on virtual columns. (MDEV-24786)

• MariaDB Enterprise Cluster conflict resolution issues. (MDEV-24923)

• Index count mismatch due to aborted FULLTEXT INDEX (MDEV-25200)

• MariaDB Enterprise Cluster node crashes when inserting a row into a table that contains a virtual column and does not have a primary key. (MDEV-25047)

• 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)

• EXISTS subquery with correlation in ON expression crashes. (MDEV-25407)

• 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)

• InnoDB startup hangs when a recovered transaction exists for the mysql.innodb_index_stats or mysql.innodb_table_stats system tables and a DDL transaction needs to be rolled back. (MDEV-25503)

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

• Server crashes on SHOW TABLES when a WHERE condition references a derived table. (MDEV-21603)

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

• After DROP INDEX or CREATE INDEX, change buffer entries for secondary indexes are lost on InnoDB restart. (MENT-1217)

• 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 a subquery that references a table value constructed with the VALUES() or VALUE() functions. (MDEV-24910)

• 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 the DEFAULT() function is called on a BLOB column. (MDEV-22703, MDEV-24958, MDEV-24942)

• Server crashes when a SELECT statement queries an Information Schema table and uses a JOIN (MDEV-24929)

• Server crash in optimize_schema_tables_memory_usage after SELECT from information_schema.innodb_sys_columns (MDEV-24868)

• 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)

• Crash with CREATE VIEW .. SELECT with non-existing field in ON condition. (MDEV-25206)

• Server crashes due to an assertion with multi-master workloads on MariaDB Enterprise Cluster when log_slave_updates is disabled and a conflicting transaction is aborted for a higher priority transaction. (MDEV-24954)

• Possible hang when KILL CONNECTION or KILL QUERY is used with MariaDB Enterprise Cluster and a multi-master setup. (MDEV-24967)

• Possible memory corruption when streaming replication is used for MariaDB Enterprise Cluster. (MDEV-24964)

• MariaDB Enterprise Cluster node crashes when the mysql.user system table is truncated. (MDEV-24865)

• MariaDB Enterprise Cluster node crashes when wsrep_provider_options set to NULL (MDEV-24856)

• Server crashes when a column is dropped from an InnoDB table with the INSTANT algorithm. (MDEV-25057)

• MariaDB Enterprise Cluster node crashes when CREATE TABLE t1 ( .. ) SELECT .. FROM t2 is executed where t1 is an InnoDB table and t2 is a non-InnoDB table. (MDEV-21697)

• MariaDB Enterprise Cluster node crashes when an uncommitted transaction is replicated using streaming replication while wsrep_on is enabled and the transaction is committed while wsrep_on is disabled. (MDEV-25226)

• Server crashes with MariaDB Enterprise Cluster when a non-InnoDB table is locked with the LOCK TABLE statement and a concurrent connections executes CREATE VIEW that references the same table. (MDEV-22227)

• Possible server crash after failing instant InnoDB ALTER on secondary indexes. (MDEV-25360)

• Server crashes in thd_clear_errors() (MDEV-23542)

• MariaDB Enterprise Backup crashes when called without parameters on Windows. (MDEV-24106)

• Server crashes during crash recovery when freed pages exist in the tablespace of an encrypted InnoDB table. Also affects [[mariadb-backup|MariaDB Enterprise Backup]] during --prepare (MDEV-24792)

• MariaDB Enterprise Cluster conflict resolution issues. (MDEV-25579, MDEV-24980, MDEV-25378)

Can result in unexpected behavior

• SUMcolumn from a derived table returns invalid values. ([MDEV-23291](https://jira.mariadb.org/browse/MDEV-23291))

• CAST('0e1111111111' AS DECIMAL(38,0)) returns an incorrect result. (MDEV-24790)

• Incorrect behavior of SET STATEMENT when it is executed as a prepared statement. (MDEV-24860)

• Query returns a ER_BAD_FIELD_ERROR error when a subquery contains a JOIN with an ON clause that references an outer column. (MDEV-25002)

• Query returns a ER_BAD_FIELD_ERROR error when a Common Table Expression (CTE) contains a UNION (MDEV-24597)

• Query returns wrong result when the 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)

• Duplicate key may be generated during MariaDB Enterprise Cluster configuration change. (MDEV-24853)

• State snapshot transfer (SST) for MariaDB Enterprise Cluster using [[mariadb-backup|MariaDB Enterprise Backup]] fails when the --log-bin option was set on the command-line with no value at server startup. (MDEV-24903)

• Race condition between persistent statistics and RENAME TABLE or TRUNCATE (MDEV-25051)

• Race condition between ANALYZE TABLE and STATS_AUTO_RECALC (MDEV-10682)

• Incorrect message about field length is written to the error log when CHECK TABLE is executed on an InnoDB table. (MDEV-24748)

• 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)

• Selectivity shown with EXPLAIN in field "filter" is incorrect for BIT columns. (MDEV-22583)

• Histogram statistics are used even with optimizer_use_condition_selectivity=3 (MDEV-19474)

• EXPLAIN shows nonsensical value for key_len with type=index (MDEV-11172)

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

• Wrong function name in error messages upon ST_GeomFromGeoJSON call. (MDEV-25272)

• [[mariadb-backup|MariaDB Enterprise Backup]] fails --prepare on large backup. (MDEV-24197)

• State snapshot transfer (SST) for MariaDB Enterprise Cluster using [[mariadb-backup|MariaDB Enterprise Backup]] fails when the password for the backup user is set via the MYSQL_PWD environment variable. (MDEV-25321)

• State snapshot transfer (SST) for MariaDB Enterprise Cluster using [[mariadb-backup|MariaDB Enterprise Backup]] fails when the --innodb option was set on the command-line at server startup. (MDEV-25328)

• An extra warning is returned when the EXPLAIN EXTENDED statement is executed in a prepared statement. (MDEV-25108)

• Complex query in stored procedure returns wrong results. (MDEV-25182)

• ALTER TABLE wrongly checks for field's default value if AFTER is used. (MDEV-25403)

• 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)

• [[mariadb-backup|MariaDB Enterprise Backup]] logs an error instead of a warning when it reads an invalid log block checksum during a --backup. (MDEV-25456)

• Rows are wrongly omitted when an InnoDB index is read using Multiversion Concurrency Control (MVCC). (MDEV-25459)

• SELECT aborts after failed REPLACE into table with virtual column. (MDEV-24583)

• InnoDB fails to fetch index type when index mismatch happens. (MDEV-22928)

• MariaDB Enterprise Cluster silently enables InnoDB 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. (MDEV-25319)

• RENAME TABLE causes "Ignoring data file ... with space ID xxxx, since the redo log references ... with space ID xxxx." for [[mariadb-backup|MariaDB Enterprise Backup]]. (MDEV-25568)

• 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)

• Dropping primary key column from a system-versioned table always fails with Error 1072 (MDEV-24690)

• ALTER TABLE .. ADD COLUMN .. AS ROW START returns misleading ER_VERS_DUPLICATE_ROW_START_END error. (MDEV-25172)

• Unexpected ER_DUP_ENTRY error when the Primary Key column is dropped from a system-versioned table. (MDEV-25327)

• slave_compressed_protocol doesn't work properly with semi-sync replication. (MDEV-24773)

• Sequence created by one connection remains invisible to another. (MDEV-24545)

• routine_definition in information_schema.routines loses tablename if it starts with an _ and is not backticked. (MDEV-25501)

• 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 INFORMATION_SCHEMA.OPTIMIZER_TRACE table is queried. (MDEV-24975)

• ALTER TABLE not replicated with MariaDB Enterprise Cluster. (MDEV-24956)

• The setting sql_safe_updates can result in unexpected warnings when using MariaDB Enterprise Cluster. (MDEV-21402)

• 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 Cluster FLUSH SSL command doesn't reload wsrep cert. (MENT-1089)

• State snapshot transfer (SST) for MariaDB Enterprise Cluster using mariadb-dump causes shutdown of donor node to fail. (MDEV-25423)

• 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)

Related to install and upgrade

• Missing libsepol dependency on SLES 12 and SLES 15. (MENT-1163)

• caching_sha2_password.so isn't included in Debian packages. (MDEV-24728)

Interface Changes

• mariadb-backup --innodb-force-recovery command-line option added

• mariadb_repo_setup --skip-check-installed command-line option added

• ST_DISTANCE_SPHERE function added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.4.19-12 is provided for:

• CentOS 7 (x86_64)

• Debian 10 (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)

• Rocky Linux 8 (x86_64, ARM64 Red Hat Enterprise Linux 8 packages)

• SUSE Linux Enterprise Server 12 (x86_64)

• SUSE Linux Enterprise Server 15 (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"..

Installation Instructions

• MariaDB Enterprise Server 10.4

• Enterprise Cluster Topology with MariaDB Enterprise Server 10.4

• Primary/Replica Topology with MariaDB Enterprise Server 10.4

• Enterprise Spider Sharded Topology with MariaDB Enterprise Server 10.4

• Enterprise Spider Federated Topology with MariaDB Enterprise Server 10.4

Upgrade Instructions

• Upgrade to MariaDB Enterprise Server 10.4

• Upgrade from MariaDB Community Server to MariaDB Enterprise Server 10.4

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}