The server crashed if an account with the
CREATE ROUTINE privilege but not
EXECUTE privilege attempted
to create a stored procedure.
Security Fix: The server crashed if an account without the proper privileges attempted to create a stored procedure. (Bug#44658)
Security Fix: Four potential format string vulnerabilities were fixed (discovered by the Veracode code analysis). (Bug#44166)
The server can load plugins under the control of startup
options. For example, many storage engines can be built in
pluggable form and loaded when the server starts. In the
stands for a plugin name such as
Previously, plugin options were handled like other boolean options (see Program Option Modifiers). That is, any of these options enabled the plugin:
And these options disabled the plugin:
However, use of a boolean option for plugin loading did not
provide control over what to do if the plugin failed to start
properly: Should the server exit, or start with the plugin
disabled? The actual behavior has been that the server starts
with the plugin disabled, which can be problematic. For example,
InnoDB fails to start, existing
InnoDB tables become inaccessible, and
attempts to create new
InnoDB tables result
in tables that use the default storage engine unless the
mode has been enabled to cause an error to occur instead.
Now, there is a change in the options used to control plugin loading, such that they have a tristate format:
Do not enable the plugin.
Enable the plugin. If plugin initialization fails, start the
server anyway, but with the plugin disabled. Specifying the
without a value also enables the plugin.
Enable the plugin. If plugin initialization fails, do not start the server. In other words, force the server to run with the plugin or not at all.
FORCE are not case sensitive.
InnoDB have been built as pluggable storage
engines and that you want the server to load them at startup,
subject to these conditions: The server is allowed to run if
CSV initialization fails, but must require
InnoDB initialization succeed. To
accomplish that, use these lines in an option file:
[mysqld] csv=ON innodb=FORCE
This change is incompatible with the previous implementation if
you used options of the form
which should be changed to
is still supported and is the same as
are still supported and are the same as
See also Bug#45336.