[MDEV-20226] Make plugin activation options into dynamic global system variables Created: 2019-07-31 Updated: 2019-08-03 Resolved: 2019-08-03 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Configuration, Plugins, Variables |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Sergei Golubchik |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
MariaDB Server currently dynamically constructs "plugin activation options", so that plugins can be unloaded at startup, or they can be prevented from being uninstalled, etc. https://mariadb.com/kb/en/library/plugin-overview/#configuring-plugin-activation-at-server-startup See here: https://github.com/MariaDB/server/blob/mariadb-10.4.7/sql/sql_plugin.cc#L3726 Some users would like these options to be fully-fledged global system variables that can be changed dynamically, so you could do things like this:
The users who requested this also requested that if a plugin gets unloaded dynamically, then the server should remember the plugin's existing system variable values, and it should re-use those values if the plugin is later dynamically reloaded. However, I am unsure if changing these plugin activation options to dynamic global system variables would actually add value, or if it would actually create more problems. For example, one potential problem is that it might make 'FORCE_PLUS_PERMANENT' less secure. If a plugin is set to 'FORCE_PLUS_PERMANENT', then a DBA could just dynamically change it to OFF, and then they could uninstall the plugin anyway. i.e. they could do something like this:
|
| Comments |
| Comment by Sergei Golubchik [ 2019-08-03 ] |
|
If you want to disable a plugin permanently, use UNINSTALL PLUGIN. |