GeoffMontee, what happens now? What does --named-pipe do?

It is supposed to enable connections over named pipes. When one wants to enable/disable a plugin one can always use --plugin-named-pipe which was implemented precisely to resolve conflicts like this.

Hi serg,

what happens now? What does --named-pipe do?

I haven't tested it myself yet. I only discovered the ambiguity while documenting both options.

I do most of my testing on Linux, so I would have to set up a Windows test environment. I can definitely try to find time to do that if no one else wants to perform the test.

When one wants to enable/disable a plugin one can always use --plugin-named-pipe which was implemented precisely to resolve conflicts like this.

The plugin activation option can be prefixed with the string "plugin"? Does that mean that users should be able to do something like this?:

[mariadb]

# enable named pipe connections

named_pipe=ON

# allow named pipe authentication

plugin_load_add = auth_named_pipe

# prevent the plugin from being uninstalled

plugin_named_pipe=FORCE_PLUS_PERMANENT

Because the server first parses the command line using the built-in list options and only after that looks for plugins, I'm pretty sure --named-pipe will mean "connections over named pipes".

Yes, any command-line option that starts from --pluginname is also recognized in the alternative form of --plugin-pluginname. For example, --plugin-innodb-fast-shutdown=2 should work just fine and do exactly what you think it does.

Let's say, documentation should clarify, that one can use --plugin-named-pipe to enable the plugin avoiding the ambiguity.

Either that or it's not a bug.