All pages
Powered by GitBook
1 of 22

MariaDB Enterprise Server 10.3

Release notes for MariaDB Enterprise Server 10.3 series releases

What's New in MariaDB Enterprise Server 10.3?

MariaDB Enterprise Server 10.3 introduces the following new features:

Enterprise Lifecycle

MariaDB Enterprise Server uses an enterprise lifecycle, which provides optimized builds, predictable release behavior, and vendor support.

Optimizer Trace

Optimizer Trace collects trace data to aid query optimization and diagnosis of query execution issues.

Enterprise Backup

MariaDB Enterprise Backup enables non-blocking backups of MariaDB Enterprise Server.

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

Release Notes for MariaDB Enterprise Server 10.3.39-20

MariaDB Enterprise Server 10.3.39-20 is a maintenance release of MariaDB Enterprise Server 10.3. |This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.39-20 was released on 2023-06-13.

MariaDB Enterprise Server 10.3 is EOL (end-of-life) as of 2023-05-25. Users of this release series should upgrade to a more recent Enterprise Server release series.

Fixed Security Vulnerabilities

CVE (with cve.org link)
CVSS base score

CVE-2022-47015 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.

Issues Fixed

Can result in data loss

  • When binlog_row_image=FULL is set and slave_parallel_threads is greater than 0, replica servers can hang if data is inserted into tables with a sequence. (MDEV-29621)

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.39-20 is provided for:

  • CentOS 7 (x86_64)

  • Debian 10 (x86_64, ARM64)

  • Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

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

Release Notes for MariaDB Enterprise Server 10.3.38-19

MariaDB Enterprise Server 10.3.38-19 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.38-19 was released on 2023-03-13.

Issues Fixed

Can result in data loss

  • When executing a DELETE or UPDATE with a subselect, the server can crash. (MDEV-10087)

  • When performing an incremental backup, MariaDB Enterprise Backup does not reflect databases that have been dropped and created. (MDEV-23335)

Can result in a hang or crash

  • When DELETE HISTORY is executed for a system versioned table with full text index, the server can crash. (MDEV-25004)

  • When an ALTER TABLE statement causes InnoDB to rebuild a table with a spatial index, the server can crash. (MDEV-29856)

  • When using SPIDER with SPIDER_DIRECT_SQL and spider_udf_ds_use_real_table=1, the server can crash. (MDEV-29855)

  • When executing REPLACE INTO ... PARTITION(...), the server can crash. (MDEV-29636)

  • Galera SST doesn't properly handle undo* files from InnoDB. As a result, SST may terminate incorrectly when --innodb-undo-tablespaces is set to 3 or more. (MDEV-30157)

  • With a query containing nested WINDOW clauses, the server can crash. (MDEV-30052)

  • When executing a SELECT from complex a view with WHERE clause and with the setting derived_merge=on, the server can crash. (MDEV-30081)

  • Infinite sequence of recursive calls when processing embedded CTE, when such a reference has the same table name as the name of the CTE. (MDEV-30248)

  • A deadlock between InnoDB statistics updates and BLOB insert can result in a server hang. (MDEV-29883)

Can result in unexpeted behavior

  • log_query_not_using_indexes=OFF is ignored when log_slow_filter is an empty string. (MDEV-21187)

  • MariaDB Enterprise Backup returns with an error when the option --galera-info is used for creating a backup of a MariaDB Server instance, which is not a MariaDB Enterprise Cluster node. Failed to get master wsrep state from SHOW STATUS (MDEV-30293)

  • When querying a table with virtual generated columns using full text search, these columns are not generated and are always NULL in the result set. (MDEV-29169)

  • Identifiers are not quoted for the output of SHOW GRANTS. Using the result to execute the grant statement results in a syntax error, if reserved keywords are used. (MDEV-30056)

  • Spider table with CHARSET utf32/utf16/ucs2 tries to set client CHARSET to unsupported value. (MDEV-29562)

  • Incorrect results are returned when using STDDEV_SAMP() with a view. (MDEV-19071)

  • A spurious error can be generated: ERROR 1292 (22007) at the line 15: Truncated incorrect DECIMAL value:#(MDEV-30342)

  • When running mariadb-binlog using the option --verbose, cannot read row events with compressed columns: Error: Don't know how to handle column type:... (MDEV-25277)

  • Incorrect results are returned with outer join, merged derived table, and view. (MDEV-28602)

  • Some DDL, such as ANALYZE, can be completed out of order on parallel replicas. (MDEV-30323)

  • seconds_behind_master is incorrect for delayed parallel replicas. (MDEV-29639)

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.38-19 is provided for:

  • CentOS 7 (x86_64)

  • Debian 10 (x86_64, ARM64)

  • Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

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

Release Notes for MariaDB Enterprise Server 10.3.37-18

MariaDB Enterprise Server 10.3.37-18 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.37-18 was released on 2022-12-21.

Notable Changes

  • The information_schema.INNODB_SYS_TABLESPACES view shows details about the InnoDB temporary tablespace, which is the tablespace where InnoDB temporary tables are stored. (MDEV-29479)

    • Starting with this release, the details about the InnoDB temporary tablespace can be shown by querying for the name innodb_temporary:

SELECT * FROM information_schema.INNODB_SYS_TABLESPACES
 WHERE name LIKE 'innodb_temporary';
  • When a table's default collation is set to the default collation for the table's character set, SHOW CREATE TABLE shows the COLLATE clause. (MDEV-29446)

    • In previous releases, MariaDB Enterprise Server reduced the size of SHOW CREATE TABLE output by excluding the COLLATE clause if the table's default collation was set to the default collation for the table's character set.

Issues Fixed

Can result in data loss

  • When a column is renamed in a partitioned table with ALTER TABLE .. RENAME COLUMN using the NOCOPY algorithm, the table can be corrupted. (MDEV-28576)

  • When the InnoDB storage engine performs change buffer operations, the InnoDB Redo Log can overflow, which can cause table corruption. (MENT-1661, MDEV-29905)

