MySQL 8.0.30 GA

MySQL 8.0.30 Now officially Release . This version has made a lot of repairs at the same time , Some functions have also been enhanced and improved . Some highlights are as follows ：

GIPK（Generated Invisible Primary Keys）

When open GIPK After the model , It is allowed to display the defined primary key InnoDB surface , Automatically generate invisible primary keys . The generated primary key name is ‘my_row_id’ And cannot be changed , Users need to pay attention to the use of this keyword .

XA Transactions and replication

The replication function supports XA The state of the transaction is copied , Solved the previous replication function stay When an exception occurs in the server node , No guarantee perform XA PREPARE、XA COMMIT or XA ROLLBACK.

For any multi server replication topology ( Includes group replication ), XA Transaction status can Spread consistently , So that all servers beginning Finally in the same state . For any topology ( Including a single server , as long as Binary logging is enabled ), Can Restore to consistent state .

InnoDB doublewrite buffer

Added Innodb_doublewrite System variables , This variable can be set to DETECT_ONLY or DETECT_AND_RECOVER. Set to DETECT_ONLY when , Database page content will not be written doublewrite buffer, Do not use during recovery doublewrite buffer  Fix incomplete page writing . This setting is only used to detect incomplete page writes . Set to DETECT_AND_RECOVER when , Consistent with existing processing .

Dynamic configuration Redo Log capacity

Redo Logs now support dynamic capacity setting . Through system variables innodb_redo_log_capacity  Can increase or decrease Redo Disk capacity used by logs .InnoDB Can maintain 32 individual Redo journal , The default size of the log is 100M. User configuration innodb_redo_log_capacity after , Variable innodb_log_files_in_group and innodb_log_file_size The value of will be ignored .

change MySQL The order of fields in the primary key of some system tables

By changing , To improve the implementation of CREATE USER,DROP USER,RENAME USER Statement execution performance  

mysqldump Customize long query time

mysqldump Add a new option  -mysqld-long-query-time , With this option , Users can increase mysqldump Query the allowed elapsed time , In order to Avoid writing slow query logs , So as to reduce unnecessary logging .

Error log Components

The error log component can now stay InnoDB Start before the storage engine is available . This kind of loading error log component Control methods pass log_error_services Variable definitions .

The implicit load error log component has the following advantage :

• InnoDB The previously recorded information is fully available Is available .

• It helps to avoid the loss of log information Boot failure .

• The explicit error log component is installed and used You no longer need to install component syntax . user Just add components to log_error_services Set up .

Enterprise audit

The query time option is added to the audit log , The number and time of records sent and received can be recorded .

Encryption function  AES_ENCRYPT() and AES_DECRYPT()  Support KDF

KDF（key derivation function） By way of Secret key Information such as passwords or passphrases Pass to function , use Come on Create a strong password in cryptography . The derived key is used for encryption And decrypt the data , It is still preserved in MySQL Server example , User cannot access . Strongly recommend Use KDF, Because it provides more than Users specify passwords and other methods A simpler way , And better security .

More details Visit the official website .

Source ：https://mp.weixin.qq.com/s/h5l811FMpZH4xm6ATvU9tA