Release Notes for MariaDB Enterprise Server 10.3.27-10

This tenth release of MariaDB Enterprise Server 10.3 is a maintenance release. This release includes security fixes.

MariaDB Enterprise Server 10.3.27-10 was released on 2020-12-14.

Fixed Security Vulnerabilities

CVE (with cve.org link)	CVSS base score
CVE-2020-14765	6.5
CVE-2020-14812	4.9
CVE-2020-14789	4.9
CVE-2020-14776	4.9
CVE-2020-28912	N/A (Critical)#1

#1: MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the MariaDB Engineering Policy for details.

Notable Changes

• Galera wsrep library updated to 25.3.31 in MariaDB Enterprise Cluster.

• In alignment with the MariaDB Engineering Policy, this release does not include CentOS 6.x and RHEL 6.x packages.

• The audit plugin (not MariaDB Enterprise Audit) did not log proxy users. The new plugin version 2.0.3 introduces an event sub-type PROXY_CONNECT for event type CONNECT (MDEV-19443)

  • On connect, if a proxy user is used, an extra line will be logged:

    1. TIME,HOSTNAME,user,localhost,ID,0,PROXY_CONNECT,test,plug_dest@%,0``

• Better MariaDB GTID support for the mariadb-backup --slave-info option. (MDEV-19264)

• New global InnoDB variable innodb_max_purge_lag_wait (MDEV-16952)

• The new parameter --include-unsupported for the script mariadb_es_repo_setup can be used to enable a repository of unsupported packages in the repository configuration. The repository currently includes the CONNECT Storage Engine. The storage engine can be installed by yum install MariaDB-connect-engine or apt-get install mariadb-plugin-connect-engine (MENT-1003)

• Back port of a MariaDB Server 10.5 feature to not acquire InnoDB record locks when covering table locks exist. (MENT-403)

• Change innodb_log_optimize_ddl=OFF by default. (MDEV-23720)

Issues Fixed

Can result in data loss

• Data corruption is possible for encrypted InnoDB tables if the non-default option innodb_background_scrub_data_uncompressed=ON is used. (MENT-910)

• Temporary tables created by the user or the system can overwrite existing files on creation. (MDEV-23569)

