Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.4, 10.5, 10.6, 10.11, 11.0, 11.1, 11.2, 11.3
-
None
Description
We have several aliases among system variables (when the same variable has more than one name), for backward compatibility or external compatibility purposes.
When such a variable is set at runtime via one name, the value is naturally updated for both, but the source of the value isn't:
set @val= @@global.default_storage_engine; |
|
|
select variable_name, global_value, global_value_origin from information_schema.system_variables where variable_name in ('storage_engine','default_storage_engine'); |
set global storage_engine= Aria; |
select variable_name, global_value, global_value_origin from information_schema.system_variables where variable_name in ('storage_engine','default_storage_engine'); |
|
|
# Cleanup
|
set global default_storage_engine= @val; |
|
10.4 87a5d16911bb94d383480fdd49e20876ed1400f2 |
set global storage_engine= Aria; |
select variable_name, global_value, global_value_origin from information_schema.system_variables where variable_name in ('storage_engine','default_storage_engine'); |
variable_name global_value global_value_origin
|
DEFAULT_STORAGE_ENGINE Aria COMPILE-TIME |
STORAGE_ENGINE Aria SQL
|
In the output above, for both variables global_value_origin should now be SQL, but it's only set for the variable which was actually used in the statement.