Shulou(Shulou.com)06/01 Report--

MariaDB 10.4 is its current development branch. On May 21st, the 10.4.5 RC release version was released, which is getting closer and closer to the official release. The new features of 10.4 are also of increasing concern. This article summarizes some of the blog content officially released by mariadb. For more information, you can read changelog: https://mariadb.com/kb/en/library/mariadb-1040-changelog/ of MariaDB 10.4.

Performance improvement

Because of the byte length, the performance of the Unicode character set is generally lower than that of other character sets such as latin1. MySQL8.0 has made great improvements in this area. In this respect, MariaDB 10.4 is also much faster than 10.3. Nowadays, people increasingly like to use emojis diagrams, which require the utf8 character set to be stored, so this is a very important improvement. MariaDB 10.4 is more efficient in IN () subqueries because conditions can now be pushed into materialized subqueries.

Depending on the size of the redo log, it takes a while to start and shut down the InnoDB. MariaDB has improved startup, shutdown, and purge. These improvements are particularly important given the popularity of mariabackup and xtrabackup hot backup tools. Eventually, these tools range from InnoDB shutdown (when playing back redo log) to starting a restore, so improvements in these areas greatly reduce the time it takes to dump backups.

InnoDB improvement

MariaDB 10.4 is ready for instantaneous DROP CLOLUMN operations. Without rebuilding the table, you can reorder the columns of the table. We can't emphasize how important this is. You may want to know what is the most common operation in a production environment? Adding and deleting indexes is particularly important. Another common operation is to add a new column or delete an index. By far, the most common method is to use external tools: pt-online-schema-change or gh-ost. Both tools have limitations (for example, gh-ost cannot be used in Galera Cluster). What is particularly tricky is that there are also great restrictions when tables have foreign keys. Instantaneous ADD COLUMN is already available, and changes can be made through instantaneous DROP COLUMN,schema. These instantaneous operations are also what we need. Like creating indexes, schema can make non-blocking changes, but when using replication, these operations are challenging. So even though these operations can be performed in a production environment, we recommend using pt-online-schame-change.

The expansion of Varchar columns will become faster, and changes in additional character sets and collations on non-indexed columns will be instantaneous.

General change

Another big change is in user management. The mysql.host table is no longer used and no longer created. The user's account and global permissions are stored in the mysql.global_ privtable. These changes are important for tools that manage MySQL and MariaDB users through options. In versions prior to 10.4, cases involving user management needed to be rewritten. We admit that these areas do need to be changed, but this is not helpful in maintaining MariaDB and MySQL tools. In terms of user management, MariaDB 10.4 has an option to control expired user passwords. This is definitely an important async in a good direction-it helps to better implement password management.

Finally, in version 10.4, you can set up sql_mode=MSSQL. This is an initial implementation, but at some point sql_mode=ORACLE is also the initial implementation. This shows MariaDB's focus on enterprise users-more and more users can migrate from Oracle or Microsoft SQL Server to MariaDB as more features are added and fewer migration issues are encountered.

MariaDB branch

Recently I read a blog post explaining MariaDB's views on InnoDB improvements and compatibility. The main reason is that MariaDB will no longer incorporate the new features of InnoDB from MySQL and will focus on the improvement of stability and performance. This means that MariaDB is no longer compatible with MySQL. Logical backup tools like mysqldumper/mysqlloader will be the only tools for migration. Fortunately, MariaDB has the ability to maintain his own InnoDB branch.

In terms of performance, from a historical point of view, the performance of MariaDB integrated InnoDB has improved.

For users, MariaDB10.4 will be more stable than previous versions of release. This also means that we need to learn about two different storage engine kernels-- especially performance changes. Development tools are required to support different versions of InnoDB. We will pay attention to the progress in this area. With the introduction of more and more incompatible features and major changes to mysql8.0, it makes sense to focus on developing new features rather than being compatible with MySQL.

Original text

Https://severalnines.com/blog/whats-new-mariadb-104

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.