Bug #31258 | Disabling a plugin with dependencies does not work with mysql-test-run.pl | ||
---|---|---|---|
Submitted: | 27 Sep 2007 20:16 | Modified: | 28 Sep 2007 16:53 |
Reporter: | Hakan Küçükyılmaz | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 6.0 | OS: | Any |
Assigned to: | Antony Curtis | CPU Architecture: | Any |
[27 Sep 2007 20:16]
Hakan Küçükyılmaz
[27 Sep 2007 22:00]
Calvin Sun
This one is required to make 6.0 tree green.
[28 Sep 2007 2:27]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/34624 ChangeSet@1.2602, 2007-09-27 19:24:33-07:00, acurtis@xiphis.org +7 -0 Bug#31258 "Disabling a plugin with dependencies does not work wth mysql-test-run.pl" Note: This patch does not implement plugin dependencies. New command line option: --disable-plugins=NAMES where NAMES is a comma seperated list of plugin names which will not be loaded automatically during initialization. Names are case-insenstive and SQL LIKE wildcards are permitted which enable disabling all plugins which start with a specific name. When initializing built-in and installed plugins, check if they have been explicitly disabled by the --disable-plugins= option.
[28 Sep 2007 2:55]
Hakan Küçükyılmaz
Just tested Antony's patch on mysql-6.0-falcon tree and it works! Best regards, Hakan
[28 Sep 2007 15:53]
Calvin Sun
this fix is needed to make 6.0 tree green.
[28 Sep 2007 16:53]
Sergei Golubchik
This is expected behavior. Falcon plugin introduces a configuration variable falcon_serial_log_dir (which can be also referred to as plugin-falcon_serial_log_dir). Note that my_getopt allows to refer to an option using an unambiguous prefix (see http://dev.mysql.com/doc/refman/5.0/en/program-options.html). And skip-var is equivalent to var=0 (http://dev.mysql.com/doc/refman/5.0/en/command-line-options.html). So, --loose-skip-plugin-falcon_serial_log is interpreted as falcon_serial_log_dir=0, and does NOT disable the plugin falcon_serial_log. There are different solutions that would help to fix symptoms of this bug - to allow unload falcon plugins - for example the patch that Antony wrote, or wl#3295, or ignoring plugin's variables if the plugin is skipped. But no solution fundamentally helps to resolve the ambiguity. Plugin authors should take care to avoid giving plugins and variables ambiguous names.