• Table can disappear after ALTER TABLE command if [[server-system-variables/#foreign_key_checks|SET FOREIGN_KEY_CHECKS=0]] is used before altering a child table to remove a primary key. (MDEV-22934)

Can result in a hang or crash

• InnoDB persistent stats analyze forces a full scan, which results in a lock crash. (MENT-1024)

• InnoDB hangs on INSERT with the error message Semaphore wait has lasted > 300 seconds. (MENT-1007)

• Server crash can happen on filesort with a setting for max_sort_length to a value lower than the default of 64 (MDEV-24033)

• Potential stack overflow in InnoDB fulltext search with a complex MATCH .. AGAINST string. (MDEV-23999)

• mariadb-backup can hang if the server goes idle after a particular kind of redo log write. (MDEV-23982)

• A server crash can occur when encryption is enabled for temporary tables (encrypt-tmp-files=ON), and queries use window functions. (MDEV-23867)

• A crash of MariaDB Server is possible when binary logging is activated, caused by improper raising of an error or replication checksum. (MDEV-23832)

• InnoDB assertion on TRUNCATE after ALTER TABLE .. DISCARD TABLESPACE (MDEV-23705)

• Server crashes after a failed attempt to create a unique key on a virtual column. (MDEV-23685)

• Possible server crash when using an index on a spatial data type with InnoDB. (MDEV-23600)

• Possible server crash when a string function is used for a column of type DATETIME and the string function is used in a subquery, which is returning a row. (MDEV-23535)

• MariaDB Enterprise Cluster node can crash on high INSERT, DELETE, or UPDATE load from many connections executed on the same table with foreign keys. (MDEV-23557)

• Server crashes if a query is executed on an InnoDB table with a foreign key where the foreign key was removed while using SET FOREIGN_KEY_CHECKS=0. This case should result in an SQL error. (MDEV-23470)

• Recursive procedure call ends with a crash instead of an SQL error. (MDEV-23463)

• InnoDB fails to open the table during removal of VIRTUAL column DDL while using SET FOREIGN_KEY_CHECKS=0, due to a lack of a referenced index. (MDEV-23387)

• Server crash when altering a table after its tablespace has been discarded already. (MDEV-22939)

• SHOW BINLOG EVENTS FROM ... caused a variety of non-determinism failures if the given position did not exist. (MDEV-22473)

• SET GLOBAL replicate_do_db = DEFAULT causes a crash. (MDEV-20744)

• JSON_MERGE_PATCH(json_doc, json_doc[, json_doc] ...) can crash if the first parameter is set to NULL and the second is not valid JSON. (MDEV-20593)

• Server crashes after DELETE with ON DELETE SET NULL for a foreign key and a virtual column in the index. (MDEV-20396)

• Server can crash on a prepared SELECT statement executed via MariaDB Connector/ODBC. (MDEV-19838)

• Crash on SELECT on a table that contains indexed virtual columns. (MDEV-18366)

• Possible server crash for queries using the window function NTH_VALUE() (MDEV-15180)

• Galera got stuck after FLUSH TABLES (MDEV-22707)

• Server crash can occur when SET GLOBAL replicate_do_table is used. (MDEV-23534)

• Possible crash when using Spider Tables and partitions. (MDEV-20100)

Can result in unexpected behavior

• Defining a view with SQL syntax ISNULL(ID) =0 incorrectly returns a syntax error. (MENT-1015)

• MariaDB Enterprise Backup reports an error that it cannot find an Aria log file './aria_log.00000000' (MENT-907)

• MariaDB Enterprise Backup failure for incremental backups. (MDEV-24026)

• Aborting a query on an InnoDB table with KILL QUERY does not show an SQL error message if the query could not be aborted. (MDEV-23938)

• Optimizer has chosen an inefficient plan, if a multi-component index, a second index, and a WHERE or ON clause with conditions over these indexes are used. (MDEV-23811)

• Some rounding has been done in an unexpected way for decimal numbers. (MDEV-23702)

• Server crashes after changing innodb_buffer_pool_size at runtime via a SET statement. (MDEV-23693)

• Creating a view removes parentheses on expressions from the SELECT, which results in wrong results. (MDEV-23656)

• mysql_tzinfo_to_sql under InnoDB is slow. (MDEV-23440)

• UDF cannot be uninstalled if the UDF library file doesn't exist. (MDEV-23327)

• CAST(expr AS type) with type DECIMAL can return an unexpected result if the given value for "expr" includes many leading zeros. (MDEV-23105)

• Galera replication is broken if only one timezone is loaded. (MDEV-22626)

• Galera SST donation fails, FLUSH TABLES WITH READ LOCK times out. (MDEV-22543)

• Memory leaks possible after ALTER TABLE with FOREIGN KEY (MDEV-22277)

• MariaDB Enterprise Backup SST fails for MariaDB Enterprise Cluster if the data-directory has a lost+found directory. (MDEV-21951)

• SHOW BINLOG EVENTS FROM ... caused a variety of non-determinism failures if the given position did not exist. (MDEV-21839)

• Linux AIO returned OS error 22 if parameters set to innodb_flush_method O_DIRECT and innodb_use_native_aio=1 (default). (MDEV-21584)

• CREATE OR REPLACE TRIGGER in Galera cluster not replicating, if a trigger with the same name already exists. (MDEV-21578)

• mysqld_multi no longer works with different server binaries. (MDEV-21526)

• Possible error for incremental backup --prepare for encrypted tablespaces. (MDEV-20755)

• Possible slow server starts and stops if full text indexes are used. (MDEV-18867)

• The parentheses in a VIEW can be defined incorrectly for a combination of = and BETWEEN (MDEV-17408)

• ER_BASE64_DECODE_ERROR upon replaying the binary log. (MDEV-16372)

• Several IPv6 issues with MariaDB Enterprise Cluster powered by Galera. (MDEV-21770, MDEV-23576, MDEV-23580, MDEV-23581, MDEV-23574)

• Subquery on information_schema fails with error message. (MENT-1016)

• AUTO_INCREMENT does not increment with a compound primary key on a partitioned table. (MENT-997)

• CREATE TEMPORARY TABLE .. LIKE (system-versioned table) returns an error if a unique index is defined in the table. (MDEV-23968)

• CREATE .. SELECT can result in an empty result on a join versioned table. (MDEV-23799)

• Error ERROR 4142 (HY000): SYSTEM_TIME partitions in table t1 do not support historical query upon querying a view, when that view is selecting from the versioned table with partitions. It only happens if the view itself was created using FOR SYSTEM_TIME ALL (MDEV-23779)

• Disk Space not reused for Blob in the data file. (MDEV-23072)

• mysqldump will not dump sequence definition details on --no-data dump. (MDEV-21786)

• CHECK TABLE fails to validate corruption on a table that was corrupted by a bug related to instant ADD or DROP (fixed in MariaDB Enterprise Server 10.3.17, 10.4.7). (MDEV-21251)

• Subquery execution is not terminated after LIMIT ROWS EXAMINED is exceeded. (MDEV-18335)

Related to install and upgrade

• mariadb_es_repo_setup curl failed on Ubuntu Focal if ca-certificates is not installed. Now it will prompt an error about missing ca-certificates (MENT-971)

Interface Changes

• innodb_log_optimize_ddl system variable default value changed from ON to OFF

• innodb_max_purge_lag_wait system variable was added

• mysqld --innodb-max-purge-lag-wait command-line option added

• performance_schema_digests_size

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.3.27-10 is provided for:

• Red Hat Enterprise Linux 7

• Red Hat Enterprise Linux 8

• CentOS 7

• CentOS 8

• Ubuntu 16.04

• Ubuntu 18.04

• Ubuntu 20.04

• Debian 9

• Debian 10

• SUSE Linux Enterprise Server 12

• SUSE Linux Enterprise Server 15

• Microsoft Windows

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

Note

In alignment with the MariaDB Engineering Policy, this release does not include CentOS 6.x and RHEL 6.x packages.

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