MariaDB Enterprise Server 10.4.27-18 is a maintenance release of . This release includes a variety of fixes.
MariaDB Enterprise Server 10.4.27-18 was released on 2022-12-21.
The 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:
When a table's default collation is set to the default collation for the table's character set, shows the COLLATE clause. ()
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.
When a column is renamed in a partitioned table with using the , the table can be corrupted. ()
When the InnoDB storage engine performs change buffer operations, the can overflow, which can cause table corruption. (, )
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. ()
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. ()
When querying a partitioned table using the PARTITION syntax, if the WHERE clause results in an index merge, the server can crash. ()
When detecting CTE dependencies of nested CTEs that include one or more recursive CTEs, infinite recursion can occur until the server crashes. ()
When the is configured to use the bundled wsrep_notify.sh script, the server can hang during startup. ()
When selecting from InnoDB's (such as , , and ), if connections with open XA transactions are disconnected or killed at the same time, the server can crash. ()
When an application-time period with an empty name is added to a table using , the server can crash. ()
In previous releases, statements like the following could cause the server to crash:
When the Spider storage engine's ODBC foreign data wrapper is used with MariaDB Connector/ODBC 3.1.10, and later, the server can crash. ()
In the presence of replication filters, revoking privileges from a non-existing user on a primary (master) breaks replication on the replica (slave). ()
When is set on a replica node, the replica node does not skip replicated . ()
When a Spider table has a prefix index, query results can be incorrect. ()
InnoDB can extend tablespace files when additional capacity is not required. (
When an InnoDB table contains virtual generated columns that are indexed, InnoDB fails to purge secondary index records. ()
When using the InnoDB adaptive hash index, non-locking reads can return wrong results due to a potential ACID violation. (, , )
When is used on a temporary table, an empty result set is returned. ()
When a sequence is used as the default value in a table, rows inserted by an
When a column has both a UNIQUE index and a FULLTEXT index, full-text search using MATCH(..) AGAINST(..) does not work properly. ()
If the server is started with the 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. ()
With MariaDB Enterprise Cluster, when is configured, the joiner node ignores custom values for the system variable, and the SST copies the buffer pool file to the default location instead. ()
When a TIMESTAMP column is filtered in a subquery inside the ALL operator, the results can be incorrect. ()
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/. ()
When is executed, spurious errors about table rebuilds are logged. ()
In previous releases, the following messages would be logged, even though the tool already mitigated the issues itself:
In alignment with the , MariaDB Enterprise Server 10.4.27-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)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see
When renaming a table to a long name, the server can crash. (MDEV-29258)
When an 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)
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 statement, the server can crash. (MDEV-23160)
When 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 on the joiner node could contain the following error about the crash:
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 error code. (MDEV-17124)
In previous releases, the following error would occur:
INSERT ... SELECTWhen the does not contain a port number, the status variable shows 0 as the port number. (MDEV-28868)
When is enabled, performance is impacted if the rowid filter contains no elements. (MDEV-28846)
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)
SELECT * FROM information_schema.INNODB_SYS_TABLESPACES
WHERE name LIKE 'innodb_temporary';[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 ;ALTER TABLE t
ADD PERIOD IF NOT EXISTS FOR `` (s,e);ERROR 1615 (HY000): Prepared statement needs to be re-preparederror: Table rebuild required. Please do "ALTER TABLE `TABLE_NAME` FORCE" or dump/reload to fix it!"This page is: Copyright © 2025 MariaDB. All rights reserved.