Release Notes for MariaDB Enterprise Server 10.3.23-7
This page is part of MariaDB's Documentation.
The parent of this page is: Release Notes for MariaDB Enterprise Server 10.3
Topics on this page:
Overview
This seventh release of MariaDB Enterprise Server 10.3 is a maintenance release, including a variety of fixes.
MariaDB Enterprise Server 10.3.23-7 was released on 2020-06-08.
Fixed Security Vulnerabilities
CVE (with cve.org link) | CVSS base score |
5.5 | |
5.3 | |
4.9 | |
4.9 | |
N/A (Medium)#1 |
- #1:
MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the MariaDB Engineering Policy for details.
Notable Changes
mysql_
upgrade now displays a warning when upgrading a replica from MySQL Server to MariaDB Enterprise Server if data was present in themysql.slave_master_info
andmysql.slave_relay_log_info
tables. A warning is needed as this information will be ignored. (MDEV-10047)mysqldump 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_ is now limited to 255. (MDEV-22258)thread 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
mysqladmin shutdown --wait_for_all_slaves
for a master. (MENT-202)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)innodb_
instant_ system variable added to control whether an instantalter_ column_ allowed ADD
orDROP
column or reorder can change an InnoDB format. The default isadd_last
to allow an instantADD COLUMN
as the last column of the table. Optionnever
should be used if a tablespace import to older version of MariaDB Server should be possible. (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 a hang or crash
MariaDB Enterprise Backup ignored the timeout setting --ftwrl-wait-timeout when an explicit
LOCK TABLES ... WRITE
was active in another session. As a result, MariaDB Enterprise Server waited for release of the lock even if the timeout was reached. (MDEV-20230)When additional
open_table_caches_instances
have been created, a crash could occur due to exceeding the limit of open file descriptors. (MDEV-18027)Clean shutdown of MariaDB Enterprise Cluster was not possible due to a deadlock situation between Galera Nodes. (MENT-432)
Adding a column to discarded InnoDB tablespace was possible, resulting in a crash. (MDEV-22446)
Can result in unexpected behavior
Replication could be aborted when the replication data includes nested version-based conditional comments.
mysqld and
mysqld_safe
processes showed as running after a server shutdown. (MDEV-21563)MariaDB Enterprise Backup ignored the ignore_
db_ configuration from the server configuration file. (MDEV-19347)dirs A duplicate key error showed the duplicate key value truncated to 64 characters without indicating the truncation. (MDEV-20604)
Using
SET GLOBAL
for the InnoDB variables innodb_ft_ , innodb_aux_ table ft_ , innodb_server_ stopword_ table ft_ , and innodb_user_ stopword_ table buffer_ could lead to corrupted strings for the settings. (MDEV-22393)pool_ filename Changing the
Server-Id
could lead to events being disabled for replicas, even if a single node configuration without a replica was used. (MDEV-21758)SHOW PRIVILEGES incorrectly shows the privilege
Delete versioning rows
instead ofDelete history
(MDEV-20382)Wrong query results have been returned with optimizer_
switch="split_ (MDEV-21614)materialized=on" SHOW GRANTS does not quote role names properly for a user granted to this role. (MDEV-20076)
Partitioning could choose a wrong partition for
RANGE
partitioning by DECIMAL column. (MDEV-21195)
Related to installation or upgrade
The plugin
pam_user_map.so
was not provided with binary tarball packages. (MDEV-21913)
Interface Changes
innodb_
encryption_ system variable maximum value changed fromthreads 4294967295
to255
innodb_
instant_ system variable addedalter_ column_ allowed mariabackup --rollback-xa command-line option added
mysqld --innodb-instant-alter-column-allowed command-line option added
mysqld --shutdown-wait-for-slaves command-line option added
mysqldump --ignore-table-data command-line option added
shutdown_
wait_ system variable addedfor_ slaves
Platforms
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.3.23-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
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
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.