Release date: 24 December 2023
MariaDB 11.4 is a long-term development series of MariaDB. It is an evolution of MariaDB 11.3 with several entirely new features.
MariaDB 11.4.0 is a single preview release. Features are to be considered preview, and none are guaranteed to make it into MariaDB 11.4.
The preview is available as a container quay.io/mariadb-foundation/mariadb-devel:11.4.
For an overview of MariaDB 11.4 see the What is MariaDB 11.4? page.
Thanks, and enjoy MariaDB!
and now support the WITH VALIDATION and WITHOUT VALIDATION clauses. If neither is specified, the default behavior is WITH VALIDATION ()
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 ()
Not only ascending, but also can now be used to optimize and ()
The preferred way to specify is to use the dedicated Spider table options (implemented in ). Abusing the table COMMENT clause is now deprecated ()
function now supports conversion up to base 62 ()
Added support for packages () outside of ()
Remove thr_alarm from server codebase
Includes removal of the system variable (
writing speed was improved by moving checksum calculations out of the global binlog mutex (). 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 ().
The range of values was extended. The maximal allowed value for timestamps was '2038-01-19 03:14:07 UTC', and is now '2106-02-07 06:28:15 UTC'. This does not change the storage format, and new tables can be read by old MariaDB servers as long as timestamp values are within the old timestamp range. At the moment this is only supported on 64-bit platforms (). This was not included in .
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).
Note that this feature was not included in MariaDB 11.4. events in the now include connection id of the client connection that generated the event. This allows to tag all row events with a corresponding connection id (MDEV-7850).
Do not use non-stable (non-GA) releases in production!
This page is licensed: CC BY-SA / Gnu FDL