Can result in a hang or crash

  • When a query contains an IN/ALL/ANY predicand and the subquery contains a GROUP BY clause with an IN/ALL/ANY predicand with a single-value subquery as the left operand, the server can crash. (MDEV-29350)

  • If an InnoDB table contains a foreign key constraint and the child table's DATABASE_NAME/TABLE_NAME.ibd is longer than 330 characters, when the parent table is renamed, the server can crash. (MDEV-29409)

  • When a DDL statement is executed using the INPLACE algorithm and innodb_adaptive_hash_index=ON is set, the server can hang. (MDEV-27700, MDEV-29384)

  • When renaming a table to a long name, the server can crash. (MDEV-29258)

  • When an ALTER TABLE statement causes InnoDB to rebuild a table with a spatial index, the server can crash. (MDEV-29520)

  • When an InnoDB temporary table contains a spatial index, the server can crash if the temporary table is dropped due to DROP TEMPORARY TABLE or client disconnect. (MDEV-29507)

  • When querying a partitioned table using the PARTITION syntax, if the WHERE clause results in an index merge, the server can crash. (MDEV-21134)

  • When detecting CTE dependencies of nested CTEs that includes one or more recursive CTEs, infinite recursion can occur until the server crashes. (MDEV-29361)

  • When the wsrep_notify_cmd system variable is configured to use the bundled wsrep_notify.sh script, the server can hang during startup. (MDEV-27682)

  • When selecting from InnoDB's information_schema views (such as INNODB_TRX, INNODB_LOCKS, and INNODB_LOCK_WAITS), if connections with open XA transactions are disconnected or killed at the same time, the server can crash. (MDEV-29575)

  • For some queries that involve tables with different but convertible character sets for columns taking part in the query, a repeatable execution of such queries in the prepared statement mode or as part of a stored routine can crash the server. (MDEV-16128)

  • When executing a SELECT .. UNION .. SELECT or [EXPLAIN EXTENDED](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/administrative-sql-statements/analyze-and-explain-statements/explain) statement, the server can crash. ([MDEV-23160](https://jira.mariadb.org/browse/MDEV-23160))

  • When optimizer_switch='condition_pushdown_for_derived=on' is set and a view that includes a subquery is queried, the server crashes. (MDEV-16549)

  • When the rolling upgrade procedure for MariaDB Enterprise Cluster (powered by Galera) is used to upgrade from ES 10.3 to ES 10.4, the joiner nodes can crash after the upgrade to ES 10.4. (MDEV-29375)

    • In previous releases, the MariaDB Error Log on the joiner node could contain the following error about the crash:

[Note] WSREP: 

####### Assign initial position for certification: 5c410a36-23a8-11ed-a44c-f6f37823dd10:3, protocol version: -1

[ERROR] WSREP: Corrupt buffer header: addr: 0x7f722bd5b530, seqno: 7019267256999739392, size: 825111097, ctx: 0x559652a28678, flags: 14391. store: 46, type: 49
[ERROR] mysqld got signal 6 ;
  • When the global value of the wsrep_on system variable is changed dynamically on a node that does not have MariaDB Enterprise Cluster (powered by Galera) configured, the server crashes when DDL is executed in TOI mode. (MDEV-29706)

    • In previous releases, the following statements could cause the crash on a node without Enterprise Cluster configured:

SET GLOBAL wsrep_on=ON;
CREATE TABLE t (c INT) ENGINE=InnoDB;

Can result in unexpected behavior

  • In the presence of replication filters, revoking privileges from a non-existing user on a primary (master) breaks replication on the replica (slave). (MDEV-28530)

  • When replicate_wild_ignore_table='mysql.%' is set on a replica node, the replica node does not skip replicated SET DEFAULT ROLE statements. (MDEV-28294)

  • When a Spider table has a prefix index, query results can be incorrect. (MDEV-27172)

  • InnoDB can extend tablespace files when additional capacity is not required. (MDEV-13013)

  • When an InnoDB table is being rebuilt and a BLOB is updated during the online rebuild, a memory leak can occur. (MDEV-29600)

  • When a view is queried using a prepared statement, the query fails with the ER_NEED_REPREPARE error code. (MDEV-17124)

    • In previous releases, the following error would occur:

ERROR 1615 (HY000): Prepared statement needs to be re-prepared
  • When an InnoDB table contains virtual generated columns that are indexed, InnoDB fails to purge secondary index records. (MDEV-29666)

  • When using the InnoDB adaptive hash index, non-locking reads can return wrong results due to a potential ACID violation. (MDEV-28709, MDEV-29635, MDEV-27927)

  • When SHOW COLUMNS is used on a temporary table, an empty result set is returned. (MDEV-28455)

  • When a sequence is used as the default value in a table, rows inserted by an INSERT ... SELECT statement can be assigned the wrong values. (MDEV-29540)

  • When a column has both a UNIQUE index and a FULLTEXT index, full-text search using MATCH(..) AGAINST(..) does not work properly. (MDEV-29778)

  • If the server is started with the --ssl option enabled, but the TLS certificates and keys are not configured, the server will advertise the TLS support in the handshake, but will not actually be able to use it. (MDEV-29811)

  • With MariaDB Enterprise Cluster, when wsrep_sst_method='mariadb-backup' is configured, the joiner node ignores custom values for the innodb_buffer_pool_filename system variable, and the SST copies the buffer pool file to the default location instead. (MDEV-28968)

Related to install and upgrade

  • When MyRocks is installed from a Debian package, the rocksdb.cnf configuration file gets installed to /etc/mysql/mariadb.conf.d/ instead of /etc/mysql/conf.d/. (MDEV-28605)

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.37-18 is provided for:

  • CentOS 7 (x86_64)

  • Debian 10 (x86_64, ARM64)

  • Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

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

Release Notes for MariaDB Enterprise Server 10.3.36-17

MariaDB Enterprise Server 10.3.36-17 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.36-17 was released on 2022-09-12.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2018-25032

7.5

CVE-2022-32091

6.5

CVE-2022-32084

6.5

Notable Changes

  • Debian 9 support has been discontinued.

  • The --max-statement-time command-line option has been added for mariadb-dump with a default value of 0. (MDEV-18702)

Issues Fixed

Can result in data loss

  • When mariadb-backup is executed with the --rsync command-line option, the backup tries to copy the InnoDB buffer pool dump file, which is located at the path defined by the innodb_buffer_pool_filename system variable. (MDEV-28781)

    • Starting with this release, mariadb-backup only copies the InnoDB buffer pool dump file during State Snapshot Transfers (SSTs) for MariaDB Enterprise Cluster, powered by Galera.

  • When ALTER TABLE .. IMPORT TABLESPACE is executed against an encrypted InnoDB tablespace file, the table can be corrupted. (MDEV-28779)

Can result in a hang or crash

  • When INSERT .. SELECT .. GROUP BY is executed and the GROUP BY clause contains a derived table, the server can crash. (MDEV-28617)

  • When a query contains an ANY(SELECT .. GROUP BY(SELECT ..)) predicand with a redundant subquery in the GROUP BY clause, the server can crash. (MDEV-29139)

  • When ALTER TABLE .. ADD is used to add a column with the INSTANT algorithm, the server can crash if the ROW_FORMAT in the .frm file does not match the actual row format used by the data file. (MDEV-26577)

    • For tables created prior to MariaDB Server 10.2, the ROW_FORMAT in the .frm file could be inconsistent with the actual row format used by the data file. If the server were upgraded to MariaDB Enterprise Server 10.6, the inconsistency could remain.

  • When INSERT .. SELECT is executed and the SELECT query calls an aggregate or window function, the server can crash with a segmentation fault. (MDEV-26427)

  • When the JSON_EXTRACT() function is called, the server can crash with a segmentation fault. (MDEV-29188)

  • When a query uses the DISTINCT keyword and calls an aggregate function as an argument for an always-constant function, the server can crash. (MDEV-23809)

    • An always-constant function is a function that always returns a constant value, even if the function's arguments are not constant.

    • For example, the COLLATION() function is an always-constant function.

  • When mariadb-backup is executed with the --compress and --parallel options, the backup can hang due to a race condition between threads. (MDEV-29043)

  • When an EXISTS predicate or an IN, ALL, or ANY predicand is used in an eliminated GROUP BY clause, the server can crash. (MENT-1606, MDEV-29350)

Can result in unexpected behavior

  • For multi-table [UPDATE|[UPDATE]] or DELETE queries, the optimizer fails to apply partition pruning optimization for the table that is updated or deleted from. (MDEV-28246)

  • When an IN condition contains a mixture of numeric and string values, results can be inconsistent. (MDEV-21445)

  • When a sequence event is written to the binary log with binlog_format=ROW, the value of binlog_row_image is not respected. (MDEV-28487)

  • When a transaction can't be fully written to the binary log, but the transaction can be safely rolled back, a LOST_EVENTS incident event is written to the binary log. (MDEV-21443)

    • In previous releases, this problem could cause replica servers to encounter the following error:

Last_SQL_Errno	1590
Last_SQL_Error	The incident LOST_EVENTS occurred on the master. Message: error writing to the binary log
  • Starting with this release, a LOST_EVENTS incident is only written to the binary log when safe rollback is not possible.

  • When a replica server replicates an incident event, the details about the failure are not in the primary server's error log, the replica server's error log, or the output of SHOW REPLICA STATUS. (MDEV-21087)

  • When a backup is performed with mariadb-backup, the backup includes binary logs. (MDEV-28758)

  • When a table is created from a SELECT statement that uses a recursive CTE, the table can use unexpected data types and contain truncated data if the calculated values from the recursive part of the CTE do not fit in the column types that are taken from the non-recursive part of the CTE. (MDEV-12325)

    • Starting with this release, the CTE calculation is aborted when the calculated values do not fit in the column types. When this occurs, a warning or error (depending on sql_mode is raised with the ER_WARN_DATA_OUT_OF_RANGE error code and the following error message:

Out of range value for column 'COLUMN_NAME' at row ROW_NUM
  • When mariadb client uses EditLine instead of readline (such as on Debian and Ubuntu), Unicode characters are not accepted. (MDEV-28197)

  • When the optimizer chooses a semi-join optimization for a subquery, the LooseScan and FirstMatch strategies are not considered for certain queries where they would be appropriate, and they are considered for certain queries where they would be inappropriate. (MDEV-28749)

  • When FULLTEXT search is performed on an InnoDB table, the results are incorrect when the search term contains an apostrophe ('). (MDEV-20797)

    • Starting with this release, when a search term contains an apostrophe ('), InnoDB tokenizes the word at the apostrophe, ignores the first token, and matches against the second token.

Interface Changes

  • mariadb-backup --sst-max-binlogs command-line option removed

  • mysql --enable-cleartext-plugin command-line option added

  • mysqldump --max-statement-time command-line option added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.36-17 is provided for:

  • CentOS 7 (x86_64)

  • Debian 10 (x86_64, ARM64)

  • Microsoft Windows (x86_64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

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

Release Notes for MariaDB Enterprise Server 10.3.35-16

MariaDB Enterprise Server 10.3.35-16 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.35-16 was released on 2022-06-13.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2022-27458

7.5

CVE-2022-27456

7.5

CVE-2022-27452

7.5

CVE-2022-27449

7.5

CVE-2022-27448

7.5

CVE-2022-27447

7.5

CVE-2022-27445

7.5

CVE-2022-27387

7.5

CVE-2022-27386

7.5

CVE-2022-27384

7.5

CVE-2022-27383

7.5

CVE-2022-27381

7.5

CVE-2022-27380

7.5

CVE-2022-27379

7.5

CVE-2022-27378

7.5

CVE-2022-27377

7.5

CVE-2022-27376

7.5

CVE-2022-32088

6.5

CVE-2022-32087

6.5

CVE-2022-32085

6.5

CVE-2022-32083

6.5

CVE-2021-46669

6.5

CVE-2022-21427

4.9

Backported Features

MariaDB Enterprise Server enables a predictable development and operations experience through an enterprise lifecycle. These new features have been backported after reaching maturity in MariaDB Community Server:

  • mysqldump option --as-of reads data as of specific timestamp from system-versioned tables. (MENT-1457)

Notable Changes

  • Galera updated to 25.3.37

  • Spider storage engine refuses attempts to create a temporary table since the engine cannot itself store data and cannot create temporary tables on a remote server. (MDEV-28225)

  • Status variables Innodb_encryption_key_rotation_list_length, Innodb_num_index_pages_written and Innodb_num_non_index_pages_written were unused and have been removed. (MDEV-28541, MDEV-28537)

  • Starting with this release, when wsrep_sst_method| is set to rsync or mariadb-backup, the sst_max_binlogs SST option can be specified in the [sst] option group in configuration files. This parameter specifies the number of binary log files to be sent to the joiner node during SST. (MDEV-27524)

    • The default value is 0:

      • If a binlog exists, it will be transferred.

      • If a binlog does not exist, no binlog will be transferred.

Issues Fixed

Can result in data loss

  • When the parser converts a string from the binary character set to a multi-byte character set (such as utf32), an invalid string could be produced. (MDEV-23210)

  • When rows are inserted into an intermediate temporary table via the LOAD DATA INFILE statement,and then the rows are copied from the temporary table to a persistent table, the rows are not written to binary log if binlog_format=MIXED is set, which prevents the operation from properly replicating to replica servers. (MDEV-24667)

  • When innodb_disallow_writes=ON is set, mysqladmin shutdown can hang. (MDEV-25975)

    • Starting with this release, the innodb_disallow_writes system variable has been removed.

  • When a replica server's I/O thread receives an incomplete event group from the primary server, the replica server continues writing events to the relay log and does not raise an error. (MDEV-27697)

  • Semisync-replica server recovery fails to rollback a prepared transaction. (MENT-1534)

Can result in a hang or crash

  • With MariaDB Enterprise Cluster, powered by Galera, when wsrep_sst_method is set to rsync or mariadb-backup, the donor node does not transfer the correct binary logs to the joiner node with some configurations. (MDEV-27524)

  • When a window function is used in the global ORDER BY clause of a SELECT statement with a UNION, the statement should be rejected, but the server executes the statement and crashes with a segmentation fault. (MDEV-15208)

  • When a stored procedure queries a view and uses a for loop, the server can crash with a segmentation fault when the stored procedure is called twice in the same session. (MDEV-26009)

  • Server can crash when a procedure that queries a view is called twice. (MDEV-26009)

  • When innochecksum is executed on an encrypted tablespace file using the --page-type-summary or -S option, innochecksum crashes with a segmentation fault unless the --page-type-dump or -D option is also specified. (MDEV-27835)

  • When an invalid CREATE SEQUENCE ... RESTART statement is used inside of a CREATE PROCEDURE or CREATE FUNCTION statement, the server can crash while parsing the statement. (MDEV-28220)

  • Possible crash on parsing a syntax incorrect statement CREATE SEQUENCE .. RESTART inside of a ``CREATE PROCEDUREorCREATE FUNCTION` (MDEV-28220)

  • When a table contains a virtual generated column that is defined using the IF() and DATE_FORMAT() functions, inserting a row into the table can cause the server to crash with a segmentation fault. (MDEV-24176)

  • Server crash after INSERT in a table with virtual column generated using date_format() and if() (MDEV-24176)

  • When a non-updateable view is defined with ALGORITHM=TEMPTABLE, selecting data from the view can cause the server to crash with a segmentation fault. (MDEV-21028)

  • When a UNION of decimal types is performed in an ORDER BY clause, the server can crash with a segmentation fault. (MDEV-25994)

  • When a stored procedure executes a query that results in a mergeable derived table, the server can crash with a segmentation fault when the stored procedure is called twice in the same session. (MDEV-27212)

    • Querying views can result in mergeable derived tables.

    • Using subqueries with outer references can result mergeable derived tables.

  • When ANALYZE FORMAT=JSON is executed with a query that contains a subquery, the server can crash. (MDEV-28268)

  • When a query using a window function with an OVER (PARTITION BY ..) or OVER (ORDER BY ..) clause is executed, the server can crash with a segmentation fault. (MDEV-19398)

    • If the query also uses WITH ROLLUP, this crash is more likely.

    • If the query'sOVER (PARTITION BY ..)orOVER (ORDER BY ..)clause uses an aggregate function, this crash is more likely.

  • When a query contains an outer join expression and a non-correlated subquery that the optimizer determines is low cost, executing the query can cause the server to crash if the optimizer also determines that the inner join expression can be eliminated. (MDEV-28437)

  • With MariaDB Enterprise Cluster, a joiner node's binary logs could be deleted during an Incremental State Transfer (IST), which causes the node to fail to start, because it can not read the binary logs. (MDEV-28583)

  • This issue is confirmed to happen with wsrep_sst_method set to rsync, but it might also occur with other SST/IST methods.

  • ALTER TABLE on a large InnoDB table can hang. (MDEV-28415)

Can result in unexpected behavior

  • When OPTIMIZE TABLE is executed on a sequence, the server raises an ER_BINLOG_UNSAFE_STATEMENT warning, even if binlog_format is set to ROW or MIXED. (MDEV-24617)

    • The warning can appear in the MariaDB Error Log as the following:

[Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave Statement: OPTIMIZE TABLE SEQUENCE_NAME
  • When an UPDATE or DELETE statement uses an OR clause, the server raises an ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE error. (MDEV-18304)

    • The error can appear on the client as the following:

You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column
  • When an UPDATE statement uses a subquery inside an IN() clause, the optimizer could incorrectly choose to perform a full table scan (with type: ALL) when a range scan (with type: range) would be more efficient. (MDEV-22377)

  • When a table contains multiple ENUM columns with identical values, the values could become corrupt if multi-byte character sets are used. (MDEV-28078)

  • When DECIMAL columns are read from information_schema.PROCESSLIST, the server could incorrectly raise an ER_BAD_DATA warning. (MDEV-28131)

    • The warning can appear on the client as the following after executing SHOW WARNINGS:

Encountered illegal value '' when converting to DECIMAL
  • With sql_mode=ORACLE, the parser allows functions to be called using PACKAGE_NAME.FUNCTION_NAME(), but the parser raises a ER_PARSE_ERROR error if the function is called using DATABASE_NAME.PACKAGE_NAME.FUNCTION_NAME(). (MDEV-28166)

    • When a view is used to update multiple rows of a temporal table in a single UPDATE statement, the server incorrectly raises a ER_WARN_VIEW_WITHOUT_KEY warning. (MDEV-22973)

    • The warning can appear on the client as the following after executing SHOW WARNINGS:

View being updated does not have complete key of underlying table in it
  • When using mariadb-binlog with --raw and --stop-never, events from the primary server's currently active log file are not written to their respective log file specified by --result-file. (MDEV-14608)

  • When a prepared statement is used to execute EXPLAIN, a different query plan can be returned on the second execution. (MDEV-19631)

  • When slave_compressed_protocol is enabled with semi-synchronous replication, the numbering on packet headers can become out of sync between the primary and replica servers, but the inconsistency does not have any negative impact with release builds of MariaDB Enterprise Server. (MDEV-25580)

  • The server and MariaDB Enterprise Backup can raise unnecessary warnings about tablespace IDs in some scenarios. (MDEV-27343)

    • The warning can appear as the following:

InnoDB: Allocated tablespace ID TABLESPACE_ID for DATABASE_NAME/TABLE_NAME, old maximum was 0
  • This warning can be written to standard output (stdout) when preparing a backup with MariaDB Enterprise Backup.

  • This warning can be written to the MariaDB Error Log when InnoDB performs crash recovery at startup.

  • With MariaDB Enterprise Cluster, the joiner node fails to complete an SST when innodb_log_group_home_dir specifies a directory different than datadir. (MDEV-27740)

  • When a non-partitioned table using the DATA DIRECTORY clause is converted to a partitioned table, the DATA DIRECTORY clause is silently ignored, and the partitioned table is moved to the default directory. (MDEV-27065)

  • Starting with this release, the server will raise the WARN_OPTION_IGNORED warning.

  • When a table contains an invisible column, mariadb-dump does not produce the correct CREATE TABLE statement in the backup file. (MDEV-28253)

  • When a Spider table is queried using IF(COUNT() ..), the server can raise an ER_BAD_FIELD_ERROR error. (MDEV-25116)

  • With MariaDB Enterprise Cluster, State Snapshot Transfers (SSTs) can fail on the donor node when binary logs are enabled. (MDEV-26201)

  • With MariaDB Enterprise Cluster, when wsrep_node_address contains an IPv6 address and wsrep_sst_receive_address is set to the default value of AUTO, State Snapshot Transfers (SST) can fail. (MDEV-26171)

  • With temporal tables, replication can break if a system versioned table has been created on the replica via mariadb-dump, if the original table was altered before. (MDEV-28254)

  • mariadb-backup does not detect multi-source replication primary. (MDEV-21037)

  • Master_SSL_Crl shows Master_SSL_CA value in SHOW SLAVE STATUS output. (MDEV-28428)

  • MariaDB Audit plugin produces corrupted log entries for CONNECT events. (MENT-1438)

  • mariadb-dump does not create a dump where the sql_mode is set correctly for SQL/PL packages. (MDEV-27816)

  • Missing binlog data for INSERT .. ON DUPLICATE KEY UPDATE (MDEV-28310)

  • mariadb-backup prepare fails for incremental backups if a new schema is created after full backup. (MDEV-28446)

  • Optimizer uses all partitions during an UPDATE and ignores partitioning filters. (MDEV-28246)

  • When INSERT .. ON DUPLICATE KEY UPDATE is executed and binlog_format is set to MIXED, the server raises an [e1592|[ER_BINLOG_UNSAFE_STATEMENT warning]] even though the statement is written to the binary log in row-based format. (MDEV-21810)

    • The warning can appear in the MariaDB Error Log as the following:<<sql inline=false>> [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... ON DUPLICATE KEY UPDATE on a table with more than one UNIQUE KEY is unsafe Statement: INSERT INTO TABLE_NAME VALUES (..) ON DUPLICATE KEY UPDATE KEY_NAME = KEY_VALUE <<sql>>

  • When INSERT .. ON DUPLICATE KEY UPDATE is executed and binlog_row_image is set to FULL, the server does not write unchanged columns to the binary log. (MDEV-21810)

    • Crash recovery fails if the configured server ID does not match the server ID in the crashed data directory. (MENT-1535)

Related to install and upgrade

  • Galera snapshot transfer fails to upgrade between some major versions. (MDEV-27437)

  • On Windows, MSI installer does not install client shared libraries. (MDEV-28581)

  • After upgrade, mysql.plugin table has an entry for Semi-sync Replication, though this former plugin functionality is now built-in. (MDEV-21873)

Interface Changes

  • innodb_disallow_writes system variable removed

  • Innodb_encryption_key_rotation_list_length status variable removed

  • Innodb_num_index_pages_written status variable removed

  • Innodb_num_non_index_pages_written status variable removed

  • mariadb-backup --sst-max-binlogs command-line option added

  • mysqldump --as-of command-line option added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.35-16 is provided for:

  • CentOS 7 (x86_64)

  • Debian 9 (x86_64, ARM64)

  • Debian 10 (x86_64, ARM64)

  • Microsoft Windows (x86_64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

Note

This is the final release for Debian 9.

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

Release Notes for MariaDB Enterprise Server 10.3.34-15

MariaDB Enterprise Server 10.3.34-15 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.34-15 was released on 2022-03-14.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2021-46668

5.5

CVE-2021-46665

5.5

CVE-2021-46664

5.5

CVE-2021-46663

5.5

CVE-2021-46661

5.5

CVE-2021-46659

5.5

CVE-2022-21595

4.4

Notable Changes

  • Galera updated to 25.3.35

  • The maximum values for innodb_ft_cache_size and innodb_ft_total_cache_size have been changed from 80000000 to 1099511627776 (1 TB). (MENT-1428)

Issues Fixed

Can result in data loss

  • Columns in some INFORMATION_SCHEMA tables are erroneously declared with DEFAULT clauses, which is not compliant with the SQL standard. (MDEV-18918)

    • Consequently, when sql_mode=EMPTY_STRING_IS_NULL is set, queries like CREATE TABLE .. SELECT .. FROM INFORMATION_SCHEMA... could encounter replication errors like the following:

Error 'Invalid default value for 'TABLE_NAME'' on query. Default database: 'test'. Query: 'CREATE TABLE `t1` (`TABLE_NAME` varchar(64) CHARACTER SET utf8 NOT NULL DEFAULT ''
  • When an ALTER TABLE statement changes the order of indexes in a MyISAM or Aria table using the INPLACE algorithm, the table can become corrupt. (MDEV-25803)

  • When CREATE OR REPLACE SEQUENCE is written to the binary log, the statement is not flagged as DDL, which causes the replica servers to execute the statement in an unsafe way if parallel replication is enabled. (MDEV-27365)

Can result in a hang or crash

  • When a FULLTEXT index is added to an InnoDB table with ALGORITHM=INPLACE and the indexed column uses the tis620character set, the server can crash with a segmentation fault (signal 11). ([MDEV-24901](https://jira.mariadb.org/browse/MDEV-24901))

  • When MariaDB Server is used on the ARM architecture, which uses a weak memory model, an internal hash table implementation can cause the server to crash with a segmentation fault (signal 11). (MDEV-27088)

  • When wsrep_sst_method=mariadb-backup and innodb_force_recovery=1 are set with MariaDB Enterprise Cluster, powered by Galera, the joiner node fails to perform an SST. (MDEV-26064)

    • The SST log contains the following message related to the failure:

mariadb-backup: The option "innodb_force_recovery" should only be used with "--prepare".
mariadb-backup: innodb_init_param(): Error occurred.
  • When --stream=xbstream is set, MariaDB Enterprise Backup can hang on lock acquisitions due to a deadlock. (MDEV-26558)

  • When a stored procedure is defined with a query that contains a set function, and the set function's only argument is an outer reference to a column of a mergeable view, a derived table, or a CTE, the second execution of the stored procedure can cause the server to crash. (MDEV-25086)

  • When a derived table is created for certain queries that use subqueries over Views or CTEs, the server can crash with a segmentation fault (signal 11). (MDEV-25631)

  • When a stored procedure uses a cursor to run a query that requires an internal temporary table (such as queries containing an ORDER BY clause), the server can crash due to a segmentation fault (signal 11). (MDEV-24827)

  • Server can crash if a CTE or derived table is not used by the query. (MDEV-25766)

  • When log_slow_verbosity = 'explain' is set and a query is executed that references a derived table, the server can crash while writing the query's execution plan to the slow query log. (MDEV-26249)

  • When a stored procedure or a prepared statement is used to execute a query that performs a join which compares a GEOMETRY column with a different data type, executing the stored procedure or prepared statement twice can cause the server to crash. (MDEV-20770)

  • With MariaDB Enterprise Cluster, when wsrep_cluster_address is set to an unknown address and wsrep_slave_threads is set to 0, the server crashes. (MDEV-25472)

  • When a system versioned table is created with character_set_server=utf8mb4 and collation_server=utf8mb4_unicode_1400_ci, the server can crash. (MDEV-27195)

  • When a system-versioned table is partitioned by SYSTEM_TIME, executing DELETE FROM .. PARTITION(..) causes the server to crash. (MDEV-27217)

  • When the following conditions are met, executing a prepared statement twice can cause the server to crash: (MDEV-23182)

    • The in_predicate_conversion_threshold system variable must be set to some value n.

    • The query must contain an IN(...) clause with more than n string literals.

    • The query must require character set conversions.

Can result in unexpected behavior

  • When a multi-byte character set is used, the last character of a TINYTEXT column can be truncated, which makes it appear as a question mark ('?). (MDEV-24335)

  • Subquery using the ALL keyword on TIME columns produces a wrong result. (MDEV-27098)

  • Subquery using the ALL keyword on DATE columns produces a wrong result. (MDEV-27072)

  • When float literals are defined using scientific notation and the token also contains certain special characters, the parser incorrectly parses the float value and completely drops it from the request. (MDEV-27066)

  • When a double-encapsulated CTE query calls a function which reads a table that has been aliased in the CTE query, the server incorrectly raises an error with the ER_NO_SUCH_TABLE error code. (MDEV-26825)

  • When a CTE is used in a subquery of a DELETE statement, the server incorrectly raises an error with the ER_NO_DB_ERROR error code. (MDEV-26470)

  • When MariaDB Enterprise Cluster performs an SST, the SST scripts incorrectly try to read ssl_ca as a path to a directory of TLS CA certificates instead of using ssl_capath for that purpose. (MDEV-27181)

  • When MariaDB Enterprise Cluster performs an SST, the SST scripts do not always interpret log_bin_index correctly. (MDEV-26915)

  • When an index is used for an ORDER BY .. LIMIT query, the optimizer does not disable the Range Checked for Each Record optimization. (MDEV-27270)

  • When optimizer_switch='index_merge_sort_intersection=on' is set, the optimizer can incorrectly choose to merge an index that does not help, because the query conditions require the full index to be scanned. (MDEV-27262)

  • When the version system variable is set, MariaDB Connector/C and the mariadb client do not interpret MariaDB Server's extended metadata properly, which can cause results from some SHOW .. to be right-aligned. (MDEV-27304)

  • When an INSERT .. SELECT statement selects from and inserts into the same table, rows are counted twice, which can cause row numbers to be reported incorrectly in error messages. (MDEV-26698)

  • When a replica server's relay log is rotated, Seconds_Behind_Master in SHOW SLAVE STATUS can temporarily show an incorrect value that is very high. (MDEV-16091)

  • The collation column in the #information_schema.STATISTICS## table is incorrectly read as NULL. (MDEV-4621)

  • When a join performs a comparison between an expression that uses a case-insensitive collation and an ENUM##ENUM## column that uses a binary collation, the comparison uses the wrong collation, which can cause results to be incorrect. (MDEV-26129)

  • When innodb_buffer_pool_size is changed dynamically with SET GLOBAL, InnoDB does not enforce the minimum value that is enforced on startup, which can result in an impossibly small buffer pool with some values of innodb_buffer_pool_chunk_size. (MDEV-27467)

  • When the DATABASE() function is used in some queries (such as queries using UNION ALL), database names can be truncated to 34 characters, even though database names can have up to 64 characters. (MDEV-27544)

  • When the --symbolic-links option is disabled, such as when --skip-symbolic-links or --disable-symbolic-links is set, InnoDB still allows symbolic links and .isl files to be created if tables have the DATA DIRECTORY option. (MDEV-26870)

  • When CREATE TABLE t1 LIKE t2 is executed and the t2 table is a partitioned table that uses the MyISAM or Aria storage engines and has the DATA DIRECTORY option defined for partitions, the operation fails with a file system error. (MDEV-25917)

  • When sql_mode=ONLY_FULL_GROUP_BY is set, some window functions incorrectly raise an error with the ER_MIX_OF_GROUP_FUNC_AND_FIELDS error code. (MDEV-17785)

  • When a CTE is used with a UNION in a CREATE TABLE .. AS .. statement, the server incorrectly raises an error with the ER_NO_DB_ERROR error code. (MDEV-27086)

  • When the JSON_COMPACT function is called with values from a subquery, the output is not always returned as the JSON data type. (MDEV-18284)

  • When a system-versioned table is partitioned by SYSTEM_TIME with a ``LIMIT` clause, CHECK TABLE can incorrectly return an error. (MDEV-25552)

  • The lateral derived optimization is not disabled for queries that use WITH ROLLUP, which causes queries that use GROUP BY to return incorrect results. (MDEV-26337)

  • When optimizer_switch='split_materialized=on' is set, queries that use the split optimization can return the wrong results. (MDEV-27510, MDEV-27132)

  • When a row is deleted from an InnoDB table, and then a new row with the same key is inserted into the table by a different transaction, InnoDB's MVCC code can incorrectly hide the new row from transactions that should see the changes: (MENT-1414)

    • Consequently, queries can try to insert another new row with the same key, which results in an error with the ER_DUP_ENTRY error code.

    • When a replica server has slave_parallel_mode set to 'optimistic' or 'aggressive', this can result in the following error in SHOW REPLICA STATUS:

Last_Errno: 1062
Last_Error: Error 'Duplicate entry 'VALUE' for key 'KEY_NAME'' on query. Default database: 'DATABASE_NAME'. Query: 'INSERT INTO ..'

Interface Changes

  • ER_VERS_NOT_ALLOWED error code added

  • innodb_buffer_pool_size system variable minimum value changed from 5242880 to 2097152

  • innodb_ft_cache_size system variable dynamic changed from No to Yes

  • innodb_ft_cache_size system variable maximum value changed from 80000000 to 1099511627776

  • innodb_ft_total_cache_size system variable dynamic changed from No to Yes

  • innodb_ft_total_cache_size system variable maximum value changed from 1600000000 to 1099511627776

  • mysql_upgrade --check-if-upgrade-is-needed command-line option added

  • mysqld rocksdb-ignore-datadic-errors command-line option added

  • rocksdb_ignore_datadic_errors system variable added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.34-15 is provided for:

  • CentOS 7 (x86_64)

  • Debian 9 (x86_64, ARM64)

  • Debian 10 (x86_64, ARM64)

  • Microsoft Windows (x86_64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

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

Release Notes for MariaDB Enterprise Server 10.3.32-14

MariaDB Enterprise Server 10.3.32-14 is a maintenance release of MariaDB Enterprise Server 10.3. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.32-14 was released on 2021-12-13.

Fixed Security Vulnerabilities

CVE (with [cve.org] link)
CVSS base score

CVE-2022-27385

7.5

CVE-2021-46667

7.5

CVE-2022-31624

6.5

CVE-2021-46662

5.5

CVE-2021-35604

5.5

Notable Changes

  • Galera updated to 25.3.35

  • Enterprise Spider no longer enables pushdown of UDFs and Stored Functions to the Data Node by default: (MDEV-26545)

    • The default value of spider_use_pushdown_udf has changed from -1 to 0

    • In previous releases, Enterprise Spider pushed UDFs and Stored Functions down to the Data Node by default, which could cause query results to be inconsistent.

    • Starting with this release, all UDFs and stored functions are evaluated on the Spider Node by default. If desired, pushdown of UDFs and Stored Functions can be explicitly enabled by setting spider_use_pushdown_udf=1. Testing is recommended to confirm that query results are consistent.

  • Performance Schema tables provide descriptions of each column in the COMMENT column option. (MDEV-25325)

Issues Fixed

Can result in a hang or crash

  • MariaDB Enterprise Cluster, powered by Galera, can crash on INSERT if the table does not have a primary key and if the data for a field exceeds 4096 bytes. (MDEV-24978)

  • When an InnoDB tablespace (.ibd) file is imported using ALTER TABLE .. IMPORT TABLESPACE without a corresponding .cfg``file, InnoDB causes a server crash. ([MDEV-26131](https://jira.mariadb.org/browse/MDEV-26131), [MDEV-20931](https://jira.mariadb.org/browse/MDEV-20931))

  • When OPTIMIZE TABLE (or mariadb-check -o) is executed against an InnoDB table with a FULLTEXT index, InnoDB can cause a server crash. (MDEV-25702, MENT-1198)

  • Resolving aggregate functions that are used in a view can cause in a crash. (MDEV-24454)

  • Executing CREATE OR REPLACE TABLE AS SELECT under LOCK TABLE can cause in a crash. (MDEV-23391)

  • If two InnoDB tables have a foreign key and an operation cascades from the parent table to the child table, an index on a virtual generated column in the child table can become corrupt. (MDEV-26866)

  • MariaDB Enterprise Cluster, powered by Galera, crashes with errors like: [ERROR] WSREP: Trx 236236 tries to abort slave trx 236238 (MDEV-25835)

  • Server crashes when a table uses a sequence as a column default (DEFAULT NEXT_VALUE(my_seq)) and the table is used concurrently by both a prepared statement and a normal statement. (MDEV-22785)

  • MariaDB Enterprise Cluster can crash due to an incorrect conflict resolution on multi-master setup. (MDEV-25992, MDEV-25114)

Can result in unexpected behavior

  • skip_networking does not prevent replication. (MDEV-24969)

  • MariaDB Enterprise Cluster joiner node incorrectly uses localhost for TLS certificate verification and fails to join cluster when wsrep_sst_method=mariadb-backup and encrypt=3 are configured. (MDEV-26360)

  • mariadb --binary-mode is not able to replay some mysqlbinlog outputs if 0 is in the data. (MDEV-25444)

  • Memory leak with row-based replication can lead to high memory usage on replica servers. (MDEV-26712)

  • SHOW CREATE VIEW and mariadb-dump generate invalid SQL for some complex views. (MDEV-26299)

  • When statement-based or mixed replication is used and a DML statement encounters an error in a transaction that creates or drops a temporary table, non-committed writes to transactional tables can be incorrectly replicated to replica servers. (MDEV-26833)

  • MariaDB Enterprise Cluster joiner node fails to join cluster when wsrep_sst_method=mariadb-backup and Backward Compatible SST TLS Mode is configured. (MDEV-26211)

  • Spider does not work correctly for UDF and stored functions if used in a query's WHERE conditions. (MDEV-26545)

  • On a partitioned Spider table, result of SELECT wrongly depends on the partition targeted by the previous SELECT (MDEV-26333)

  • If an INVISIBLE column has a computed default value, an INSERT statement that doesn't specify a value for the column causes the default value to be ignored. (MDEV-25891)

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.34-15 is provided for:

  • CentOS 7 (x86_64)

  • CentOS 8 (x86_64, ARM64)

  • Debian 9 (x86_64, ARM64)

  • Debian 10 (x86_64, ARM64)

  • Microsoft Windows (x86_64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

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

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

Release Notes for MariaDB Enterprise Server 10.3.31-13

This thirteenth release of MariaDB Enterprise Server 10.3 is a maintenance release. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.31-13 was released on 2021-09-14.

Fixed Security Vulnerabilities

CVE (with cve.org lnk)

CVSS base sore

CVE-2021-2389

5.9

CVE-2021-4666

5.5

CVE-2021-4658

5.5

CVE-2021-4657

5.5

CVE-2021-2372

4.4

Backported Features

This release of MariaDB Enterprise Server includes features backported from MariaDB Enterprise Server 10.6.

  • Enhanced consistency for Semi-Sync Replication

    • When rpl_semi_sync_slave_enabled=ON, consistency is guaranteed for a Primary server in an HA (Primary/Replica) topology when using semi-synchronous replication. (MDEV-21117)

    • Prior to this release, when using semi-synchronous replication, if a Primary crashed before sending a transaction to the Replica, on restart the Primary could recover incomplete InnoDB transactions when rejoining as a Replica.

    • With this release, when using semi-synchronous replication and with rpl_semi_sync_slave_enabled=ON, incomplete transactions will be rolled-back on the Replica, ensuring the new Primary (former Replica) and new Replica (former Primary) remain in sync.

Notable Changes

  • Galera updated to 25.3.34

  • ARM64 is now supported for several platforms.

  • The script wsrep_sst_mariadb-backup checks all server-related configuration groups when processing a configuration file. (MDEV-25669)

  • Prior to this release, only the [mysqld] configuration group was checked when processing a configuration file.

  • MariaDB Enterprise Backup expects --stream=mbstream to stream a backup using the included mbstream utility. (MDEV-15730)

  • Prior to this release, MariaDB Enterprise Backup expected --stream=xbstream, even though the xbstream utility had been renamed to mbstream.

  • InnoDB no longer acquires advisory file locks by default. (MDEV-24393)

  • The information_schema.KEYWORDS table has been added and can be used to view details about SQL keywords. (MDEV-25129)

  • The information_schema.SQL_FUNCTIONS table has been added and can be used to view details about built-in functions. (MDEV-25129)

  • When using data-at-rest encryption with the file_key_management encryption plugin, InnoDB will automatically disable key rotation checks. (MDEV-14180)

    • The file_key_management encryption plugin does not support key rotation, so key rotation checks are not required.

    • In previous releases, unnecessary key rotation checks with the file_key_management plugin could reduce performance, unless they were explicitly disabled by setting innodb_encryption_rotate_key_age=0.

Issues Fixed

Can result in data loss

  • When an ALTER TABLE ... ADD COLUMN statement is executed with ALGORITHM=INSTANT, a warning is not raised when the operation causes the default value of a DATE column to be truncated. (MDEV-25971)

Can result in a * hang or crash

  • Possible server crash when pushing a WHERE condition over a mergeable derived table / view / CTE DT into a grouping view / derived table / CTE V whose item list contained set functions with constant arguments. (MDEV-25635)

  • Server crashes on second execution of a stored procedure or a prepared statement when the corresponding query executes a window function on a view, CTE, or derived table. (MDEV-25565)

  • Server crashes possible when executing a prepared statement with a hanging recursive CTE. (MDEV-26135)

  • Server crashes while executing query with a CTE in a prepared statement or stored procedure. (MDEV-26025)

  • Server crashes while executing query with a recursive CTE that is indirectly used twice. (MDEV-26202)

  • Server crashes due to infinite recursion while processing an embedded recursive CTE with missing RECURSIVE. (MDEV-26095)

  • Server crashes in InnoDB deadlock checker under high load. (MDEV-25594)

  • Server crashes when a virtual generated column has a prefix index. (MDEV-26220)

  • Server crashes possible when using virtual generated columns. (MDEV-18166, MDEV-18249)

  • Server crashes while executing DELETE when a YEAR column is truncated. (MDEV-17890)

  • Server crashes while executing SET ROLE when a hostname cannot be resolved. (MDEV-26081)

  • Server crashes when a subquery references an outer column in an ORDER BY clause. (MDEV-25629)

  • Server crashes due to a stack overrun in the query optimizer while executing query with more than 32 equality conditions that compare columns of different tables (such as tableX.colX=tableY.colY). (MDEV-17783)

  • Server crashes when a window function is the left expression of an IN(SELECT ..) subquery. (MDEV-25630)

  • Possible deadlock on a Replica server using GTID Replication when slave_parallel_mode=optimistic and OPTIMIZE TABLE, REPAIR TABLE, or ANALYZE TABLE is executed. (MDEV-17515)

  • Server crashes when ALTER TABLE .. ADD FULLTEXT INDEX fails on an InnoDB table. (MDEV-25721)

  • Server crashes while executing TRUNCATE on an InnoDB table with a Full-Text Index. (MDEV-25663)

  • Server crashes while executing ALTER TABLE on an InnoDB table with virtual generated columns that are indexed. (MDEV-25872)

  • Server crashes while executing CHECK TABLE when innodb_read_only is enabled. (MDEV-25886)

  • Crash when parsing query using derived table containing table value constructors (MDEV-25484)

  • Server crashes when a connection is killed while executing ALTER TABLE after previously locking the table with LOCK TABLE. (MDEV-17749)

  • Server crashes when the global value of the system_versioning_asof system variable is set using a stored function that reads the value of another global system variable. (MDEV-16481)

Can result in unexpected behavior

  • When CREATE OR REPLACE TABLE fails after dropping the table, the DROP TABLE operation is not written into the binary log. (MDEV-25595)

  • The SHOW GRANTS statement does not quote role names properly for DEFAULT ROLE. (MDEV-26080)

  • The innochecksum utility reports errors for freed pages. (MDEV-25361)

  • When an unknown column is referenced in the WHERE clause of a recursive CTE, the query sometimes succeeds instead of failing with an ER_BAD_FIELD_ERROR. (MDEV-26189)

  • Reusing CTE inside a function fails with the ER_NO_SUCH_TABLE error code. (MDEV-23886)

  • Several fixes for MariaDB Enterprise Cluster (Galera) SST scripts. (MDEV-20580, MDEV-25818, MDEV-25759, MDEV-25719, MDEV-15639, MDEV-15371, MDEV-18797, MENT-1170, MDEV-24979, MDEV-21192)

  • With MariaDB Enterprise Cluster, when wsrep_sst_method=mariadb-backup, MariaDB Enterprise Backup does not inherit server options set by the Environment systemd configuration parameter. (MDEV-24962)

  • With MariaDB Enterprise Cluster, when wsrep_sst_method=rsync is set and log-bin and/or log-bin-index are set to custom paths, the rsync SST does not copy the binary log index. (MDEV-25978)

As a result of this issue, a Joiner node writes the following error to the MariaDB Error Log:

tail: cannot open 'mysql-bin.index' for reading: No such file or directory
  • With MariaDB Enterprise Cluster, when wsrep_sst_method=rsync is set, rsync for a new SST process may be killed rather than the rsync for the old SST process. (MDEV-25880)

  • With MariaDB Enterprise Cluster, the WSREP threads could write warnings about foreign keys to the MariaDB Error Log when wsrep_debug is not enabled. (MDEV-26062)

    • In prior releases, the following warning could be written to the log:InnoDB: WSREP: referenced FK check fail: Lock wait index PRIMARYtableschema.child_table`` Starting with this release, the WSREP threads will only write warnings about foreign keys to the MariaDB Error Log when wsrep_debug is enabled.

  • The CREATE INDEX statement may check the wrong maximum column length. (MDEV-26203)

  • The Spider storage engine handles ">=" as ">" in some cases, where multi-column indexes are used. (MDEV-25985)

  • The max_password_errors system variable does not work correctly with the ed25519 authentication plugin. (MDEV-25641)

  • The "Condition pushdown into derived table" optimization cannot be applied if the expression being pushed refers to a derived table column which is computed from an expression that has a stored function call, @session variable reference, or other similar construct. (MDEV-25969)

  • A query that uses ORDER BY .. LIMIT clause and "Range checked for each record" optimization could produce incorrect results. (MDEV-25858)

  • An aborted OPTIMIZE TABLE statement is logged in the binary log and replicates to the Replica server. (MDEV-22530)

  • EXPLAIN shows an execution plan different from the plan actually executed. (MDEV-25682)

  • EXPLAIN shows an execution plan different from actually executed. (MDEV-25682)

  • Wrong result when selecting from views, derived tables, or CTEs with the form (SELECT .. LIMIT <n>) ORDER BY .. (MDEV-25679)

  • For system-versioned tables, the SHOW INDEX statement displays the system-invisible row_end column as part of the primary key. (MDEV-16857)

  • For system-versioned tables partitioned by SYSTEM_TIME``, overflowing the partitions leads to incorrect results from [SELECT](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/data-manipulation/selecting-data/select). result ([MDEV-22247](https://jira.mariadb.org/browse/MDEV-22247))

  • For Spider tables, SELECT statements that use CASE WHEN .. THEN``can result in syntax error. ([MDEV-24760](https://jira.mariadb.org/browse/MDEV-24760))

  • For Spider tables, SELECT statements that use the JSON_EXTRACT() function in the WHERE clause can result in a syntax error. (MDEV-24517)

  • For Spider tables, UPDATE statements that call native functions using remove_str``(such as [TRIM()](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/sql-statements-and-structure/sql-statements/built-in-functions/string-functions/trim)) fail with the [ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/reference/mariadb-internals/using-mariadb-with-your-programs-api/error-codes/mariadb-error-codes-1500-to-1599/e1582) error code. ([MDEV-24020](https://jira.mariadb.org/browse/MDEV-24020))

  • For Spider tables, server-sided prepared statements (created by PREPARE and executed by EXECUTE) incorrectly turn unsigned integer literals into signed integers. (MDEV-25808)

  • For Spider tables, statements that use the JSON_REPLACE() function fail with the ER_SP_DOES_NOT_EXIST error code. (MDEV-24523)

Interface Changes

  • KEYWORDS information schema table added

  • SQL_FUNCTIONS information schema table added

  • system_versioning_asof system variable default value changed from DEFAULT to "" (empty)

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.31-13 is provided for:

  • CentOS 7 (x86_64)

  • CentOS 8 (x86_64, ARM64)

  • Debian 9 (x86_64, ARM64)

  • Debian 10 (x86_64, ARM64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 12 (x86_64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, AM64)

  • Microsoft Windows (x86_64)

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

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

Release Notes for MariaDB Enterprise Server 10.3.29-12

This twelfth release of MariaDB Enterprise Server 10.3 is a maintenance release. This release includes a variety of fixes.

MariaDB Enterprise Server 10.3.29-12 was released on 2021-06-14.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2021-2166

4.9

CVE-2021-2154

4.9

Notable Changes

  • New function ST_DISTANCE_SPHERE() calculates the spherical distance between two geometries (point or multipoint) on a sphere. (MDEV-13467)

  • Galera updated to 25.3.3

  • Issue deprecation warnings for innodb_checksum_algorithm values none, innodb, strict_none, strict_innodb (MDEV-25106)

Issues Fixed

Can result in data loss

  • ALTER TABLE fails to rename a column in InnoDB table and causes server to crash. InnoDB table is not accessible after restart. (MDEV-24763)

  • Table corruption ER_NO_SUCH_TABLE_IN_ENGINE or ER_CRASHED_ON_USAGE after ALTER on InnoDB table with foreign key. (MDEV-24532)

  • MariaDB Enterprise Backup deletes the current source file after a No space left on device error, before exiting. Only the incomplete target file is still available. (MDEV-25221)

  • Possible corruption in online ALTER TABLE for InnoDB with ROW_FORMAT=REDUNDANT (MDEV-24730)

  • DELETE HISTORY may delete current data on system-versioned table. (MDEV-25468)

Can result in a hang or crash

  • Possible hang when KILL CONNECTION or KILL QUERY is used with MariaDB Enterprise Cluster and a multi-master setup. (MDEV-18874)

  • Possible memory corruption with MariaDB Enterprise Cluster when inserting values bigger than 4096 bytes into variable-length fields (BLOB, TEXT, VARCHAR, and related types). (MDEV-24978)

  • innodb_flush_method=O_DIRECT fails on compressed tables. (MDEV-25121)

  • Server crashes in check_grant upon invoking function with userstat enabled. (MDEV-25242)

  • MariaDB Client crashes when --default-character-set) is set and --character-sets-dir is undefined. (MDEV-24879)

  • Possible Server crash when dropping a table. Only seen when using a table space per table and if the tablespace size is increased at the time of the drop. (MDEV-20648)

  • Possible server hang with InnoDB and indexed virtual columns after an error with UPDATE, INSERT, REPLACE on virtual columns. (MDEV-24786)

  • MariaDB Enterprise Cluster conflict resolution issues. (MDEV-24923)

  • Index count mismatch due to aborted FULLTEXT INDEX (MDEV-25200)

  • MariaDB Enterprise Cluster node crashes when inserting a row into a table that contains a virtual column and does not have a primary key. (MDEV-25047)

  • Server crashes when InnoDB fails to add a new index on a new virtual column and a concurrent connection executes a query that accesses the freed virtual column. (MDEV-24971)

  • EXISTS subquery with correlation in ON expression crashes. (MDEV-25407)

  • Server crashes in row_undo_mod_clust_low upon rollback of read-only transaction. (MDEV-25457)

  • Server crashes on the second execution of a stored procedure when the stored procedure uses an invalid multi-table UPDATE statement to update a view. (MDEV-24823)

  • InnoDB startup hangs when a recovered transaction exists for the mysql.innodb_index_stats or innodb-system-variables/#innodb_table_stats|mysql.innodb_table_stats system tables and a DDL transaction needs to be rolled back. (MDEV-25503)

  • Server crashes when InnoDB tries to fetch data from table containing a FULLTEXT INDEX and the table's tablespace was discarded. (MDEV-25536)

  • Server crashes on SHOW TABLES when a WHERE condition references a derived table. (MDEV-21603)

  • Potential hang in InnoDB purge when virtual indexed columns exist. (MENT-1203)

  • After DROP INDEX or CREATE INDEX, change buffer entries for secondary indexes are lost on InnoDB restart. (MENT-1217)

  • Crashes with nested table value constructors. (MDEV-22786)

  • Server crashes when an aggregate function is called on a table value constructed with the VALUES() or VALUE() functions. (MDEV-24919)

  • Server crashes when a SELECT statement has a subquery that references a table value constructed with the VALUES() or VALUE() functions. (MDEV-24910)

  • Server crashes when a SELECT statement has an IN() clause that references the UNION of two table values constructed with the VALUES() or VALUE() functions. (MDEV-24840)

Possible memory corruption or crash if a table definition is evicted from the cache during a transaction commit. (MDEV-24811)

  • Server crashes when the DEFAULT() function is called on a BLOB column. (MDEV-22703, MDEV-24958, MDEV-24942)

  • Server crashes when a SELECT statement queries an Information Schema table and uses a JOIN (MDEV-24929)

  • Server crashes in optimize_schema_tables_memory_usage after SELECT from information_schema.innodb_sys_columns (MDEV-24868)

  • Server crashes when a FULLTEXT INDEX is added to an InnoDB table and the tablespace for the table was previously discarded. (MDEV-25070)

  • Server crashes when the optimizer incorrectly removes a GROUP BY from a subquery, because the column is specified in both the SELECT list and the GROUP BY list. (MDEV-24925)

  • Server crashes when a SELECT statement has a subquery in the FROM clause that contains a GROUP BY clause and multiple indexes are used: one index is used to resolve the GROUP BY clause and another index is used for the LATERAL DERIVED optimization. (MDEV-23723)

  • MariaDB Enterprise Cluster conflict resolution issues. (MDEV-24892)

Can result in unexpected behavior

  • SUM column from a derived table returns invalid values. (MDEV-23291)

  • CAST('0e1111111111' AS DECIMAL(38,0)) returns an incorrect result. (MDEV-24790)

  • Incorrect behavior of SET STATEMENT when it is executed as a prepared statement. (MDEV-24860)

  • Query returns a ER_BAD_FIELD_ERROR error when a subquery contains a JOIN with an ON clause that references an outer column. (MDEV-25002)

  • Query returns a ER_BAD_FIELD_ERROR error when a Common Table Expression (CTE) contains a UNION (MDEV-24597)

  • Query returns wrong result when the MIN() or MAX() aggregate functions are used and the aggregated column is indexed. (MDEV-25112)

  • Wrong result (extra rows and wrong values) with incremental block nested loop hash. (MDEV-21104)

  • Query returns wrong results when a JOIN is evaluated using the Block Nested Loop Hash (BLNH) optimization with a compound index. (MDEV-24767)

  • Server fails to start using mysqld_multi with mysqld_safe options. (MDEV-21039)

  • Duplicate key may be generated during MariaDB Enterprise Cluster configuration change. (MDEV-24853)

  • State snapshot transfer (SST) for MariaDB Enterprise Cluster using MariaDB Enterprise Backup fails when the --log-bin option was set on the command-line with no value at server startup. (MDEV-24903)

  • Race condition between persistent statistics and RENAME TABLE or TRUNCATE (MDEV-25051)

  • Race condition between ANALYZE TABLE and STATS_AUTO_RECALC (MDEV-10682)

  • Incorrect message about field length is written to the error log when CHECK TABLE is executed on an InnoDB table. (MDEV-24748)

  • No error is returned when the optimizer removes a redundant part of a subquery that contains an unknown table alias. For example, if the optimizer removes a redundant GROUP BY clause from an IN() subquery, unknown table aliases in the redundant part are ignored. (MDEV-23449)

  • Selectivity shown with EXPLAIN in field "filter" is incorrect for BIT columns. (MDEV-22583)

  • Histogram statistics are used even with optimizer_use_condition_selectivity=3 (MDEV-19474)

  • EXPLAIN shows nonsensical value for key_len with type=index (MDEV-11172)

  • SSL connection fails when server and client certs are signed by same CA. (MDEV-23740)

  • Wrong function name in error messages upon ST_GeomFromGeoJSON call. (MDEV-25272)

  • MariaDB Enterprise Backup fails --prepare on large backup. (MDEV-24197)

  • State snapshot transfer (SST) for MariaDB Enterprise Cluster using MariaDB Enterprise Backup fails when the password for the backup user is set via the MYSQL_PWD environment variable. (MDEV-25321)

  • State snapshot transfer (SST) for MariaDB Enterprise Cluster using MariaDB Enterprise Backup fails when the --innodb option was set on the command-line at server startup. (MDEV-25328)

  • An extra warning is returned when the EXPLAIN EXTENDED statement is executed in a prepared statement. (MDEV-25108)

  • Complex query in stored procedure returns wrong results. (MDEV-25182)

  • ALTER TABLE wrongly checks for field's default value if AFTER is used. (MDEV-25403)

  • Incorrect name resolution for subqueries in ON expressions. (MDEV-25362)

  • When FLUSH LOGS is executed, a race condition between InnoDB group commit and binary log rotation causes the old binary log file to become obsolete before the InnoDB group commit has been written to it. (MDEV-24526)

  • MariaDB Enterprise Backup logs an error instead of a warning when it reads an invalid log block checksum during a --backup. (MDEV-25456)

  • Rows are wrongly omitted when an InnoDB index is read using Multiversion Concurrency Control (MVCC). (MDEV-25459)

  • SELECT aborts after failed REPLACE into table with virtual column. (MDEV-24583)

  • InnoDB fails to fetch index type when index mismatch happens. (MDEV-22928)

  • MariaDB Enterprise Cluster silently enables InnoDB Monitor output and never disables it when a wsrep slave thread tries to perform a brute-force (BF) kill, but fails due to a long lock wait. (MDEV-25319)

  • RENAME TABLE causes "Ignoring data file ... with space ID xxxx, since the redo log references ... with space ID xxxx." for MariaDB Enterprise Backup. (MDEV-25568)

  • The Replication Heartbeat binary log event (Heartbeat_log_event) uses 4 bytes to store the log position within the current binary log file, so the log position overflows when the binary log file size exceeds 4 GB. (MDEV-16146)

  • InnoDB spatial indexes miss large geometry fields. (MENT-1205)

  • Table alias from previous statement interferes with later commands. (MENT-1200)

  • MariaDB Enterprise Cluster fails to replicate SET PASSWORD statement when strict_password_validation is enabled. (MDEV-25258)

  • EXPLAIN statement does not show details about sub-queries when the primary table is a table value constructed with the VALUES() or VALUE() functions. (MDEV-24936)

  • JOIN of a materialized derived table returns wrong result when the split_materialized optimization is enabled. (MDEV-25128)

  • Uninitialized value upon CREATE .. SELECT .. VALUE and variety of resulting errors with different engines. (MDEV-24710)

  • Dropping primary key column from a system-versioned table always fails with Error 1072. (MDEV-24690)

  • ALTER TABLE .. ADD COLUMN .. AS ROW START returns misleading ER_VERS_DUPLICATE_ROW_START_END error. (MDEV-25172)

  • Unexpected ER_DUP_ENTRY error when the Primary Key column is dropped from a system-versioned table. (MDEV-25327)

  • slave_compressed_protocol doesn't work properly with semi-sync replication. (MDEV-24773)

  • Sequence created by one connection remains invisible to another. (MDEV-24545)

  • routine_definition in |information_schema.routines loses tablename if it starts with an _ and is not backticked. (MDEV-25501)

  • JOIN of a derived table using an aggregation function returns incorrect results. (MENT-1210)

  • CREATE PROCEDURE / DROP PROCEDURE not logged with MariaDB Audit Plugin. (MDEV-23457)

Related to install and upgrade

  • Missing libsepol dependency on SLES 12 and SLES 15. (MENT-1163)

  • caching_sha2_password.so isn't included in Debian packages. (MDEV-24728)

  • Minor version upgrade does not perform server restart. (MDEV-25240)

Interface Changes

  • mariadb-backup --innodb-force-recovery command-line option added

  • mariadb_repo_setup skip-check-installed command-line option added

  • ST_DISTANCE_SPHERE function added

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.3.29-12 is provided for:

  • CentOS 7

  • CentOS 8

  • Debian 9

  • Debian 10

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 8

  • SUSE Linux Enterprise Server 12

  • SUSE Linux Enterprise Server 15

  • 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".

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

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-2021-27928

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

  • SHOW GRANTS is missing the WITH GRANT privilege for roles. (MDEV-24289)

  • mysqld_safe log messages are missing in the error log file. (MDEV-21367)

  • CHECK_CLAUSE field in INFORMATION_SCHEMA.CHECK_CONSTRAINTS truncates check constraints expressions. (MDEV-24139)

  • Unexpected error message when selecting from view that uses mergeable derived table. (MDEV-24314)

  • Permission denied error message is returned on users with SELECT permissions for nested CTEs. (MDEV-20751)

  • Regression: SELECT .. UNION .. with inconsistent column names fails. (MDEV-19179)

  • Race condition between KILL and transaction commit with MariaDB Enterprise Cluster. (MDEV-23536)

  • Plugin system variables and activation options can break mysqld --wsrep_recover for MariaDB Enterprise Cluster. (MDEV-20717)

  • SELECT INTO OUTFILE used permission 666 where 644 should be used to limit the privileges to change the file. (MDEV-23875)

  • Syntax error on correct syntax for CREATE VIEW that includes X is null = 0 (MDEV-24194)

  • Altered connection limits for user have no effect. (MDEV-17852)

  • Syntax error when using COLLATEfor creating virtual columns. (MDEV-12161)

  • Auto purge of relaylogs stops when relay-log-file is slave-relay-log.999999 and slave_parallel_threads is enabled. (MDEV-8134)

  • ORDER BY in view definition leads to wrong result with GROUP BY on query using view. (MDEV-23826)

  • SUM column from a derived table returns invalid values. (MDEV-23291)

  • mariadb-audit-plugin-options-and-system-variables#server_auditserver_audit doesn't respect filters for PROXY_CONNECT events. (MDEV-24318)

  • mariadb-audit-plugin-options-and-system-variables#server_auditserver_audit plugin doesn't consider proxy users in server_audit_excl_users and server_audit_incl_users (MDEV-19442)

  • With ALTER USER .. IDENTIFIED BY command, password isn't replaced by asterisks in audit log. (MENT-1128)

  • Queries against Spider tables return wrong values for columns following constant declarations. Fix backported from 10.4.13 (MDEV-20502)

  • UPDATE does not insert history row for system versioned or application period based tables if the row has not changed. (MDEV-23446)

  • Wrong duplicate primary key error between the history row generated on referential action and the history row on evaluating foreign referential action for self-reference in a system versioned table (MDEV-21138, MDEV-23644)

  • Wrong number of decimal digits in certain UNION or subquery constellations, like union of unsigned and NULL type. (MDEV-24387)

  • CREATE TABLE .. SELECT FROM does not create table if VALUE() is not using a scalar value (MDEV-24618)

  • InnoDB may report incorrect binlog position information after RESET MASTER (MDEV-22351)

  • Sequences which are used as default by a table are not dumped in right order by mysqldump (MDEV-21785)

Related to install and upgrade

  • mysql_upgrade fails with error messages ALGORITHM=INSTANT is not supported for this operation (MDEV-16735)

Interface Changes

  • accounts performance schema table schema changed

  • CHECK_CONSTRAINTS information schema table schema changed

  • events_stages_summary_by_account_by_event_name performance schema table schema changed

  • events_stages_summary_by_user_by_event_name performance schema table schema changed

  • events_statements_summary_by_account_by_event_name performance schema table schema changed

  • events_statements_summary_by_user_by_event_name performance schema table schema changed

  • events_waits_summary_by_account_by_event_name performance schema table schema changed

  • events_waits_summary_by_user_by_event_name performance schema table schema changed

  • group_concat_max_len system variable maximum value changed from 18446744073709551615 to 4294967295

  • mariadb-backup --log-innodb-page-corruption command-line option added

  • mariadb_es_repo_setup --include-unsupported command-line option added

  • mariadb_es_repo_setup --skip-check-installed command-line option added

  • mariadb_es_repo_setup --version command-line option added

  • mariadb_repo_setup --version command-line option added

  • max_sort_length system variable minimum value changed from 8 to 64

  • mysqldump --system command-line option added

  • setup_actors performance schema table schema changed

  • threads performance schema table schema changed

  • users performance schema table schema changed

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.

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 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 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)

  • 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 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)

  • 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 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 lack of 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 foreign key and a virtual column in 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 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 data-directory has 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 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)

  • 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 compound primary key on partitioned table. (MENT-997)

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

  • 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)

  • 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 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-system-variables/#innodb_log_optimize_ddlinnodb_log_optimize_ddl system variable default value changed from ON to OFF

  • innodb_max_purge_lag_wait system variable 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.

Release Notes for MariaDB Enterprise Server 10.3.25-9

This ninth release of MariaDB Enterprise Server 10.3 is a hotfix release to address a CVE which has been rated "critical" using the criteria defined in the MariaDB Engineering Policy.

MariaDB Enterprise Server 10.3.25-9 was released on 2020-10-07.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2020-15180

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.

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.25-9 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|

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

Release Notes for MariaDB Enterprise Server 10.3.24-8

This eighth release of MariaDB Enterprise Server 10.3 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.3.24-8 was released on 2020-09-08.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2021-2022

4.4

Notable Changes

  • Limit innodb_encryption_threads to 255 (MDEV-22258)

  • Minimum value of max_sort_length raised to 8 (previously 4) so fixed size data types like DOUBLE and BIGINT are not truncated for lower values of max_sort_length. (MDEV-22715)

  • Backport from MariaDB Server 10.5.4 improvements to DROP TABLE for InnoDB. (MENT-636)

  • Backport option tls_version from MariaDB Server 10.4. (MENT-581)

Issues Fixed

Can result in data loss

  • InnoDB doublewrite recovery can corrupt data pages. (MDEV-11799)

  • InnoDB table can disappear when trying to change primary key after disabling Foreign Key checks and violating a Foreign Key constraint. (MENT-804)

  • InnoDB corruption in delete buffering. (MDEV-22497)

  • Rollback of insert fails when column reorder happens. (MDEV-22637)

  • Possible data inconsistency when executing ADD PRIMARY KEY with concurrent DML transactions. (MDEV-23244)

Can result in a hang or crash

  • InnoDB deadlock in FLUSH TABLES .. FOR EXPORT (MDEV-22890)

  • InnoDB data file extension is not crash-safe. (MDEV-23190)

  • innodb_log_optimize_ddl=OFF is not crash safe. (MDEV-21347)

  • Deadlock involving parallel workers, STOP SLAVE, and FLUSH TABLES WITH READ LOCK (MDEV-23089)

  • Crashes when running a SQL query containing a specific subquery pattern. (MDEV-23221)

  • Dropping the adaptive hash index may cause DDL to lock up InnoDB. (MDEV-22456)

  • RESET MASTER TO could result in a crash, when the value exceeds the max allowed 2147483647 (MDEV-22451)

  • Crash on WITH RECURSIVE large query. (MDEV-22748)

  • Crash with Prepared Statement with a ? parameter inside a re-used CTE. (MDEV-22779)

  • MariaDB could crash after changing the query_cache size. (MDEV-5924)

  • Crash in CREATE TABLE AS SELECT when the precision of returning type = 0 (MDEV-22502)

  • ENUM or SET in a CREATE TABLE statement which has a 0x00 byte in one of the values could crash the server. (MDEV-22111)

  • InnoDB recovery can block server startup. (MENT-915)

Can result in unexpected behavior

  • Service shutdown fails if OS datetime has been updated backwards. (MDEV-17481)

  • ALTER TABLE .. ANALYZE PARTITION can run for hours for huge tables if engine-independent persistent statistics are enabled, due to reading and locking of all rows in the InnoDB table instead of for the partition. (MDEV-21472)

  • UPDATE can fail with privilege error when UPDATE privilege exists at database level but SELECT privilege exists at table level. (MDEV-23010)

  • Latency and throughput regression identified in write-heavy benchmarks for latest releases in MariaDB Server 10.2, 10.3, and 10.4. (MENT-909)

  • START SLAVE UNTIL .. file .. pos stops at an earlier position earlier than defined if the transaction that spans over the given stop position has to roll back due to conflicts. (MDEV-15152)

  • mariadb-backup --prepare does not stop on errors while applying InnoDB redo log. (MDEV-22354)

  • Point in time recovery of binary log fails with syntax error when sql_mode=ORACLE. (MDEV-23108)

  • Replication aborts with ER_SLAVE_CONVERSION_FAILED upon CREATE .. SELECT when sql_mode=ORACLE. (MDEV-19632)

  • Regression in Audit Plugin Performance. (MENT-700)

Related to install and upgrade

  • UNINSTALL PLUGIN and UNINSTALL SONAME can't run if the library file doesn't exist. (MDEV-21258)

  • Spider plugin install hangs installation process. (MENT-926)

Interface Changes

  • mariadb-backup --tls-version command-line option added

  • max_sort_length system variable minimum value changed from 4 to 8

  • mysql_upgrade --tls-version command-line option added

  • mysql --tls-version command-line option added

  • mysqladmin --tls-version command-line option added

  • mysqlbinlog --tls-version command-line option added

  • mysqlcheck --tls-version command-line option added

  • mysqld --tls-version command-line option added

  • mysqldump --tls-version command-line option added

  • mysqlimport --tls-version command-line option added

  • mysqlshow --tls-version command-line option added

  • mysqlslap --tls-version command-line option added

  • tls-version system variable added

* Platforms

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

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

Release Notes for MariaDB Enterprise Server 10.3.23-7

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

CVE-2020-2760

5.5

CVE-2020-2752

5.3

CVE-2020-2814

4.9

CVE-2020-2812

4.9

CVE-2020-13249

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 the mysql.slave_master_info and mysql.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)

  • mariadb-backup has a new --rollback-xa option. By default, mariadb-backup 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_thread is now limited to 255. (MDEV-22258)

  • 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_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_last to allow an instant ADD COLUMN as the last column of the table. Option never 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_dirs configuration from the server configuration file. (MDEV-19347)

  • 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_aux_table, iinnodb_ft_server_stopword_table, innodb_ft_user_stopword_table , and innodb_buffer_pool_filename could lead to corrupted strings for the settings. (MDEV-22393)

  • 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 of Delete history (MDEV-20382)

  • Wrong query results have been returned with optimizer_switch="split_materialized=on" (MDEV-21614)

  • 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_threads system variable maximum value changed from 4294967295 to 255

  • innodb_instant_alter_column_allowed system variable added

  • mariadb-backup --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_for_slaves system variable added

Platforms

In alignment with 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.

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

Release Notes for MariaDB Enterprise Server 10.3.22-6

This sixth release of MariaDB Enterprise Server 10.3 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.3.22-6 was released on 2020-03-02.

Fixed Security Vulnerabilities

CVE (with cve.org link)

* CVSS base score

CVE-2020-2574

5.9

Notable Changes

  • The systemd start and stop timeout for the MariaDB service is now set to 900 seconds (15 minutes). (MDEV-17571)

  • For MariaDB Enterprise Cluster (Galera Library 25.3.29):

    • Setting socket.recv_buf_size was not effective because it was done after the socket was connected or accepted. The default value also caused TCP receive buffer auto-tuning to be disabled. This lead to sub-optimal performance in high bandwidth WAN clusters. The default value for socket.recv_buf_size has been changed to auto, which lets the kernel tune the TCP receive buffer. A new variable socket.recv_buf_size with default value auto was added to allow send buffer tuning.

Issues Fixed

Can result in a hang or crash

  • During a server restart InnoDB recovery could encounter an out-of-memory condition. A restart was only possible after increasing innodb_buffer_pool_size . (MDEV-19176)

  • On a rollback of a large insert or update, or during a background task to purge transaction history after a large update or delete, the server could hang. (MDEV-21509)

  • On a rollback or during a background task to purge transaction history due to a SPATIAL INDEX, the server could hang. (MDEV-21512)

  • Crashes could occur rarely when using ALTER TABLE ... IMPORT TABLESPACE (MDEV-21513)

  • Possible server crash if binlog_checksum=CRC32 (default) is set and if the value for parameter pos in SHOW BINLOG EVENTS FROM pos does not point to the beginning of an event in the binary log. (MDEV-18046)

  • A replication primary (master) running in semi-sync mode could crash when RESET MASTER is executed and the replica reconnects using the GTID protocol. (MDEV-19376)

  • MariaDB Enterprise Backup could encounter a deadlock if a backup is taken from a replica with slave-parallel-threads is set to a value greater than 0 (MDEV-21255)

  • MariaDB Enterprise Backup could crash when used in combination with FLUSH TABLES``and``UNLOCK TABLES``(MENT-438)

  • The aria_pack utility crashed when running an offline datafile compress on a table. (MDEV-14183)

  • Dropping a partition with wsrep_OSU_method=RSU and SESSION sql_log_bin=0 caused the MariaDB Enterprise Cluster (Galera) node to hang. (MDEV-21189)

  • With active optimizer trace (optimizer_trace='enabled=on') server could crash or the data of the optimizer trace could become corrupted. (MENT-614)

Can result in unexpected behavior

  • Executing TRUNCATE or OPTIMIZE on InnoDB tables could lead to an unexpected SQL Error (1118): Row size too large, when innodb_strict_mode=ON (default). (MDEV-21429)

  • Queries which use window functions and implicit grouping could return wrong results. (MDEV-21318)

  • Queries which use DISTINCT COUNT(*) OVER() in the expression returned wrong results. (MDEV-16579)

  • Inefficient thread handling in the thread pool, impacting any application that uses the thread pool. (MDEV-21343)

  • The MariaDB Enterprise Server config file mariadb-enterprise.cnf was not registered as a config file in RPM packages. (MENT-591)

  • ALTER USER IF EXISTS generated a SQL syntax error. (MENT-643)

  • A query using GROUP BY with an expression containing a field of a view could return wrong results. (MDEV-20922)

  • Running the script mysql_tzinfo_to_sql for MariaDB Enterprise Cluster could result in inconsistent timezone information across different nodes. (MDEV-21209)

  • Using the --use-memory option with mariadb-backup would cause it to run out of memory. (MDEV-20679)

  • For MariaDB Enterprise Cluster (Galera Library 25.3.29):

    • GCS delivered a JOIN message even if the node was in a DONOR state.

    • GCache could contain mixed histories from different clusters.

    • GComm socket timestamping/liveness checking produced false positives during replication of large transactions, which caused excessive amounts of broken connections.

    • Large transactions were able to monopolize bandwidth when segmentation was configured, causing delayed in messages relayed by segment representative. The fix implements fair queuing of messages.

    • Due to a bug in quorum computation, two primary conflicting primary components were formed when the group merged and partitioned again while the new primary view was forming.

  • A range plan was not always used for multi-join queries. (MDEV-21383)

Related to installation or upgrade

  • Server could not be started when lc_messages is set in a config file. (MENT-625)

Interface Changes

  • None

Platforms

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

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

Release Notes for MariaDB Enterprise Server 10.3.21-5

This sixth release of MariaDB Enterprise Server 10.3 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.3.22-6 was released on 2020-03-02.

Fixed Security Vulnerabilities

CVE (with cve.org link)

* CVSS base score

CVE-2020-2574

5.9

Notable Changes

  • The systemd start and stop timeout for the MariaDB service is now set to 900 seconds (15 minutes). (MDEV-17571)

  • For MariaDB Enterprise Cluster (Galera Library 25.3.29):

    • Setting socket.recv_buf_size was not effective because it was done after the socket was connected or accepted. The default value also caused TCP receive buffer auto-tuning to be disabled. This lead to sub-optimal performance in high bandwidth WAN clusters. The default value for socket.recv_buf_size has been changed to auto, which lets the kernel tune the TCP receive buffer. A new variable socket.recv_buf_size with default value auto was added to allow send buffer tuning.

Issues Fixed

Can result in a hang or crash

  • During a server restart InnoDB recovery could encounter an out-of-memory condition. A restart was only possible after increasing innodb_buffer_pool_size . (MDEV-19176)

  • On a rollback of a large insert or update, or during a background task to purge transaction history after a large update or delete, the server could hang. (MDEV-21509)

  • On a rollback or during a background task to purge transaction history due to a SPATIAL INDEX, the server could hang. (MDEV-21512)

  • Crashes could occur rarely when using ALTER TABLE ... IMPORT TABLESPACE (MDEV-21513)

  • Possible server crash if binlog_checksum=CRC32 (default) is set and if the value for parameter pos in SHOW BINLOG EVENTS FROM pos does not point to the beginning of an event in the binary log. (MDEV-18046)

  • A replication primary (master) running in semi-sync mode could crash when RESET MASTER is executed and the replica reconnects using the GTID protocol. (MDEV-19376)

  • MariaDB Enterprise Backup could encounter a deadlock if a backup is taken from a replica with slave-parallel-threads is set to a value greater than 0 (MDEV-21255)

  • MariaDB Enterprise Backup could crash when used in combination with FLUSH TABLES``and``UNLOCK TABLES``(MENT-438)

  • The aria_pack utility crashed when running an offline datafile compress on a table. (MDEV-14183)

  • Dropping a partition with wsrep_OSU_method=RSU and SESSION sql_log_bin=0 caused the MariaDB Enterprise Cluster (Galera) node to hang. (MDEV-21189)

  • With active optimizer trace (optimizer_trace='enabled=on') server could crash or the data of the optimizer trace could become corrupted. (MENT-614)

Can result in unexpected behavior

  • Executing TRUNCATE or OPTIMIZE on InnoDB tables could lead to an unexpected SQL Error (1118): Row size too large, when innodb_strict_mode=ON (default). (MDEV-21429)

  • Queries which use window functions and implicit grouping could return wrong results. (MDEV-21318)

  • Queries which use DISTINCT COUNT(*) OVER() in the expression returned wrong results. (MDEV-16579)

  • Inefficient thread handling in the thread pool, impacting any application that uses the thread pool. (MDEV-21343)

  • The MariaDB Enterprise Server config file mariadb-enterprise.cnf was not registered as a config file in RPM packages. (MENT-591)

  • ALTER USER IF EXISTS generated a SQL syntax error. (MENT-643)

  • A query using GROUP BY with an expression containing a field of a view could return wrong results. (MDEV-20922)

  • Running the script mysql_tzinfo_to_sql for MariaDB Enterprise Cluster could result in inconsistent timezone information across different nodes. (MDEV-21209)

  • Using the --use-memory option with mariadb-backup would cause it to run out of memory. (MDEV-20679)

  • For MariaDB Enterprise Cluster (Galera Library 25.3.29):

    • GCS delivered a JOIN message even if the node was in a DONOR state.

    • GCache could contain mixed histories from different clusters.

    • GComm socket timestamping/liveness checking produced false positives during replication of large transactions, which caused excessive amounts of broken connections.

    • Large transactions were able to monopolize bandwidth when segmentation was configured, causing delayed in messages relayed by segment representative. The fix implements fair queuing of messages.

    • Due to a bug in quorum computation, two primary conflicting primary components were formed when the group merged and partitioned again while the new primary view was forming.

  • A range plan was not always used for multi-join queries. (MDEV-21383)

Related to installation or upgrade

  • Server could not be started when lc_messages is set in a config file. (MENT-625)

Interface Changes

  • None

Platforms

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

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

Release Notes for MariaDB Enterprise Server 10.3.20-4

Release Notes for MariaDB Enterprise Server 10.3.20-4

This fourth release of MariaDB Enterprise Server 10.3 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.3.20-4 was released on 2019-11-18.

Fixed Security Vulnerabilities

CVE (with cve.org link)
CVSS base score

CVE-2020-2780

6.5

CVE-2019-2974

6.5

CVE-2019-2938

4.4

Notable Changes

  • New option innodb_change_buffer_dump added to Debug builds. This option dumps the contents of the InnoDB change buffer to the server error log at startup. This is useful when a slow shutdown cannot be performed successfully. (MDEV-20864)

  • Eliminated unnecessary logging of warnings to the error log regarding InnoDB maximum row size for DML statements which should be present only for DDL operations. (MENT-454)

Issues Fixed

Can result in data loss

  • mariadb-backup --prepare --export ... could overwrite binary logs if certain conditions were present. (MDEV-20703) Conditions which must be present to trigger this bug:

    • mariadb-backup is executed on the MariaDB Server host, and

    • Configuration files from the master are used, and

    • Configuration files enable binary logging

  • If unable to upgrade to MariaDB Enterprise Server 10.3.20-4, where this bug is fixed, a workaround is available: use the --defaults option to mariadb-backup to avoid the bug-triggering conditions by specifying a different configuration file.

Can result in a hang or crash

  • Prior removal of a `#FULLTEXT

index from an InnoDB table can cause a hang on startup. (MDEV-19647)`

  • Removal of a `#FULLTEXT

index from an InnoDB table can cause a hang. (MDEV-19529)`

  • Change to a InnoDB table containing a `#FULLTEXT

index can cause Server to become unresponsive. (MDEV-20987)`

  • Removal of a virtual column used by an index can result in a crash. (MENT-434)

  • CREATE INDEX, ALTER TABLE , or OPTIMIZE TABLE on an InnoDB table can cause Server to become unresponsive. (MDEV-20852)

  • INSTANT ADD COLUMN on an InnoDB table which includes a FOREIGN KEY definition can result in a crash. (MENT-435)

Can result in unexpected behavior

  • Unnecessary logging of warnings to the error log regarding InnoDB maximum row size for DML statements which should be present only for DDL operations. (MENT-454)

  • After server restart, a SELECT using a `#FULLTEXT

index on InnoDB tables can fail to return some data. (MDEV-19073)`

  • MariaDB Enterprise Backup and MariaDB Backup, when using mbstream, recreated xtrabackup_info in the same directory as the backup file. Repeated extract of the backup could fail. (MDEV-18438)

  • mysqld_multi.sh script could not be launched and returned a syntax error. (MENT-433)

  • Though not supported on Microsoft Windows, the server_audit_output_type system variable for the Audit plugin accepted a SYSLOG value. (MDEV-19851)

  • FOREIGN KEY constraints have been ignored during DELETE when parent table is System-Versioned. (MDEV-16210)

  • DELETE from child table with FOREIGN KEY was not possible when the table is System-Versioned. (MDEV-20812)

Related to install and upgrade

  • Installing MariaDB Enterprise Server from repository failed on CentOS 7 due to package dependencies. (MENT-420)

Interface Changes

  • WARN_INNODB_PARTITION_OPTION_IGNORED error code added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.20-4 is provided for:

  • CentOS 8

  • CentOS 7

  • CentOS 6

  • Debian 10

  • Debian 9

  • Debian 8

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 6

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 12

  • Ubuntu 18.04

  • Ubuntu 16.04

  • 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.

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

Release Notes for MariaDB Enterprise Server 10.3.18-3

This third release of MariaDB Enterprise Server 10.3 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.3.18-3 was released on 2019-09-30.

Issues Fixed

Can result in data loss

  • Due to a race condition in InnoDB, an exclusive lock to an inserted record could be wrongly granted to multiple transactions when the INSERT transaction commits. This could lead to a server crash or data loss. (MDEV-15326)

  • INSERT...ON DUPLICATE KEY UPDATE, when there is more than one key, could result in inconsistent data between master and slave for replication mode MIXED and STATEMENT. This has been fixed for MIXED, but cannot be controlled by the replication for STATEMENT based replication.

  • Inconsistent Slaves need to be set up again from the Master. (MDEV-17614)

  • Wrong value on instantly added column can occur after DELETE and a following UPDATE of PRIMARY KEY. (MDEV-20066)

Can result in a hang or crash

  • Replication could hang for InnoDB transactions as InnoDB has its own concurrency control innodb_thread_concurrency. (MDEV-20247)

  • Fix potential crash in ON UPDATE CASCADE when the foreign table is system versioned. (MDEV-20311)

Can result in unexpected behavior

  • After setting SET foreign_key_checks=0 it is possible to drop indexes from referenced (parent) tables, which could cause InnoDB to behave as if table doesn't exist in engine (MDEV-17187)

  • Fix for corner case where MariaDB Backup could fail because encrypted data files could not be copied if created shortly before the backup was started. (MDEV-18128)

  • MariaDB Backup could fail in the prepare face if the redo log is bigger than 512GB. (MDEV-20060)

  • Basic 3-way join queries are not parsed. (MDEV-19421)

Related to performance

  • Optimized scanning of the undo log versions while scanning the secondary index versions. (MDEV-20301)

Interface Changes

  • in_predicate_conversion_threshold system variable added

  • mysqld --in-predicate-conversion-threshold command-line option added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.18-3 is provided for:

  • CentOS 8

  • CentOS 7

  • CentOS 6

  • Debian 10

  • Debian 9

  • Debian 8

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 6

  • Ubuntu 18.04

  • Ubuntu 16.04

  • 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.

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

Release Notes for MariaDB Enterprise Server 10.3.17-2

This second release of MariaDB Enterprise Server 10.3 is a maintenance release, addressing security vulnerabilities and including a variety of fixes.

MariaDB Enterprise Server 10.3.17-2 was released on 2019-08-19.

Fixed Security Vulnerabilities

CVE (with cve.org link)

CVSS base score

CVE-2019-2805

6.5

CVE-2019-2740

6.5

CVE-2019-2758

5.5

CVE-2019-2739

5.1

CVE-2019-2737

4.9

CVE-2021-2007

3.7

CVE-2020-2922

3.7

Notable Changes

  • Merge relevant InnoDB changes from MySQL 5.7.27

  • Compatibility change: Change innodb_log_optimize_ddl to OFF by default

  • Compatibility change: Change innodb_adaptive_hash_index to OFF by default

  • Adjust spin loops to the x86 PAUSE instruction latency

  • Merge upstream changes from MyRocks (MDEV-19795)

  • DISKS plugin now requires the FILE privilege to display information in the disks table in the information schema, the table will otherwise be empty (MDEV-18328)

Issues Fixed

  • SERVER_AUDIT does not work with PS protocol

  • Removed --rsync legacy option from enterprise build of MariaDB Backup

  • Changes to mysql_install_db script text

  • DROP TABLE IF EXISTS killed on master but was replicated (MDEV-20348)

  • Post-merge fixes for rocksdb.group_min_max test (MDEV-20113)

  • Replication hangs with "preparing" and never starts (MDEV-20247)

  • Failing assertion when REDO log files reach 512Gb while preparing backup (MDEV-20060)

  • Temporary tables created with data-at-rest encryption are not fully encrypted (MDEV-17228)

  • InnoDB bugs related to creating tables (MDEV-19292, MDEV-20102)

  • ALTER TABLE for InnoDB can result in a crash in some cases (MDEV-15641)

  • Failing tests in buildbot related to FULLTEXT INDEX (MDEV-14154)

  • Server startup bug with encrypted InnoDB table (MDEV-19914)

  • Possible crash when Galera and foreign key is used, if the referenced record is deleted at the same time (MDEV-19660)

  • Recovery with mariadb-backup crash related to InnoDB with custom innodb_data_file_path (MDEV-19978)

  • Add page-id matching check in innochecksum tool (MDEV-19871)

  • DROP TEMPORARY table is logged despite no CREATE was logged in binary log (MDEV-20091)

  • mysql_upgrade_service throws exception upgrading from 10.0 to 10.3 (MDEV-19427)

  • Loading the AUDIT plugin causes performance regression (MDEV-18661)

  • REPLACE on table with virtual_field can cause crash (MDEV-19771)

  • Fix Aria ER_CRASHED_ON_USAGE and Assertion (MDEV-19595)

  • Test change: innodb.trx_id_future fails on 10.3+ (MDEV-20138)

  • Possible foreign key corruption for ALTER TABLE ... ADD COLUMN with InnoDB (MDEV-19630)

  • Corruption after instant ADD or DROP when the index tree shrinks (MDEV-19916)

  • Cannot load compressed BLOB with InnoDB (MDEV-19974)

  • Bug in versioned tables when deleting history (MDEV-19814)

  • Compressed columns cannot be restored from dump (MDEV-17363)

  • Bugs in InnoDB related to indexed virtual columns (MDEV-16222, MDEV-17005, MDEV-19870)

Interface Changes

  • mariadb-backup --rsync option removed

  • mysqld --innodb-encrypt-temporary-tables option added

  • mysqld --rocksdb-cache-dump option added

  • mysqld --rocksdb-cache-high-pri-pool-ratio option added

  • mysqld --rocksdb-cache-index-and-filter-with-high-priority option added

  • mysqld --rocksdb-delete-cf option added

  • mysqld --rocksdb-enable-insert-with-update-caching option added

  • mysqld --rocksdb-read-free-rpl-tables option removed

  • mysqld --rocksdb-rollback-on-timeout option added

  • mysqld --rocksdb-stats-level option added

  • Innodb_encryption_n_temp_blocks_decrypted status variable added

  • Innodb_encryption_n_temp_blocks_encrypted status variable added

  • wsrep_applier_thread_count status variable added

  • wsrep_rollbacker_thread_count status variable added

  • innodb_encrypt_temporary_tables system variable added

  • rocksdb_cache_dump system variable added

  • rocksdb_cache_high_pri_pool_ratio system variable added

  • rocksdb_cache_index_and_filter_with_high_priority system variable added

  • rocksdb_delete_cf system variable added

  • rocksdb_enable_insert_with_update_caching system variable added

  • rocksdb_read_free_rpl_tables system variable removed

  • rocksdb_rollback_on_timeout system variable added

  • rocksdb_stats_level system variable added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.17-2 is provided for:

  • CentOS 7

  • CentOS 6

  • Debian 9

  • Debian 8

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 6

  • Ubuntu 18.04

  • Ubuntu 16.04

  • 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.

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

Release Notes for MariaDB Enterprise Server 10.3.16-1

This first release of MariaDB Enterprise Server 10.3 includes a variety of new features and fixes, compared to MariaDB Community Server 10.3.15.

MariaDB Enterprise Server 10.3.16-1 was released on 2019-07-08.

New Features

  • MariaDB Enterprise Backup with support of non-blocking Backups

  • Backup Stages for non-blocking Backups

  • Maximum number of secondary indexes increased to 128 per table

  • Tracing facility for the Optimizer

  • Slow master shutdown option

New Default Settings

A new Enterprise config file is provided that sets optimized defaults:

  • Server does not load plugins of maturity Beta or lower

  • Authentication plugin Ed25519 is loaded by default

  • Account root is using unix_socket by default on Linux systems

  • Accounts for root can only connect from local host

  • Accounts of type anonymous-user removed

  • Database "test" has no default grants

  • simple_password_check plugin is activated by default with settings:

    • simple_password_check_minimal_length = 8

    • simple_password_check_digits = 1

    • simple_password_check_letters_same_case = 1

    • simple_password_check_other_characters = 1

  • Audit plugin is loaded by default, but is not activated

  • DISKS plugin is loaded by default on Linux systems

Notable Changes

  • DISKS plugin, used by MariaDB MaxScale, is now of maturity stable

  • Access to data provided by DISKS plugin via the information schema requires FILE privilege

  • Unsupported Community plugins are not loaded by default

  • Embedded Server removed

  • HeidiSQL is not included in Windows installations

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.3.16-1 is provided for:

  • CentOS 7

  • CentOS 6

  • Debian 9

  • Debian 8

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 6

  • Ubuntu 18.04

  • Ubuntu 16.04

  • 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.

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