Installing and Uninstalling Plugins Tells the server to disable the plugin. This may not be possible for certain built-in plugins, such as mysql_native_password . Tells the server to enable the plugin. (Specifying the option as  -- plugin_name  without a value has the same effect.) If the plugin fails to initialize, the server runs with the plugin disabled. Tells the server to enable the plugin, but if plugin initialization fails, the server does not start. In other words, this option forces the server to run with the plugin enabled or not at all. Like  FORCE , but in addition prevents the plugin from being unloaded at runtime. If a user attempts to do so with  UNINSTALL PLUGIN , an error occurs. Plugin activation states are visible in the  LOAD_OPTION  column of the  INFORMATION_SCHEMA.PLUGINS table. Suppose that  CSV ,  BLACKHOLE , and  ARCHIVE  are built-in pluggable storage engines and that you want the server to load them at startup, subject to these conditions: The server is permitted to run if  CSV initialization fails, must require that  BLACKHOLE  initialization succeeds, and should disable  ARCHIVE . To accomplish that, use these lines in an option file: The  --enable- plugin_name  option format is a synonym for  -- plugin_name =ON . The --disable- plugin_name  and  --skip- plugin_name  option formats are synonyms for -- plugin_name =OFF . If a plugin is disabled, either explicitly with  OFF  or implicitly because it was enabled with  ON  but fails to initialize, aspects of server operation requiring the plugin change. For example, if the plugin implements a storage engine, existing tables for the storage engine become inaccessible, and attempts to create new tables for the storage engine result in tables that use the default storage engine unless the NO_ENGINE_SUBSTITUTION  SQL mode is enabled to cause an error to occur instead. Disabling a plugin may require adjustment to other options. For example, if you start the server using --skip-innodb  to disable  InnoDB , other  innodb_ xxx  options likely also need to be omitted at startup. In addition, because  InnoDB  is the default storage engine, it cannot start unless you specify another available storage engine with  --default_storage_engine . You must also set  -- default_tmp_storage_engine . At runtime, the  UNINSTALL PLUGIN  statement disables and uninstalls a plugin known to the server. The statement unloads the plugin and removes it from the  mysql.plugin  system table, if it is registered there. For this reason,  UNINSTALL PLUGIN  statement requires the  DELETE  privilege for the  mysql.plugin table. With the plugin no longer registered in the table, the server does not load the plugin during subsequent restarts. UNINSTALL PLUGIN  can unload a plugin regardless of whether it was loaded at runtime with  INSTALL PLUGIN  or at startup with a plugin-loading option, subject to these conditions: 1077 Uninstalling Plugins • -- plugin_name [=ON] • -- plugin_name =FORCE • -- plugin_name =FORCE_PLUS_PERMANENT [mysqld] csv=ON blackhole=FORCE archive=OFF