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

1. Transactional data dictionary, completely separated from the MyISAM storage engine

Really put the data dictionary into some tables in InnoDB, and you no longer need FRM, TRG, and PAR files! The Information Schema now appears as a view of the data dictionary table. In principle, there is no need for the MyISAM data table type at all, and all system tables can be placed in InnoDB.

2.SQL role

A role is a collection of permissions. You can create roles, grant and remove roles to a user. This is convenient for rights management.

The utf8mb4 character set will become the default character set and support Unicode 9

The default character set will be changed from latin1 to utf8mb4 and the default sequenced collation will be changed from latin1_swedish_ci to utf8mb4_800_ci_ai.

3. Invisible index

You can make some indexes invisible so that the SQL optimizer will not use it, but it will continue to be updated in the background. Visibility can be restored at any time when necessary.

Bit operations can be performed on binary data

It is not only possible to perform bit operations on BIGINT, but also on [VAR] BINARY/ [TINY | MEDIUM | LONG] BLOB since 8.0.

4. Improved operation of IPv6 and UUID

INET6_ATON () and INET6_NTOA () can now perform bit operations, because INET6_ATON () now returns the VARBINARY (16) data type (128bits). The UUID operation is improved and three new functions UUID_TO_BIN (), BIN_TO_UUID () and IS_UUID () are introduced. MySQL does not have special IPv6 and UUID data types, but is saved as a VARBINARY (16) data type.

5. Persistent global variable

You can use SET PERSIST to set persistent global variables that will persist even if the server is restarted.

Improvement of performance Database Performance Schema

For example, more than 100 indexes are added to the performance database, which can be retrieved faster.

6. Refactoring SQL parser

Continuously improve the SQL analyzer step by step. The old parser has serious limitations because of its syntax complexity and top-down analysis, which makes it difficult to maintain and expand.

7. Cost model

The InnoDB buffer can now estimate how many tables and indexes are in the main memory cache, which allows the optimizer to know whether the data can be stored in memory or must be stored on disk when choosing the access method.

8. Histogram Histograms

By using histograms, users or DBA can do statistics on the data distribution, which can be used for query optimization to find an optimized query scheme.

9. Improve scanning performance

Improved the performance of InnoDB range queries, which can improve the performance of full table queries and range queries by 5-20%.

10. Refactoring BLOB

Refactoring BLOB accelerates fragment read / update operations, which can accelerate the operation of JSON data.

11. Persistent self-increment

InnoDB persists the maximum value of the self-incrementing sequence to the redo log. This improvement also fixes a very old 199th bug.

twelve。 Temporary watch

Remove support for compressing temporary tables and store the temporary table's metadata in memory.

Since MySQL8.0, we can see that MySQL is becoming more and more like Oracle.

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.