MariaDB Enterprise Server 10.4.34-24 is a maintenance release of . This release includes a variety of fixes.
MariaDB Enterprise Server 10.4.34-24 was released on 2024-06-11.
Galera has been updated to 26.4.18
The GCS protocol version has been changed, preventing a downgrade of individual nodes of a MariaDB Enterprise Cluster
With --gtid-ignore-duplicate set, a transaction can be double-applied from another replication source if applying the transaction from the initial source required retrying in parallel execution. ()
Backups of server with innodb_encrypt_tables=1 can become corrupted in mariadb-backup --prepare ()
Galera-replicated events can, in some cases, contain the wrong time when versioning is used ()
Using current MariaDB Enterprise Backup against an older server can result in a crash, as the system variable @@aria_log_dir_path does not exist ()
For encrypted table spaces, an ALTER operation can hang when an encryption thread works on the same tablespace ()
EXPLAIN statement that uses a subquery which has a query plan that A) will examine less than @@expensive_subquery_limit rows and B) will use the join buffer, could cause a crash. ()
Spider/ODBC passed double quotes for names, in ANSI style ()
Default charset doesn't work with the PHP MySQLi extension ()
Spider returns parsing failure on valid left join select by translating the on expression to () ()
Original IP not shown in network-related error messages when proxy_protocol
Table is getting rebuilt with ALTER TABLE ADD COLUMN, although it should be an instant operation, not requiring a rebuild ()
For the complete list of changes in this release, see the .
In alignment with the , MariaDB Enterprise Server 10.4.34-24 is provided for:
CentOS 7 (x86_64)
Debian 10 (x86_64)
Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)
Red Hat Enterprise Linux 7 (x86_64)
Some of the components of MariaDB Enterprise Server are supported on a subset of platforms. See for details.
MariaDB Enterprise Backup fails with the following error message if the prepare step of the backup encounters a data directory, which happens to store wsrep xid position in TRX SYS page: (MDEV-33540)
Incorrect DEFAULT expression evaluated in UPDATE (MDEV-33790)
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)
InnoDB: Crash recovery is broken due to insufficient innodb_log_file_sizeThis page is: Copyright © 2025 MariaDB. All rights reserved.