The release of the MariaDB database management system version 11.4.2 has been published, marking it as the first stable release of the 11.4 branch. The MariaDB 11.4 branch is categorized as a long-term support release and will receive support for at least 5 years. At the same time, release 11.5.1, which has candidate release status, is available, and branch 11.6 has been formed to develop new features.
The MariaDB project develops a fork from MySQL, preserving backward compatibility and distinguished by the integration of additional storage engines and enhanced capabilities. The development of MariaDB is overseen by the independent MariaDB Foundation in accordance with an open and transparent development process that is not dependent on individual vendors. MariaDB is supplied instead of MySQL in many Linux distributions (RHEL, SUSE, Fedora, openSUSE, Slackware, OpenMandriva, ROSA, Arch Linux, Debian) and is implemented in major projects such as Wikipedia, Google Cloud SQL, and Nimbuzz.
Among the changes in the MariaDB 11.4 branch compared to the previous LTS release 10.11:
- The query optimizer has been significantly improved, transitioning to a new cost model that provides more accurate predictions of the weights for each query execution plan. The previously used model was well-suited for finding optimal indexes but had issues with the applicability of table scans, index scans, or range selections. In the new model, this drawback has been eliminated by adjusting the base weights of operations related to the storage engine. For instance, for storage operations such as sequential record scans, it is now assumed that the data is stored on a fast SSD. Additionally, tuning of other optimizer weight parameters has been performed, which has enabled the use of indexes for "ORDER BY/GROUP BY" operations in subqueries and sped up operations with very small tables.
- The processing of subqueries in UPDATE and DELETE statements limited to a single table has been significantly accelerated.
- Indexes are now utilized in queries where DATE and YEAR functions are compared to constants, for example, "SELECT * FROM t2 WHERE YEAR(a) = 2024" or "SELECT * FROM t2 WHERE DATE(a)
Source: opennet.ru
