Changes and Improvements in MariaDB 11.4

You are viewing an old version of this article. View the current version here.

MariaDB 11.4 is a current long-term series, maintained until May 2029.

Upgrading

New Features

This list includes features from the MariaDB 11.0, MariaDB 11.1 and MariaDB 11.2 short-term releases, and the MariaDB 11.3 rolling release.

Optimizer

InnoDB

Online Schema Change

  • ALTER TABLE 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 COPY algorithm while simultaneously allowing concurrent DML statements on the altered table. (MariaDB 11.2)

Replication and Binary Log

  • Binary log writing speed was improved by moving checksum calculations out of the global binlog mutex (MDEV-31273). The binlog_legacy_event_pos system variable is available if the old behavior is desired. This is a contribution by Kristian Nielsen
  • New system variable max_binlog_total_size 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 (MDEV-31404)
  • New system variable slave_connections_needed_for_purge disables binary log purging until the number of connected slaves reaches the specified threshold (MDEV-31404).
  • FULL_NODUP is a new value for the binlog_row_image 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)
  • mariadb-binlog --flashback support for the FULL_NODUP mode. This is a contribution from Alibaba (MDEV-32894).
  • MariaDB can optionally maintain a special index of GTIDs 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 START SLAVE UNTIL (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 binlog_do_db, binlog_ignore_db, binlog_row_event_max_size (MDEV-30188, MariaDB 11.2)

SSL/TLS

JSON

Data Types

Backup and Restore

Application-Time Periods

Sys Schema

  • New view sys.privileges_by_table_by_level 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 INFORMATION_SCHEMA.TABLE_PRIVILEGES, which only lists privileges granted on the table level (MDEV-24486)

Partitioning

Connection Redirection

Privileges

  • Add a new database-level privilege, SHOW CREATE ROUTINE that allows one to see the routine definition even if the user isn't the routine owner (MDEV-29167, MariaDB 11.3)

Spider

  • The preferred way to specify Spider parameters is to use the dedicated Spider table options (implemented in MariaDB 11.3). Abusing the table COMMENT clause is now deprecated (MDEV-28861)
  • The Spider 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 spider_ignore_comments is introduced to ignore them globally at all levels (table/partition/subpartition). Another variable, spider_suppress_comment_ignored_warning, is introduced to suppress warnings when Spider ignores COMMENT/CONNECTION strings. (MDEV-28856, MariaDB 11.3)

Miscellaneous Functions

  • CONV() function now supports conversion up to base 62 (MDEV-30879)
  • Values generated by the Key Derivation Function KDF are resistant against password hashing generators, so are good for strongly hashed passwords (MDEV-31474)
  • Given a time in picoseconds, the new function FORMAT_PICO_TIME returns a human-readable time value and unit indicator (MDEV-19629, MariaDB 11.0)

Date and Time

  • DATE_FORMAT function can now print the current time zone abbreviation and current time zone offset from UTC with %Z and %z format specifiers. (MDEV-31684, MariaDB 11.3)

Processlist

Miscellaneous

Variables

Removed

The following deprecated features and system variables have been removed (MDEV-32104, MariaDB 11.3):

List of All MariaDB 11.4 Releases

DateReleaseStatusRelease NotesChangelog
8 Aug 2024MariaDB 11.4.3Stable (GA)Release NotesChangelog
29 May 2024MariaDB 11.4.2Stable (GA)Release NotesChangelog
16 Feb 2024MariaDB 11.4.1RCRelease NotesChangelog
24 Dec 2023MariaDB 11.4.0AlphaRelease Notes

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.