MySQL 5.7 Release Notes - Download - MySQL

More documents

Recommendations

Info

MySQL 5.7 Release Notes• Installation creates a single root account, 'root'@'localhost', that has no password.• A test database is created that is accessible by any user.Notemysql_install_db no longer creates anonymous-user accounts, even with--skip-random-passwords.The mysql_secure_installation program now has a --use-default option, which causesthe program to execute noninteractively. It can be used for unattended install operations.• Incompatible Change: MySQL now enables database administrators to establish a policy forautomatic password expiration: Any user who connects to the server using an account for which thepassword is past its permitted lifetime must change the password. The implementation has thesecomponents:• The default_password_lifetime system variable defines global password expirationpolicy. A value of N greater than zero means that passwords have a lifetime of N days. A valueof 0 disables automatic password expiration. The default is 360; passwords must be changedapproximately once per year.• The mysql.user table has new columns that store expiration policy information for individualaccounts:• password_last_changed indicates when the password was last changed. The server usesthis column when clients connect to determine whether the password is past its lifetime andmust be changed per the expiration policy in effect.• password_lifetime indicates the account password lifetime. A value of N greater than zeromeans that the password has a lifetime of N days. 0 disables automatic password expiration.NULL (the default) means that the global expiration policy applies.• The ALTER USER statement has new options to set password expiration policy for individualaccounts.If you upgrade to this release of MySQL from an earlier version, you must run mysql_upgrade(and restart the server) to incorporate the changes to the mysql.user table. For each account,mysql_upgrade uses the time at which it executes to set the password_last_changed columnand sets password_lifetime to NULL. This causes the default global expiration policy to go intoeffect (passwords have a lifetime of 360 days).For more information, see Password Expiration Policy, and ALTER USER Syntax.Functionality Added or Changed• Performance; InnoDB: InnoDB now supports multiple page_cleaner threads for flushing dirtypages from buffer pool instances. A new system variable, innodb_page_cleaners, is used tospecify the number of page_cleaner threads. The default value of 1 maintains the pre-MySQL 5.7.4configuration in which there is only a single page_cleaner thread. This enhancement builds on workcompleted in MySQL 5.6.2, which introduced a single page cleaner thread to offload buffer poolflushing work from the InnoDB master thread.• Incompatible Change: The AES_ENCRYPT() and AES_DECRYPT() functions now permit control ofthe block encryption mode and take an optional initialization vector argument:• The new block_encryption_mode system variable controls the mode for block-basedencryption algorithms. Its default value is aes-128-ecb, which signifies encryption using a keylength of 128 bits and ECB mode.16
MySQL 5.7 Release Notes• An optional init_vector argument provides an initialization vector for encryption modes thatrequire it:AES_ENCRYPT(str,key_str[,init_vector])AES_DECRYPT(crypt_str,key_str[,init_vector])• A random string of bytes to use for the initialization vector can be produced by calling the newRANDOM_BYTES() function.For more information, see Encryption and Compression Functions.These changes make statements that use AES_ENCRYPT() or AES_DECRYPT() unsafe forstatement-based replication and they cannot be stored in the query cache. Queries that useRANDOM_BYTES() are unsafe for statement-based replication and cannot be stored in the querycache.• Incompatible Change: The deprecated ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE,and NO_ZERO_IN_DATE SQL modes now do nothing. Instead, their previous effects are includedin the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). In otherwords, strict mode now means the same thing as the previous meaning of strict mode plus theERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE modes. This changereduces the number of SQL modes with an effect dependent on strict mode and makes them part ofstrict mode itself.To prepare for the SQL mode changes in this version of MySQL, it is advisable before upgrading toread SQL Mode Changes in MySQL 5.7. That discussion provides guidelines to assess whether yourapplications will be affected by these changes.The deprecated ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATESQL modes are still recognized so that statements that name them do not produce an error, but willbe removed in a future version of MySQL. To make advance preparation for versions of MySQL inwhich these modes do not exist, applications should be modified to not refer to those mode names.• InnoDB: InnoDB now supports the Transportable Tablespace feature for partitioned InnoDB tablesand individual InnoDB table partitions. This enhancement eases backup procedures for partitionedtables and enables copying of partitioned tables and individual table partitions between MySQLinstances. For additional information, see Copying Tablespaces to Another Server (TransportableTablespaces). (Bug #18121824, Bug #70196, Bug #18304194, Bug #71784)• InnoDB: Parameters used to identify an InnoDB pages are replaced by two new classes, and foldvalue and zip_size value calculations have been optimized. These changes simplify code byreducing the number of page identifier parameters passed to functions. (Bug #18073495)• InnoDB: The Fusion-io Non-Volatile Memory (NVM) file system on Linux provides atomic writecapability, which makes the InnoDB doublewrite buffer redundant. For system tablespace files(ibdata files) located on Fusion-io devices that support atomic writes, the InnoDB doublewrite bufferis automatically disabled. (Bug #18069105)• InnoDB: Reverse index leaf page scan has been optimized.btr_pcur_restore_position_func() can now perform optimistic restoration for reversecursors, which reduces block->mutex contention on the root page, especially for concurrentreverse scans. (Bug #17666170)• InnoDB: A new system variable, innodb_log_write_ahead_size, allows you to configure thewrite-ahead block size for redo logs to a value that matches the operating system or file systemcache block size in order to avoid “read-on-write” for redo log writes. Read-on-write occurs whenredo log blocks are not entirely cached to the operating system or file system due to a mismatchbetween write-ahead block size for redo logs and operating system or file system cache block size.Avoiding read-on-write improves throughput stability for redo log writes. (Bug #17571371)17
Page 1 and 2: MySQL 5.7 Release NotesAbstractThis
Page 3: MySQL 5.7 Release NotesFor addition
Page 6 and 7: MySQL 5.7 Release Notesthe value of
Page 8 and 9: MySQL 5.7 Release Notes• InnoDB:
Page 10 and 11: MySQL 5.7 Release Notes• If the s
Page 12 and 13: MySQL 5.7 Release Notes• The C cl
Page 14 and 15: MySQL 5.7 Release Notes• The Perf
Page 20 and 21: MySQL 5.7 Release Notes• CMake no
Page 22 and 23: MySQL 5.7 Release Notes• Clients
Page 30 and 31: MySQL 5.7 Release Notesthe specifie
Page 32 and 33: MySQL 5.7 Release Notes• A memory
Page 34 and 35: MySQL 5.7 Release Notes• A LIMIT
Page 36 and 37: MySQL 5.7 Release Notes• The make
Page 38 and 39: MySQL 5.7 Release Notes• For loga
Page 40 and 41: MySQL 5.7 Release NotesThis informa
Page 42 and 43: MySQL 5.7 Release NotesAborted_conn
Page 44 and 45: MySQL 5.7 Release NotesApplications
Page 50 and 51: MySQL 5.7 Release Notes• Replicat
Page 52 and 53: MySQL 5.7 Release Notes• Within a
Page 54 and 55: MySQL 5.7 Release Notes• Reads of
Page 56 and 57: MySQL 5.7 Release Notesthe deprecat
Page 58 and 59: MySQL 5.7 Release NotesHere, the SE
Page 60 and 61: MySQL 5.7 Release Notes• The setu
Page 62 and 63: MySQL 5.7 Release NotesFor upgrades
Page 64 and 65: MySQL 5.7 Release NotesTrigger db_n
Page 66 and 67:
MySQL 5.7 Release Notesused and pri
Page 68 and 69:
MySQL 5.7 Release Notes• CMake no
Page 70 and 71:
MySQL 5.7 Release Notes• Performa
Page 72 and 73:
MySQL 5.7 Release Notes• InnoDB:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
MySQL 5.7 Release Notesdirectory. T
Page 80 and 81:
MySQL 5.7 Release Notes• Replicat
Page 82 and 83:
MySQL 5.7 Release NotesThis fix mov
Page 84 and 85:
MySQL 5.7 Release Notes• Replicat
Page 86 and 87:
MySQL 5.7 Release Notes• INSERT .
Page 88 and 89:
MySQL 5.7 Release Notes• In debug
Page 90 and 91:
MySQL 5.7 Release Notes• When a p
Page 92 and 93:
MySQL 5.7 Release Notes• If an ac
Page 94 and 95:
MySQL 5.7 Release Notes• Full-tex
Page 96 and 97:
MySQL 5.7 Release Notes• Some sub
Page 98 and 99:
Page 100 and 101:
MySQL 5.7 Release Notes• If a use
Page 102 and 103:
MySQL 5.7 Release Notes• FLUSH•
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
MySQL 5.7 Release Notesto stop with
Page 110 and 111:
MySQL 5.7 Release Notes• Windows
Page 112 and 113:
MySQL 5.7 Release Notes• A mysys
Page 114 and 115:
MySQL 5.7 Release Notes• The obso
Page 116 and 117:
MySQL 5.7 Release Notes• Adding a
Page 118 and 119:
MySQL 5.7 Release Notesand reads op
Page 120 and 121:
MySQL 5.7 Release Notes• Cluster
Page 122:
122
show all

MySQL 5.7 Release Notes - Download - MySQL

Create successful ePaper yourself

Delete template?

Save as template?