The first stable release of the new MariaDB 10.11 (10.11.2) DBMS branch has been published, within which a branch from MySQL is being developed that maintains backward compatibility and is distinguished by the integration of additional storage engines and advanced features. MariaDB development is overseen by the independent MariaDB Foundation, following an open and transparent development process independent of individual vendors. MariaDB is shipped in place of MySQL on many Linux distributions (RHEL, SUSE, Fedora, openSUSE, Slackware, OpenMandriva, ROSA, Arch Linux, Debian) and has been adopted by major projects such as Wikipedia, Google Cloud SQL, and Nimbuzz.
At the same time, the 11.0 branch is in alpha testing, which offers significant improvements and changes that break compatibility. The MariaDB 10.11 branch has been categorized as a long-term support release and will be maintained side-by-side with MariaDB 11.x until February 2028.
Key improvements in MariaDB 10.11:
- The "GRANT ... TO PUBLIC" operation has been implemented, with the help of which you can grant certain privileges to all users on the server at once.
- SUPER and "READ ONLY ADMIN" permissions are separated - the "SUPER" privilege no longer covers the "READ ONLY ADMIN" permissions (the ability to write, even if the mode is set to read-only).
- In the "ANALYZE FORMAT=JSON" inspection mode, the time spent by the query optimizer is shown.
- Resolved performance issues that occurred when reading from a table with storage scheme settings, as well as when fully scanning tables with storage scheme settings and procedures.
- Support for saving and restoring historical data from versioned tables has been added to the mariadb-dump utility.
- Added setting system_versioning_insert_history to control the ability to make changes to past versions of data in versioned tables.
- Allow changing innodb_write_io_threads and innodb_read_io_threads settings on the fly without having to restart the server.
- On the Windows platform, Windows administrators can log in as root to MariaDB without entering a password.
- The variables log_slow_min_examined_row_limit (min_examined_row_limit), log_slow_query (slow_query_log), log_slow_query_file (slow_query_log_file), and log_slow_query_time (long_query_time) have been renamed.
Source: opennet.ru