Release Notes for MariaDB Enterprise Server 10.6.9-5
MariaDB Enterprise Server 10.6.9-5 is a maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes.
MariaDB Enterprise Server 10.6.9-5 was released on 2022-09-12.
Fixed Security Vulnerabilities
CVE (with cve.org link)
CVSS base score
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:
UUIDdata type has been backported from MariaDB Community Server 10.7 for more efficient storage of UUID values. (MENT-1459)
Galera has been updated to
Debian 9 support has been discontinued.
Red Hat Enterprise Linux 9 support has been added.
Rocky Linux 9 support has been added.
OpenSSL 3.0 support has been added for MariaDB Enterprise Cluster (powered by Galera) (MDEV-25949)
Can result in data loss
mariadb-backupis executed with the
--rsynccommand-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_filenamesystem variable. (MDEV-28781)
Starting with this release,
mariadb-backuponly copies the InnoDB buffer pool dump file during State Snapshot Transfers (SSTs) for MariaDB Enterprise Cluster, powered by Galera.
Starting with this release, InnoDB sequences are properly replicated when they are defined with
Can result in a hang or crash
INSERT .. SELECT .. GROUP BYis executed and the
GROUP BYclause 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 BYclause, the server can crash. (MDEV-29139)
ALTER TABLE .. ADDis used to add a column with the
INSTANTalgorithm, the server can crash if the
.frmfile does not match the actual row format used by the data file. (MDEV-26577)
For tables created prior to MariaDB Server 10.2, the
.frmfile 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.
INSERT .. SELECTis executed and the
SELECTquery calls an aggregate or window function, the server can crash with a segmentation fault. (MDEV-26427)
When a query uses the
DISTINCTkeyword 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.
INsubquery is used outside the context of a regular query (such as in a stored procedure), the server can crash. (MDEV-22001)
When MariaDB Enterprise Cluster is used and the Galera replication TCP port receives non-Galera network traffic, the server can crash. (MDEV-25068)
In previous releases, when the crash occurred, the following messages would appear in the MariaDB error log:
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >' what(): remote_endpoint: Transport endpoint is not connected [ERROR] mysqld got signal 6 ;
When a generated column is added to an InnoDB table with the
INSTANTalgorithm, the server can crash due to a buffer overflow. (MDEV-26420)
CREATE VIEWis executed with a view definition that contains an unknown column in an
ONcondition, the server can crash instead of raising an error with the
ER_BAD_FIELD_ERRORerror code. (MDEV-29088)
Can result in unexpected behavior
INcondition contains a mixture of numeric and string values, results can be inconsistent. (MDEV-21445)
When a transaction can't be fully written to the binary log, but the transaction can be safely rolled back, a
LOST_EVENTSincident 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_EVENTSincident 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 table is created from a
SELECTstatement 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_modeis raised with the
ER_WARN_DATA_OUT_OF_RANGEerror code and the following error message:
Out of range value for column 'COLUMN_NAME' at row ROW_NUM
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)
FULLTEXTsearch is performed on an InnoDB table, the results are incorrect when the search term contains an apostrophe (
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.
In previous releases, the following error could be raised:
ERROR 1845 (0A000): ALGORITHM=NOCOPY is not supported for this operation. Try ALGORITHM=INPLACE
Table elimination is used when the query performs a JOIN and has
When a replica server is replicating from a primary server that is too old to write
explicit_defaults_for_timestampto the binary log, the replica server ignores its own value and assumes that the value should be
Starting with this release, the replica server determines an optimal value for
explicit_defaults_for_timestampbased on the version of the primary server. If the primary server is too old to write its value to the binary log, the replica server uses its own value.
In previous releases, when the backup failed, the output could contain messages like the following:
[ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace: ./DATABASE_NAME/TABLE_NAME.ibd uses space ID: SPACE_ID. Cannot open filepath: DATABASE_NAME/TABLE_NAME.ibd which uses the same space ID. [Warning] InnoDB: We do not continue the crash recovery, because the table may become corrupt if we cannot apply the log records in the InnoDB log to it. To fix the problem and start mariadbd: [Note] InnoDB: 1) If there is a permission problem in the file and mysqld cannot open the file, you should modify the permissions. [Note] InnoDB: 2) If the tablespace is not needed, or you can restore an older version from a backup, then you can remove the .ibd file, and use --innodb_force_recovery=1 to force startup without this file. [Note] InnoDB: 3) If the file system or the disk is broken, and you cannot remove the .ibd file, you can set --innodb_force_recovery. mariadb-backup: srv_start() returned 11 (Generic error).
In previous releases, the output could contain many messages like the following:
DDL tracking : modify SPACE_ID "./DATABASE_NAME/TABLE_NAME.ibd"
Changes in Storage Engines
This release originally incorporated MariaDB ColumnStore storage engine version 22.08.1.
This release previously incorporated MariaDB ColumnStore storage engine version 22.08.2.
This release previously incorporated MariaDB ColumnStore storage engine version 22.08.3.
This release now incorporates MariaDB ColumnStore storage engine version 22.08.4.
cmapi_system variable added host
cmapi_system variable added key
cmapi_system variable added port
cmapi_system variable added version
s3_system variable added key
s3_system variable added region
s3_system variable added secret
defaults_system variable dynamic changed from for_ timestamp
mariadb--enable-cleartext-plugin command-line option added
mariadb-backup--sst-max-binlogs command-line option removed
mariadb-dump--max-statement-time command-line option added
mariadbd--spider-direct-aggregate command-line option added
direct_system variable added aggregate
DATA TYPEplugin added
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.9-5 is provided for:
CentOS 7 (x86_
Debian 10 (x86_
Debian 11 (x86_
Microsoft Windows (x86_
Red Hat Enterprise Linux 7 (x86_
Red Hat Enterprise Linux 8 (x86_
Red Hat Enterprise Linux 9 (x86_
Rocky Linux 8 (x86_
Rocky Linux 9 (x86_
SUSE Linux Enterprise Server 12 (x86_
SUSE Linux Enterprise Server 15 (x86_
Ubuntu 18.04 (x86_
Ubuntu 20.04 (x86_
Ubuntu 22.04 (x86_
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".