Release Notes for MariaDB Enterprise Server 10.4.13-7

Overview

This seventh release of MariaDB Enterprise Server 10.4 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.4.13-7 was released on 2020-06-08.

Fixed Security Vulnerabilities

CVE (with cve.mitre.org link)

CVSS base score

CVE-2020-2814

4.9

CVE-2020-2812

4.9

CVE-2020-2760

5.5

CVE-2020-2752

5.3

CVE-2020-13249

MariaDB CVEs do not have a CVSS base score. This CVE is rated "medium" according to the definition in the engineering policy.

Notable Changes

  • MariaDB ColumnStore 1.4.4 is included in this release. Specific details on this component may be found in the ColumnStore 1.4.4 release notes.

  • mariadb-upgrade now displays a warning when upgrading a replica from MySQL Server to MariaDB Enterprise Server if data was present in the mysql.slave_master_info and mysql.slave_relay_log_info tables. A warning is needed as this information will be ignored. (MDEV-10047)

  • mariadb-dump has a new --ignore-table-data=<table> option. When used, the dump will include the table definition for the listed tables, but not the INSERT statements for the data in the table. (MDEV-22037)

  • mariabackup has a new --rollback-xa option. By default, mariabackup will not commit or rollback uncommitted XA transactions, and when the backup is restored any uncommitted XA transactions must be manually committed using XA COMMIT or be manually rolled-back using XA ROLLBACK. The --rollback-xa option can be used to rollback uncommitted XA transactions while performing a --prepare operation, eliminating the need for manual commit or rollback when the backup is restored. (MDEV-21168)

  • innodb_encryption_threads is now limited to 255. (MDEV-22258)

  • require_secure_transport system variable added, to enforce TLS secure connections. (MENT-66)

  • shutdown-wait-for-slaves system variable added, to control that a primary server only completes the shutdown after the last binary log has been sent to all connected slaves. This behavior is not active by default. Before the addition of this system variable, this was achieved using mariadb-admin shutdown --wait_for_all_slaves for a master. (MENT-202)

  • Index length limit for the Aria and S3 storage engines has been increased from 1000 to 2000 bytes. (MENT-401)

  • aria_pack tool now provides the options --datadir, --ignore-control-file, --require-control-file for Aria tables with auto-recovery enabled (TRANSACTION=1). (MENT-657)

  • IF EXISTS clause can now be used with RENAME TABLE and ALTER TABLE (MENT-725)

  • sql_if_exists system variable implicitly applies IF EXISTS clause to several DDL statements, including ALTER TABLE, ALTER VIEW, ALTER FUNCTION, DROP TABLE, DROP VIEW, DROP FUNCTION, DROP PACKAGE, and RENAME TABLE. (MENT-725)

  • S3 storage engine now provides support for replication. A new system parameter s3_slave_ignore_updates was added to define whether S3 replication is the same S3 storage for primary and replica. A new system parameter s3_replicate_alter_as_create_select controls whether all rows should be added to the binary log when a S3 table is altered to a local table. (MENT-725)

  • S3 storage engine now supports partitioning with the limitation that REBUILD PARTITION, TRUNCATE PARTITION, and REORGANIZE PARTITION cannot be used. (MENT-725)

  • System user mariadb.sys has been added. (MDEV-19650)

  • innodb_instant_alter_column_allowed system variable added to control whether an instant ADD or DROP column or reorder can change an InnoDB format. The default is add_drop_reorder to allow a format change for all types of ALTER . Option never should be used if a tablespace import to older versions of MariaDB Server should be possible. add_last should be used if a tablespace import into MariaDB Enterprise Server 10.3 or 10.4 should be possible. Instant ALTER resulting in reordering of columns will not be possible, but an instant ADD column as the last column can be done (behavior of MariaDB Enterprise Server 10.3). (MDEV-20590)

Issues Fixed

Can result in data loss

  • Possible crash with data loss when an executing an update of PRIMARY KEY columns on an InnoDB table with a BLOB column. (MDEV-22384)

Can result in crashes, hangs, stalls

Can result in unexpected behavior

Interface Changes

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.4.13-7 is provided for:

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 6

  • CentOS 8

  • CentOS 7

  • CentOS 6

  • Ubuntu 20.04

  • Ubuntu 18.04

  • Ubuntu 16.04

  • Debian 10

  • Debian 9

  • Debian 8

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 12

  • Microsoft Windows

Note

CentOS 6, Debian 8, and Red Hat Enterprise Linux 6 are no longer supported as per the MariaDB Engineering Policy. Older releases are available from the MariaDB Downloads page. Instructions for installation are included as a README file within the download.