Notable Changes

• Galera updated to 25.3.35

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:

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 tis620 character set, the server can crash with a segmentation fault (signal 11). (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 and 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:

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

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

• When 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. ()

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

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

Can result in unexpected behavior

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

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

• Subquery using the ALL keyword on 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. ()

• 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 error code. ()

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

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

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

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

• When 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. ()

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

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

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

• The collation column in the table is incorrectly read as NULL. ()

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

• When is changed dynamically with , 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 . ()

• When the 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. ()

• When the 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. ()

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

• When is set, some window functions incorrectly raise an error with the error code. ()

• When DEFAULT(COLUMN_NAME) is used in a WHERE clause, the result can be incorrect. ()

• When a CTE is used with a UNION in a statement, the server incorrectly raises an error with the error code. ()

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

Related to install and upgrade

• When wsrep_sst_method=mariadb-backup is set for MariaDB Enterprise Cluster, but MariaDB Enterprise Backup is not installed on the joiner node, the joiner node fails to start. (MDEV-15209)

Interface Changes

• system variable minimum value changed from 5242880 to 2097152

• mysql_upgrade command-line option added

• mysqld command-line option added

• system variable added

Platforms

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

• CentOS 7 (x86_64)

• Debian 9 (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)

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

Notable Changes

• updated to 5.7.29.

• Limit to 255 (MDEV-22258)

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

• requires instead of privilege. ()

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

Issues Fixed

Can result in data loss

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

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

• corruption in delete buffering. (MDEV-22497)

Can result in a hang or crash

• deadlock in (MDEV-22890)*

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

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

• Deadlock involving parallel workers, , and (MDEV-23089)

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

• Dropping the adaptive hash index may cause DDL to lock up ()

• could result in a crash, when the value exceeds the max allowed 2147483647 ()

• Crash on WITH RECURSIVE large query. ()

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

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

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

• or in a statement, which has a 0x00 byte in one of the values could crash the server. ()

• 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 * table instead of for the partition. (MDEV-21472)

• can fail with privilege error when privilege exists at database level but 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. ()

• does not stop on errors while applying InnoDB redo log. ()

Related to install and upgrade

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

Interface Changes

• ER_TRANSACTIONAL_ARIA_LOG_ENGINE error code added

• system variable minimum value changed from 4 to 8

Platforms

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

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

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 to stream a backup using the included mbstream utility. ()

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

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

• The table has been added and can be used to view details about SQL keywords. ()

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

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

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

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

Issues Fixed

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

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

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

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

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

• Server crashes possible when using virtual generated columns. (, )

• Server crashes while executing when a column is truncated. ()

• Server crashes while executing when a hostname cannot be resolved. ()

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

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

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

• Possible deadlock on a Replica server using GTID Replication when and , , or is executed. ()

• Server crashes when fails on an InnoDB table. ()

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

• Server crashes while executing on an InnoDB table with virtual generated columns that are indexed. ()

Can result in unexpected behavior

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

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

• The 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 . ()

• Reusing CTE inside a function fails with the error code. ()

• Several fixes for MariaDB Enterprise Cluster (Galera) SST scripts. (, , , , , , , MENT-1170, , )

• With MariaDB Enterprise Cluster, when , MariaDB Enterprise Backup does not inherit server options set by the Environment systemd configuration parameter. ()

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

As a result of this issue, a Joiner node writes the following error to the

• With MariaDB Enterprise Cluster, when 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 is not enabled. (MDEV-26062)

  • In prior releases, the following warning could be written to the log:

• 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 statement may check the wrong maximum column length. (MDEV-26203)

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

• The system variable does not work correctly with the authentication plugin. ()

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

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

• An aborted statement is logged in the binary log and replicates to the Replica server. ()

• shows an execution plan different from actually executed. ()

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

• Procedure containing CTE incorrectly stored in the system table. ()

Interface Changes

• information schema table added

• information schema table added

Platforms

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

• CentOS 7 (x86_64)

• CentOS 8 (x86_64, ARM64)

• Debian 9 (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)

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

option added

Notable Changes

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

• Galera updated to 25.3.3

Issues Fixed

Can result in data loss

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

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

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

Can result in a hang or crash

• Possible hang when or 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 (, , , and related types). (MDEV-24978)

• fails on compressed tables. (MDEV-25121)

• Server crashes in check_grant upon invoking function with enabled. ()

• crashes when --default-character-set is set and --character-sets-dir is undefined. ()

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

• Possible server hang with and indexed virtual columns after an error with , , on virtual columns. ()

• conflict resolution issues. ()

• Index count mismatch due to aborted FULLTEXT INDEX ()

• node crashes when inserting a row into a table that contains a virtual column and does not have a primary key. ()

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

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

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

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

• startup hangs when a recovered transaction exists for the or system tables and a DDL transaction needs to be rolled back. ()

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

• Server crashes on when a WHERE condition references a derived table. ()

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

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

Can result in unexpected behavior

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

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

• Query returns a error when a Common Table Expression (CTE) contains a UNION ()

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

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

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

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

• Duplicate key may be generated during configuration change. ()

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

• Race condition between persistent statistics and or ()

• Race condition between and STATS_AUTO_RECALC ()

• Incorrect message about field length is written to the when is executed on an table. ()

• 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 subquery, unknown table aliases in the redundant part are ignored. ()

• Selectivity shown with in field "filter" is incorrect for columns. ()

• Histogram statistics are used even with ()

• shows nonsensical value for key_len with type=index ()

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

• Wrong function name in error messages upon call. ()

• fails on large backup. ()

• State snapshot transfer (SST) for using fails when the password for the backup user is set via the MYSQL_PWD environment variable. ()

• State snapshot transfer (SST) for using fails when the option was set on the command-line at server startup. ()

• An extra warning is returned when the statement is executed in a prepared statement. ()

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

• wrongly checks for field's default value if AFTER is used. ()

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

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

• logs an error instead of a warning when it reads an invalid log block checksum during a . ()

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

• aborts after failed into table with virtual column. ()

• fails to fetch index type when index mismatch happens. ()

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

• causes "Ignoring data file ... with space ID xxxx, since the redo log references ... with space ID xxxx." for . ()

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

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

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

• fails to replicate statement when is enabled. ()

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

• command-line option added

• command-line option added

• function added

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.2.38-12 is provided for:

• CentOS 7

• CentOS 8

• Debian 9

• Red Hat Enterprise Linux 7

• Red Hat Enterprise Linux 8

• SUSE Linux Enterprise Server 12

• SUSE Linux Enterprise Server 15

• Ubuntu 18.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.}

