MariaDB 10.4 is no longer maintained. Please use a more recent release.
The most recent release of MariaDB 10.4 is:MariaDB 10.4.34 Stable (GA) Download Now
MariaDB 10.4 is a previous major stable version. The first stable release of 10.4 was in June 2019, and it was maintained until June 2024.
See the Differences in MariaDB Enterprise Server 10.4 page for items that are different between MariaDB Community Server 10.4 and MariaDB Enterprise Server 10.4.
See for an overview of the changes.
The is now default on Unix-like systems, which is a major change to authentication in MariaDB ()
()
()
Added instant and changing of the order of columns ()
More Instant VARCHAR extension or ROW_FORMAT=DYNAMIC and ROW_FORMAT=COMPACT ()
change CHAR(0) to any VARCHAR
change a CHAR that is longer than 255 bytes to VARCHAR or wider CHAR
Implementation of the , one can enable the optimizer trace by enabling the system variable ()
is now enabled by default; new default values are and ()
Two new values for the variable : COMPLEMENTARY_FOR_QUERIES and PREFERABLY_FOR_QUERIES ()
extended with support for (, , , )
Support of brackets (parentheses) for specifying precedence in // operations ()
New command to reload SSL certificates without server restart ()
For a list of all new variables, see and .
Added to the system variable ()
Removed the status variable ().
New setting, TIME_ROUND_FRACTIONAL ()
New variable
Speed up rotation of binary logs, SHOW BINARY LOGS etc with optimizing binary log index file locking (, ).
A new server command, , and a new option, are added to instruct the server to wait for the last binlog event to be sent to all connected slaves before shutting down. ().
allows one to implement very efficient backups with minimal locking. .
In and later, has been upgraded from Galera 3 to Galera 4.
The following table lists each version of the 4 wsrep provider, and it lists which version of MariaDB each one was first released in. If you would like to install 4 using , , or , then the package is called galera-4.
The database contains new tables related to Galera replication:
wsrep_cluster
wsrep_cluster_members
wsrep_streaming_log
End users may read but not modify these tables.
The new streaming replication feature allows replicating transactions of unlimited size. With streaming replication, a cluster is replicating a transaction in small fragments during transaction execution. This transaction fragmenting is controlled by two new configuration variables:
(bytes, rows, statements) defines the metrics for how to measure transaction size limit for fragmenting. Possible values are:
bytes: transaction’s binlog events buffer size in bytes
rows: number of rows affected by the transaction
Transactions replicated through galera replication will now process the commit phase using MariaDB's group commit logic. This will affect transaction throughput, especially when binary logging is enabled in the cluster.
Rolling Upgrades from Galera 3 to Galera 4
Rolling upgrades from (or earlier) to also require an upgrade from 3 to 4. Galera 4 has a lot of changes and improvements that were not present in Galera 3.
Prior to the General Availability (GA) releases of and Galera 4, earlier versions of and Galera 4 had bugs that could lead to problems if Galera 4 nodes were in a cluster with Galera 3 nodes during a rolling upgrade. In these versions, rolling upgrades were not supported. This meant that, in order to upgrade a cluster, the cluster had to be completely stopped, and the nodes could only be restarted after the entire cluster had been upgraded to and Galera 4.
These bugs have been fixed in more recent versions, and rolling upgrades from Galera 3 to Galera 4 are supported. In order to perform a rolling upgrade, it is recommended to upgrade to or later and Galera 26.4.2 or later. However, as a general rule, users should try to ensure that they are upgrading to the latest versions of and Galera 4.
For more detailed information on how to upgrade, see .
Crash safe -based ()
Added Linux abstract socket support ()
Enabled C++11 ()
Performance improvements in collations (, , , )
Support for window via the new method ()
Json service for plugins ()
Change in behavior for ().
The function is automatically used as a for the in order to ensure that a valid json document is inserted (
For a complete list of security vulnerabilities (CVEs) fixed across all versions of MariaDB, see the page.
:
:
:
:
The obsolete is no longer created (MDEV-15851)
Much faster privilege checks for MariaDB setups with many user accounts or many database grants (MDEV-15649)
table is retired. User accounts and global privileges are now stored in the table (MDEV-17658)
support for and other (MDEV-12321)
change a VARCHAR that is shorter than 128 bytes into any longer VARCHAR
Instant collation or charset changes for non-indexed columns (MDEV-15564)
Reduced redo log volume for undo tablespace initialization (MDEV-17138)
Removed crash-upgrade support for pre-10.2.19 TRUNCATE TABLE (MDEV-13564)
Added key rotation for (MDEV-12041)
Implement (MDEV-12026)
are now used (but not collected) by default (MDEV-18608).
variable added. The default value is 100 (ANALYZE will use the whole table), but one can also set analyze to only use a sample of table data to collect the statistics.
Condition pushdown optimization now has bigger scope:
Conditions in HAVING clause can be pushed to WHERE. This behavior is controlled through flag condition_pushdown_from_having.
The flag optimize_join_buffer_size now defaults to on (MDEV-17903)
added (MDEV-16188). It is controlled through flag rowid_filter .
IF NOT EXISTS clause added to and IF EXISTS clause added to and (MDEV-16294)
Unique indexes can be created on or fields (MDEV-371)
The default for is now 200 (previously 0) (MDEV-18551)
on Windows now defaults to ON (MDEV-18439)
26.4.13
, , , , , ,
26.4.12
, , , , , ,
26.4.11
, , , ,
26.4.9
, ,
26.4.8
, ,
26.4.7
,
26.4.6
,
26.4.5
,
26.4.4
,
26.4.3
,
26.4.2
26.4.1
26.4.0
statements: number of SQL statements executed in the multi-statement
transaction
defines the limit for fragmenting. When a transaction’s size, in terms of the configured fragment unit, has grown over this limit, a new fragment will be replicated.
User data type plugins (MDEV-4912, in progress)
Improvements with SQL standard INTERVAL support to help functions and return more predictable results.
Historically, MariaDB uses the TIME data type for both "time of the day" values and "duration" values. In the first meaning the natural value range is from '00:00:00' to '23:59:59.999999', in the second meaning the range is from '-838:59:59.999999' to '+838:59:59.999999'.
To remove this ambiguity and for the SQL standard conformance we plan to introduce a dedicated data type INTERVAL that will be able to store values in the range at least from '-87649415:59:59.999999' to '+87649415:59:59.999999', which will be enough to represent the time difference between TIMESTAMP'0001-01-01 00:00:00' and TIMESTAMP'9999-12-31 23:59:59.999999'.
As a first step we support this range of values for intermediate calculations when TIME-alike string and numeric values are used in INTERVAL (i.e. duration) context, e.g. as the second argument of SQL functions TIMESTAMP(ts,interval) and ADDTIME(ts,interval), so the following can now be calculated:
MariaDB Named Commands (MDEV-17591)
MariaDB systemd multi-instance service have changed. See for details.
Stable (GA)
14 Aug 2023
Stable (GA)
7 Jun 2023
Stable (GA)
10 May 2023
Stable (GA)
6 Feb 2023
Stable (GA)
7 Nov 2022
Stable (GA)
15 Aug 2022
Stable (GA)
20 May 2022
Stable (GA)
12 Feb 2022
Stable (GA)
9 Feb 2022
Stable (GA)
8 Nov 2021
Stable (GA)
6 Aug 2021
Stable (GA)
23 Jun 2021
Stable (GA)
7 May 2021
Stable (GA)
22 Feb 2021
Stable (GA)
11 Nov 2020
Stable (GA)
3 Nov 2020
Stable (GA)
7 Oct 2020
Stable (GA)
10 Aug 2020
Stable (GA)
12 May 2020
Stable (GA)
28 Jan 2020
Stable (GA)
11 Dec 2019
Stable (GA)
8 Nov 2019
Stable (GA)
5 Nov 2019
Stable (GA)
11 Sep 2019
Stable (GA)
31 Jul 2019
Stable (GA)
18 Jun 2019
Stable (GA)
21 May 2019
RC
7 Apr 2019
RC
25 Feb 2019
RC
29 Jan 2019
Beta
20 Dec 2018
Beta
9 Nov 2018
Alpha
26.4.21
26.4.20
26.4.19
26.4.18
26.4.16
26.4.14
16 May 2024
Stable (GA)
7 Feb 2024
Stable (GA)
13 Nov 2023
SELECT ADDTIME(TIMESTAMP'0001-01-01 00:00:00', '87649415:59:59.999999');
-> '9999-12-31 23:59:59.999999'
SELECT TIMESTAMP(DATE'0001-01-01', '87649415:59:59.999999')
-> '9999-12-31 23:59:59.999999'
SELECT ADDTIME(TIME'-838:59:59.999999', '1677:59:59.999998');
-> '838:59:59.999999'This page is licensed: CC BY-SA / Gnu FDL