Release Notes for MariaDB Enterprise Server 10.3.28-11

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

MariaDB Enterprise Server 10.3.28-11 was released on 2021-03-15.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE (with cve.org link)

CVSS base score

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

  • The new mysqldump --system={all, users, plugins, udfs, servers, stats, timezones} command-line option allows dumping system information in logical form. (MDEV-23630)

  • Added primary host and port info to replica stop messages. (MDEV-10272)

  • Parameter innodb_idle_flush_pct has no effect and is defined as deprecated. (MDEV-24536)

  • New MariaDB Enterprise Backup --log-innodb-page-corruption to continue the backup process when corruption is encountered. Corrupted pages are logged in backup_corrupted file in the backup destination directory. (MDEV-22929)

  • MariaDB Enterprise Backup adds completed with Error! to the end of the log file if the backup is started with parameter --log-innodb-page-corruption and completed with corrupted tables. The new log entry canceled with Error! will be used when the backup could not be completed. (MENT-1059)

  • wsrep_provider and wsrep_notify_cmd system variables are read-only. (MDEV-25179)

Issues Fixed

Can result in data loss

  • In a very unlikely event, corruption of system tablespace or last recovered page can occur on recovery or a MariaDB Backup prepare (MENT-1124, MDEV-24449)

  • Crash on recovery after server kill during instant ADD COLUMN (MDEV-24323)

Can result in a hang or crash

  • Possible segfault on CREATE TABLE with explicit FTS_DOC_ID_INDEX using multiple fields. (MDEV-24403)

  • Server crashes upon attempt to update view through second execution of a stored procedure. (MDEV-16940)

  • CREATE VIEW containing WITH clause can crash. (MDEV-22781)

  • Possible crash for a query using recursive CTE without having a default schema defined. (MDEV-24019)

  • Server crash on WITH RECURSIVE UNION ALL (CTE) query. (MDEV-23619)

  • Server hang due to Galera lock conflict resolution. (MDEV-23328)

  • Possible crash in replication when applying a transaction that contains cascading foreign key delete for a table and that has an indexed virtual column. (MDEV-23033)

  • Possible lock conflicts between two wsrep high priority threads in MariaDB Enterprise Cluster on tables having unique secondary keys. (MDEV-23851)

  • Server crash when VALUE() uses a subselect. (MDEV-24675)

  • Possible crash of the server when audit logging is active. (MENT-1098)

Can result in unexpected behavior

Interface Changes

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.28-11 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.

Last updated

Was this helpful?