An overview of changes, improvements, and what's new in MariaDB Community Server 11.4
MariaDB 11.4 is a current long-term series, maintained until May 2029.
See and .
This list includes all features since the previous long-term release, (those introduced in the , and short-term releases, and the rolling release).
Major improvements to the Optimizer. See .
for single-table / statements. Update and delete statements that use subqueries can now use all subquery optimization strategies that MariaDB offers, so now if you use subqueries in UPDATE or DELETE, these statements will likely be much faster (, )
Queries with the or functions comparing against a constant can now make use of indexes, so these will be noticeably quicker in certain instances. For example SELECT * FROM t2 WHERE YEAR(a) = 2019 or SELECT * FROM t2 WHERE DATE(a) <= '2017-01-01'
Shrink without restart by setting the system variable. (, )
The is now shrunk by reclaiming unused space at startup (, )
can now do most operations with ALGORITHM=COPY, LOCK=NONE, that is, in most cases, unless the algorithm and lock level are explicitly specified, ALTER TABLE will be performed using the algorithm while simultaneously allowing concurrent on the altered table. ()
For more information, refer to, .
writing speed was improved by moving checksum calculations out of the global binlog mutex (). The system variable is available if the old behavior is desired. This is a contribution by Kristian Nielsen
New system variable enables binary log purging when the total size of all binary logs exceeds the specified threshold. The implementation is based on the patch from Percona ()
New system variable disables binary log purging until the number of connected slaves reaches the specified threshold ().
is now enabled in the server by default. No configuration necessary, if no server certificate was provided a self-signed certificate will be automatically generated by the server. See for details ().
Clients now can validate self-signed server certificates if the or authentication is used and account password is not empty ().
Clients now require SSL and have enabled by default ().
now allows retrieval of the key when iterating on JSON objects (, )
New functions , and to check for JSON intersection (, )
extracts key/value pairs from a JSON object (, )
It is now possible to create on tables that contain (, )
data types can now be cast into types (, )
This means INET4 values can be compared with INET6 values and can be inserted into INET6 columns; the server can automatically convert INET4 value into INET6 as needed ()
New option, -j, --parallel= for increased parallelism, specifies the number of dump table jobs executed in parallel (only for use with the --tab option). Also added to , with --use-threads as a synonym. ()
mode has been deprecated (, )
Add views for in information_schema (), in particular
New view
New view
New columns IS_SYSTEM_TIME_PERIOD_START and IS_SYSTEM_TIME_PERIOD_END
New view shows granted privileges broken down by table on which they allow access and level on which they were granted. For example, if a user x has SELECT privilege granted ON db.*, this view will list all tables in the db schema with the user x having SELECT privilege on them. This is different from , which only lists privileges granted on the table level ()
and now support the WITH VALIDATION and WITHOUT VALIDATION clauses. If neither is specified, the default behavior is WITH VALIDATION ()
From :
44 new added. These are aliases for MySQL collations to make it easier to replicate from MySQL to MariaDB ()
The includes a new column, COMMENT which contains information about which collation the alias refers to.
Added a using the system variable (, )
At the moment client-side support is missing
Add a new database-level , SHOW CREATE ROUTINE that allows one to see the routine definition even if the user isn't the routine owner (, )
The preferred way to specify is to use the dedicated Spider table options (implemented in ). Abusing the table COMMENT clause is now deprecated ()
The storage engine now supports table options instead of having to encode them in COMMENT/CONNECTION strings. When any table option is specified, Spider will ignore COMMENT/CONNECTION strings at the same table/partition/subpartition. A new variable is introduced to ignore them globally at all levels (table/partition/subpartition). Another variable, , is introduced to suppress warnings when Spider ignores COMMENT/CONNECTION strings. (, )
function now supports conversion up to base 62 ()
Values generated by the Key Derivation Function are resistant against password hashing generators, so are good for strongly hashed passwords ()
Given a time in picoseconds, the new function returns a human-readable time value and unit indicator (, )
function can now print the current time zone abbreviation and current time zone offset from UTC with %Z and %z format specifiers. (, )
Added a SENT_ROWS column to the table, as well as extended the display size for the columns in processlist to ensure
that most results will fit in display (, )
Added support for packages () outside of ()
Setting a non-default value will now always issue a deprecation warning (, )
enhancement (, )
Temporary tables are now displayed in the ,
For a list of all new variables, see .
Removed
Remove thr_alarm from server codebase
Includes removal of the system variable ()
In addition, the following deprecated features and system variables have been removed (, ):
For a complete list of security vulnerabilities (CVEs) fixed across all versions of MariaDB, see the page.
:
:
Queries like can now use an index on varchar_col if its collation is case insensitive. An option, , has been added to enable this optimization. (MDEV-31496, MariaDB 11.3)
Not only ascending, but also can now be used to optimize and (MDEV-27576)
FULL_NODUP is a new value for the system variable. It essentially works like FULL, that is all columns are included in the event, but it takes less space, because the after image omits columns that were not changed by the UPDATE statement, and have same values as in the before image. This is a contribution from Alibaba (MDEV-32589)support for the mode. This is a contribution from Alibaba (MDEV-32894).
MariaDB can optionally maintain a and their location in the binary log. If enabled (the default), it allows finding very quickly where a new connecting replica should start replicating from. Without an index, this required scanning the binlog. This is a contribution by Kristian Nielsen (MDEV-4991).
Add keywords "SQL_BEFORE_GTIDS" and "SQL_AFTER_GTIDS" for (MDEV-27247, MariaDB 11.3). SQL_BEFORE_GTIDS stops the replica when it sees gtids of the option's argument list, without executing them. (MariaDB 11.3)
All binlog* variables are now visible as system variables, specifically , , (MDEV-30188, MariaDB 11.2)
Use --disable-ssl or --disable-ssl-verify-server-cert to revert to the old behavior.
Clients can use new command line options and to verify the server certificate by its fingerprint
: validation of stored program statements (MDEV-5816, MariaDB 11.2)
Extend and to support an initialization vector and algorithm (MDEV-9069, MariaDB 11.2)
The option is now a system variable, and the tx_isolation system variable is deprecated (MDEV-21921, MariaDB 11.1)
"engine_condition_pushdown" in (deprecated since MariaDB 10.1.1)
, , , (deprecated since MariaDB 10.1.2)
(deprecated since MariaDB 10.1.3)
"parser" in table comment (deprecated since MariaDB 10.2.11)
variable (MDEV-30905, MariaDB 11.3)
and related parameters (MDEV-30545, MariaDB 11.1)
The has been removed (MDEV-29694, MariaDB 11.0)
MariaDB 11.4.7
Stable (GA)
6 May 2025
MariaDB 11.4.6
Stable (GA)
4 Feb 2025
MariaDB 11.4.5
Stable (GA)
1 Nov 2024
MariaDB 11.4.4
Stable (GA)
8 Aug 2024
MariaDB 11.4.3
Stable (GA)
29 May 2024
MariaDB 11.4.2
Stable (GA)
16 Feb 2024
MariaDB 11.4.1
RC
24 Dec 2023
MariaDB 11.4.0
Alpha
6 Nov 2025
MariaDB 11.4.9
Stable (GA)
6 Aug 2025
MariaDB 11.4.8
Stable (GA)
22 May 2025
This page is licensed: CC BY-SA / Gnu FDL