Mysql：Changes in MySQL 5.7.5 (2014-09-25, Milestone 15)：innodb_buffer_pool_size parameter is 【dynamic】

• Incompatible Change: The InnoDB storage engine can no longer be disabled. The --skip-innodb option is deprecated and has no effect, and its use results in a warning. It will be removed in a future MySQL version. This also applies to its synonyms (--innodb=OFF, --disable-innodb, and so forth).

• Incompatible Change: MySQL 5.6 deprecated passwords that used the older pre-4.1 password hashing format. Support for these passwords is now removed, which involves the following changes. Applications that use any feature no longer supported must be modified.

  • The server-side mysql_old_password authentication plugin is removed. Accounts that use this plugin are disabled at startup and the server writes an “unknown plugin” message to the error log. For instructions on upgrading accounts that use this plugin, see Migrating Away from Pre-4.1 Password Hashing and the mysql_old_password Plugin.

    The client-side mysql_old_password authentication plugin is removed from the C client library.

  • The --secure-auth option to the server and client programs is the default, but is now a no-op. It is deprecated and will be removed in a future MySQL version.

  • The --skip-secure-auth option to the server and client programs is no longer supported and using it produces an error.

  • The secure_auth system variable permits only a value of 1; a value of 0 is no longer permitted.

  • For the old_passwords system variable, a value of 1 (produce pre-4.1 hashes) is no longer permitted.

  • The OLD_PASSWORD() function is removed.

  • The mysqladmin old-password command is removed.

• MySQL now includes a server-side authentication plugin named mysql_no_login for setting up accounts that accept no client connections. This plugin enables DBAs to implement the following use cases:

  • Stored program and view objects that perform sensitive or adminstrative operations must run with elevated privileges. Less-privileged users must be able to execute these objects but not be able to directly log in as the account that has the privileges. To implement this, create a no-login account using mysql_no_login, grant it the required privileges, define objects with a DEFINER of that account, and include SQL SECURITY DEFINER in the definitions.

  • Access to a proxy account must always be by the usual proxy mechanism, never by users logging in directly to the proxy account. To implement this, assign mysql_no_login as the authentication plugin when you create the proxy account.

  For more information, see No-Login Pluggable Authentication.

Functionality Added or Changed