The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2025-03-12. For the latest, interactive version please visit https://mariadb.com/kb/.

Release Notes for MariaDB Enterprise Server 10.4.17-10

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

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

Fixed Security Vulnerabilities

CVE (with cve.org link)CVSS base score
CVE-2020-147656.5
CVE-2020-148124.9
CVE-2020-147894.9
CVE-2020-147764.9
CVE-2020-28912N/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

  • 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:
      TIME,HOSTNAME,user,localhost,ID,0,PROXY_CONNECT,test,plug_dest@%,0
  • 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)

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

  • On connect, if a proxy user is used, an extra line will be logged:
    TIME,HOSTNAME,user,localhost,ID,0,PROXY_CONNECT,test,plug_dest@%,0
  • The event type can also be used in filters "connect_event": ["CONNECT","DISCONNECT","PROXY_CONNECT"]
  • Performance improvements for comparisons of temporal data types with temporal literals. (MDEV-23551)
  • Performance improvements for comparisons of temporal data types. (MDEV-23537)

Issues Fixed

Can result in data loss

  • Temporary tables created by the user or the system can overwrite existing files on creation. (MDEV-23569)
  • Server crashes on an instant ALTER TABLE .. MODIFY of a column from "not null" to "null". A virtual column must exist in the table. (MDEV-23672)
  • DELETE .. FOR PORTION OF statement accepts non-constant FROM .. TO clause. This contradicts the documentation and is inconsistent with the behavior of the UPDATE statement. (MDEV-22596)

Can result in a hang or crash

  • InnoDB persistent stats analyze forces full scan which results in a lock crash. (MENT-1024)
  • InnoDB hang on INSERT with error message Semaphore wait has lasted > 300 seconds. (MENT-1007)
  • Potential stack overflow in InnoDB fulltext search with a complex MATCH .. AGAINST string. (MDEV-23999)
  • Mariabackup can hang if the server goes idle after a particular kind of redo log write. (MDEV-23982)
  • A crash of MariaDB Server is possible when binary logging is activated, caused by improper raising of an error or replication checksum. (MDEV-23832)
  • Server crashes after failed attempt to create unique key on 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)
  • Server crashes if a query is executed on an InnoDB table with a foreign key where the foreign key was removed while using FOREIGN_KEY_CHECKS=0. This case should result in an SQL error. (MDEV-23470)
  • Recursive procedure call ends with a crash instead of SQL error. (MDEV-23463)
  • Server crash when altering a table after its tablespace has been discarded already. (MDEV-22939)
  • 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 foreign key and a virtual column in index. (MDEV-20396)
  • Possible crash when using Spider Tables and partitions. (MDEV-20100)
  • MariaDB Enterprise Cluster node crash with Galera message
    Assertion `server_state_.rollback_mode() == wsrep::server_state::rm_async' failed. in the error log. (MENT-937)
  • Galera node crashes or hangs during IST if the connection between donor and joiner is unstable or if cluster configuration changes take place at the same time. (MENT-514)
  • Possible server crash with SELECT executed on a system versioned table, if variable system_versioning_asof was set to a value of type DATE instead of DATETIME. (MDEV-23562)
  • Server crash when SELECT WSREP_LAST_SEEN_GTID() while Galera replication is not enabled (wsrep-on=OFF). (MDEV-23466)
  • Server crash if function FORMAT(num, decimal_position[, locale]) is used with a decimal_position > 30. (MDEV-23415)
  • Multiple calls to a Stored Procedure from another Stored Procedure crashes server. (MDEV-23094)
  • Server hang if TABLE LOCK is used after BACKUP LOCK was used. (MDEV-22879)
  • Server crash on table updates using FOR PORTION OF (MDEV-22805)
  • Server crash if a transaction is started with SET SESSION wsrep_on=1, but the global wsrep_on is 0 (MDEV-22443)

Can result in unexpected behavior

  • Defining a view with SQL syntax ISNULL(ID)=0 incorrectly returns a syntax error. (MENT-1015)
  • 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)
  • Creating a view removes parentheses on expressions from the SELECT, which results in wrong results. (MDEV-23656)
  • UDF cannot be uninstalled if the UDF library file doesn't exist. (MDEV-23327)
  • 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 slow server start and stop 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 binary log. (MDEV-16372)
  • A AUTO_INCREMENT does not increment with compound primary key on partitioned table. (MENT-997)
  • CREATE .. SELECT can result in empty result on join versioned table. (MDEV-23799)
  • Error
    ERROR 4142 (HY000): SYSTEM_TIME partitions in table `t1` does 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 data file. (MDEV-23072)
  • 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 not terminated after LIMIT ROWS EXAMINED is exceeded. (MDEV-18335)
  • Deadlock between BACKUP STAGE BLOCK_COMMIT and parallel replication. (MDEV-23586)
  • Possible memory leak in galera library. (MDEV-23559)
  • Wrong result of MIN(time_expr) and MAX(time_expr) with GROUP BY (MDEV-23525)
  • FORMAT(num, decimal_position[, locale]) where decimal position is 0 or 38 and num is DECIMAL(38,38) returns incorrect results. (MDEV-23118)
  • A query result includes a data row twice depending on the WHERE clause used, if partitioning is used. (MDEV-22246)
  • 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

Platforms

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

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • CentOS 7
  • CentOS 8
  • Debian 9
  • Debian 10
  • SUSE Linux Enterprise Server 12
  • SUSE Linux Enterprise Server 15
  • Ubuntu 16.04
  • Ubuntu 18.04
  • Ubuntu 20.04
  • 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.

Installation Instructions

Upgrade Instructions

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.