Changes and Improvements in MariaDB 10.4 (original) (raw)

The most recent release of MariaDB 10.4 is:
MariaDB 10.4.34 Stable (GA) Download Now

Implemented Features
Security Vulnerabilities Fixed in MariaDB 10.4
List of All MariaDB 10.4 Releases

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.

Implemented Features

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.

Authentication

See Authentication from MariaDB 10.4 for an overview of the changes.
The unix_socket authentication plugin is now default on Unix-like systems, which is a major change to authentication in MariaDB (MDEV-12484)
User password expiry (MDEV-7597)
Account Locking (MDEV-13095)
The obsolete mysql.host table is no longer created (MDEV-15851)
Much faster privilege checks for MariaDB setups with many user accounts or many database grants (MDEV-15649)
mysql.user table is retired. User accounts and global privileges are now stored in the mysql.global_priv table (MDEV-17658)
SET PASSWORD support for ed25519 and other authentication plugins (MDEV-12321)

InnoDB

Added instant DROP COLUMN and changing of the order of columns (MDEV-15562)
More Instant VARCHAR extension or ROW_FORMAT=DYNAMIC and ROW_FORMAT=COMPACT (MDEV-15563)
- change CHAR(0) to any VARCHAR
- change a CHAR that is longer than 255 bytes to VARCHAR or wider CHAR
- 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 innodb_encrypt_log (MDEV-12041)
Implement innodb_checksum_algorithm=full_crc32 (MDEV-12026)

Optimizer

Implementation of the optimizer trace, one can enable the optimizer trace by enabling the system variable optimizer_trace (MDEV-6111)
Engine Independent Table Statistics is now enabled by default; new default values are use_stat_tables=PREFERABLY_FOR_QUERIES and optimizer_use_condition_selectivity=4 (MDEV-15253)
- Two new values for the variable use_stat_tables: COMPLEMENTARY_FOR_QUERIES and PREFERABLY_FOR_QUERIES (MDEV-17255)
- Histograms are now used (but not collected) by default (MDEV-18608).
- analyze_sample_percentage 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 can be pushed into materialized IN-subqueries (MDEV-12387)
- Conditions in HAVING clause can be pushed to WHERE. This behavior is controlled through optimizer switch flag condition_pushdown_from_having.
The optimizer switch flag optimize_join_buffer_size now defaults to on (MDEV-17903)
Rowid Filtering optimization added (MDEV-16188). It is controlled through optimizer switch flag rowid_filter .

Syntax

Temporal tables extended with support for application-time periods (MDEV-16973, MDEV-16974, MDEV-16975, MDEV-17082)
Support of brackets (parentheses) for specifying precedence in UNION/EXCEPT/INTERSECT operations (MDEV-11953)
New FLUSH SSL command to reload SSL certificates without server restart (MDEV-16266)
New CAST target — CAST(x AS INTERVAL DAY_SECOND(N)) (MDEV-17776)
IF NOT EXISTS clause added to INSTALL PLUGIN and IF EXISTS clause added to UNINSTALL PLUGIN and UNINSTALL SONAME (MDEV-16294)
Unique indexes can be created on BLOB or TEXT fields (MDEV-371)

Variables

For a list of all new variables, see System Variables Added in MariaDB 10.4 and Status Variables Added in MariaDB 10.4.

Added to the tcp_nodelay system variable (MDEV-16277)
Removed the Innodb_pages0_read status variable (MDEV-15705).
New sql-mode setting, TIME_ROUND_FRACTIONAL (MDEV-16991)
New variable gtid_cleanup_batch_size for determining how many old rows must accumulate in the mysql.gtid_slave_pos table before a background job will be run to delete them.
The default for eq_range_index_dive_limit is now 200 (previously 0) (MDEV-18551)
core_file on Windows now defaults to ON (MDEV-18439)

Replication

Speed up rotation of binary logs, SHOW BINARY LOGS etc with optimizing binary log index file locking (MDEV-19116, MDEV-19117).
A new server command, SHUTDOWN WAIT FOR ALL SLAVES, and a new mysqladmin shutdown --wait-for-all-slaves option, are added to instruct the server to wait for the last binlog event to be sent to all connected slaves before shutting down. (MDEV-18450).

Backup

BACKUP STAGE allows one to implement very efficient backups with minimal locking. MDEV-5336.

Galera 4

In MariaDB 10.4.2 and later, Galera has been upgraded from Galera 3 to Galera 4.

Galera 4 Versions

The following table lists each version of the Galera 4 wsrep provider, and it lists which version of MariaDB each one was first released in. If you would like to install Galera 4 using yum, apt, or zypper, then the package is called galera-4.

New Features in Galera 4

The [mysql](/kb/en/the-mysql-database-tables/) 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:

[wsrep_trx_fragment_unit](/kb/en/galera-cluster-system-variables/#wsrep%5Ftrx%5Ffragment%5Funit) (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
- statements: number of SQL statements executed in the multi-statement transaction
[wsrep_trx_fragment_size](/kb/en/galera-cluster-system-variables/#wsrep%5Ftrx%5Ffragment%5Fsize) 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.

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.

Limitations in Galera 4

Rolling Upgrades from Galera 3 to Galera 4

Rolling upgrades from MariaDB 10.3 (or earlier) to MariaDB 10.4 also require an upgrade from Galera 3 to Galera 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 MariaDB 10.4 and Galera 4, earlier versions of MariaDB 10.4 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 MariaDB 10.4 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 MariaDB 10.4.6 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 MariaDB 10.4 and Galera 4.

For more detailed information on how to upgrade, see Upgrading from MariaDB 10.3 to MariaDB 10.4 with Galera Cluster.

General

Crash safe Aria-based system tables (MDEV-16421)
Added Linux abstract socket support (MDEV-15655)
Enabled C++11 (MDEV-16410)
Performance improvements in Unicode collations (MDEV-17534, MDEV-17511, MDEV-17502, MDEV-17474)
User data type plugins (MDEV-4912, in progress)
Improvements with SQL standard INTERVAL support to help functions TIMESTAMP() and ADDTIME() 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:

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'

Support for window UDF functions via the new method x_remove (MDEV-15073)
Json service for plugins (MDEV-5313)
Change in behavior for FLUSH TABLES (MDEV-5336).
The JSON_VALID function is automatically used as a CHECK constraint for the JSON data type alias in order to ensure that a valid json document is inserted (MDEV-13916)
MariaDB Named Commands (MDEV-17591)
MariaDB systemd multi-instance service have changed. See systemd page for details.