MariaDB Enterprise Server 10.4.26-17 is a maintenance release of . This release includes a variety of fixes.
MariaDB Enterprise Server 10.4.26-17 was released on 2022-09-12.
CVE (with link)
CVSS base score
Galera has been updated to 26.4.13-1
Debian 9 support has been discontinued.
The has been added for with a default value of 0. ()
When is executed with the command-line option, the backup tries to copy the InnoDB buffer pool dump file, which is located at the path defined by the system variable. ()
Starting with this release, only copies the InnoDB buffer pool dump file during State Snapshot Transfers (SSTs) for MariaDB Enterprise Cluster, powered by Galera.
When is executed against an encrypted InnoDB tablespace file, the table can be corrupted. ()
When INSERT .. SELECT .. GROUP BY is executed and the GROUP BY clause contains a derived table, the server can crash. ()
When a query contains an ANY(SELECT .. GROUP BY(SELECT ..)) predicand with a redundant subquery in the GROUP BY clause, the server can crash. ()
When ALTER TABLE .. ADD is used to add a column with the
When a generated column is added to an InnoDB table with the INSTANT algorithm, the server can crash due to a buffer overflow. ()
When is executed with a view definition that contains an unknown column in an ON condition, the server can crash instead of raising an error with the error code. ()
For multi-table or queries, the optimizer fails to apply partition pruning optimization for the table that is updated or deleted from. ()
When an IN condition contains a mixture of numeric and string values, results can be inconsistent. ()
When a sequence event is written to the binary log with , the value of is not respected. ()
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. ()
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 . ()
When a backup is performed with , the backup includes binary logs. ()
When uses EditLine instead of readline (such as on Debian and Ubuntu), Unicode characters are not accepted. ()
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. ()
When a FULLTEXT search is performed on an InnoDB table, the results are incorrect when the search term contains an apostrophe ('). (
mariadb-backup command-line option removed
mysql command-line option added
mysqld command-line option added
In alignment with the , MariaDB Enterprise Server 10.4.26-17 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)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see
With MariaDB Enterprise Cluster, when is enabled on a node, users without the can still write to the node. (MDEV-28546)
With MariaDB Enterprise Cluster, when a value is retrieved from an InnoDB sequence using the , the change is not replicated. (MDEV-27862)
Starting with this release, InnoDB sequences are properly replicated when they are defined with NOCACH.
When an InnoDB table's collation is changed using with the INPLACE or NOCOPY algorithms, duplicate entries in unique indexes are not detected. (MDEV-26294)
INSTANTROW_FORMAT.frmFor 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 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 is an always-constant function.
When is executed with the and 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)
When an IN subquery 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 :
In previous releases, this problem could cause replica servers to encounter the following error:
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 is raised with the error code and the following error message:
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.
After upgrading from old versions of MariaDB Server, some operations fail if ALGORITHM=NOCOPY is specified. (MDEV-28727)
In previous releases, the following error could be raised:
mysqldump command-line option addedsystem variable added
Rocky Linux 8 (x86_64, ARM64 Red Hat Enterprise Linux 8 packages)
SUSE Linux Enterprise Server 12 (x86_64)
SUSE Linux Enterprise Server 15 (x86_64, ARM64)
Ubuntu 20.04 (x86_64, ARM64)
7.5
7.5
6.5
6.5
6.5
6.5
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 ;Last_SQL_Errno 1590
Last_SQL_Error The incident LOST_EVENTS occurred on the master. Message: error writing to the binary logOut of range value for column 'COLUMN_NAME' at row ROW_NUMERROR 1845 (0A000): ALGORITHM=NOCOPY is not supported for this operation. Try ALGORITHM=INPLACEThis page is: Copyright © 2025 MariaDB. All rights reserved.