#1: MariaDB CVEs are assigned a word rating instead of a CVSS base score. See the MariaDB Engineering Policies for details.

Notable Changes

• Galera wsrep library updated to 25.3.31 in MariaDB Enterprise Cluster.

• In alignment with the MariaDB Engineering Policies, 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 . (MDEV-19443)

  • On connect, if a proxy user is used, an extra line will be logged: TIME,HOSTNAME,user,localhost,ID,0,PROXY_CONNECT,test,plug_dest@%,0

• Better MariaDB GTID support for the option. ()

• New global variable ()

• 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 record locks when covering table locks exist. (MENT-403)

• Change by default. ()

Issues Fixed

Can result in data loss

• Data corruption possible for encrypted tables if the non-default option 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 command if is used before altering a child table to remove a primary key. (MDEV-22934)

Can result in a hang or crash

• persistent stats analyze forces full scan which results in a lock crash. (MENT-1024)

• hang on with error message Semaphore wait has lasted > 300 seconds. (MENT-1007)

• Server crash can happen on filesort with a setting for to a value lower than the default of 64 (MDEV-24033)

• Potential stack overflow in fulltext search with a complex MATCH .. AGAINST string. ()

• mariadb-backup can hang if the server goes idle after a particular kind of redo log write. ()

• A server crash can occur when encryption is enabled for temporary tables (encrypt-tmp-files=ON) and queries use window functions. ()

• A crash of MariaDB Server is possible when binary logging is activated, caused by improper raising of an error or replication checksum. ()

• assertion on after ALTER TABLE .. DISCARD TABLESPACE ()

• Server crashes after failed attempt to create unique key on virtual column. ()

• Possible server crash when using an index on a spatial data type with . ()

• Possible server crash when a string function is used for a column of type and the string function is used in a subquery which is returning a row. ()

• node can crash on high , , or load from many connections executed on the same table with foreign keys. ()

• Server crashes if a query is executed on an table with a foreign key where the foreign key was removed while using . This case should result in an SQL error. ()

• Recursive procedure call ends with a crash instead of SQL error. ()

• fails to open the table during removal of VIRTUAL column DDL while using SET , due to lack of referenced index. ()

• Server crash when altering a table after its tablespace has been discarded already. ()

• caused a variety of non-determinism failures if the given position did not exist. ()

• SET GLOBAL replicate_do_db = DEFAULT causes a crash. ()

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

• Server crashes after with ON DELETE SET NULL for foreign key and a virtual column in index. ()

• Server can crash on a prepared statement executed via . ()

• Crash on on a table that contains indexed virtual columns. ()

• Possible server crash for queries using the window function ()

• got stuck after FLUSH TABLES ()

• Server crash can occur when SET GLOBAL is used. ()

Can result in unexpected behavior

• Defining a view with SQL syntax incorrectly returns a syntax error. (MENT-1015)

• MariaDB Enterprise Backup reports an error that it cannot find an log file './aria_log.00000000' (MENT-907)

• MariaDB Enterprise Backup failure for incremental backups. (MDEV-24026)

• Aborting a query on an table with does not show an SQL error message, if the query could not be aborted. ()

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

• Some rounding has been done in an unexpected way for decimal numbers. ()

• Server crashes after changing at runtime via a statement. ()

• Creating a view removes parentheses on expressions from the , which results in wrong results. ()

• mysql_tzinfo_to_sql under is slow. ()

• UDF cannot be uninstalled if the UDF library file doesn't exist. ()

• with type can return an unexpected result, if the given value for "expr" includes many leading zeros. ()

• replication broken if only one timezone is loaded. ()

• SST donation fails, FLUSH TABLES WITH READ LOCK times out. ()

• Memory leaks possible after with FOREIGN KEY ()

• SST fails for if data-directory has lost+found directory. ()

• caused a variety of non-determinism failures if the given position did not exist. ()

• Linux AIO returned OS error 22 if parameters set to _flush_method O_DIRECT and _use_native_aio=1 (default). ()

• CREATE OR REPLACE TRIGGER in not replicating, if a trigger with the same name already exists. ()

• mysqld_multi no longer works with different server binaries. ()

• Possible error for incremental backup for encrypted tablespaces. ()

• Possible slow server start and stop if full text indexes are used. ()

• The parentheses in a VIEW can be defined incorrectly for a combination of = and BETWEEN ()

• upon replaying binary log. ()

• Several IPv6 issues with powered by Galera. (, , , , )

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

• system variable default value changed from ON to OFF

• system variable added

• command-line option added

• system variable maximum value changed from 200 to 1048576

Platforms

In alignment with the enterprise lifecycle, MariaDB Enterprise Server 10.2.36-10 is provided for:

• Red Hat Enterprise Linux 7

• Red Hat Enterprise Linux 8

• CentOS 7

• CentOS 8

• Ubuntu 16.04

• Ubuntu 18.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.}