content_image/734618.jpg
--plugin-load-add  can be used to avoid specifying a large set of plugins as a single long unwieldy --plugin-load  argument. 

--plugin-load-add  can be given in the absence of --plugin-load , but any instance of -- plugin-load-add  that appears before --plugin-load . has no effect because --plugin-load resets the set of plugins to load. In other words, these options: 

--plugin-load=x --plugin-load-add=y 

are equivalent to this option: 

--plugin-load="x;y" 

But these options: 

--plugin-load-add=y --plugin-load=x 

are equivalent to this option: 

--plugin-load=x 

For additional information about plugin loading, see Section 5.6.1, “Installing and Uninstalling Plugins” . 

• --plugin- xxx 

Specifies an option that pertains to a server plugin. For example, many storage engines can be built as plugins, and for such engines, options for them can be specified with a --plugin  prefix. Thus, the -- innodb-file-per-table  option for InnoDB  can be specified as --plugin-innodb-file-per- table . 

For boolean options that can be enabled or disabled, the --skip  prefix and other alternative formats are supported as well (see Section 4.2.2.4, “Program Option Modifiers” ). For example, --skip-plugin- innodb-file-per-table  disables innodb-file-per-table . 

The rationale for the --plugin  prefix is that it enables plugin options to be specified unambiguously if there is a name conflict with a built-in server option. For example, were a plugin writer to name a plugin “sql”  and implement a “mode”  option, the option name might be --sql-mode , which would conflict with the built-in option of the same name. In such cases, references to the conflicting name are resolved in favor of the built-in option. To avoid the ambiguity, users can specify the plugin option as --plugin- sql-mode . Use of the --plugin  prefix for plugin options is recommended to avoid any question of ambiguity. 

• --port= port_num , -P port_num 

<img src='content_image/734618.jpg'>

