Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
11.0.1
-
None
Description
Deprecated variables should ideally
- return a warning when they are modified
- have their description updated
This is only partially implemented. For example, of the variables marked as deprecated in the 11.0.1 release notes, innodb_file_per_table returns a warning when modified, but its description remains unmodified:
set global innodb_file_per_table=0;
|
Query OK, 0 rows affected, 1 warning (0.000 sec)
|
|
Warning (Code 1287): '@@innodb_file_per_table' is deprecated and will
|
be removed in a future release
|
|
mysql [localhost:11001] {msandbox} ((none)) > SELECT * FROM
|
INFORMATION_SCHEMA.SYSTEM_VARIABLES WHERE
|
VARIABLE_NAME LIKE 'innodb_file_per_t%'\G
|
*************************** 1. row ***************************
|
VARIABLE_NAME: INNODB_FILE_PER_TABLE
|
...
|
VARIABLE_COMMENT: Stores each InnoDB table to an .ibd file in the database dir.
|
...
|
However, innodb_defragment_n_pages for example does neither:
set global innodb_defragment_n_pages=7;
|
Query OK, 0 rows affected (0.000 sec)
|
The descriptions should be adjusted and a warning returned in all cases to alert users that these variables are deprecated.
Attachments
Issue Links
- is blocked by
-
MDEV-28671 Presentation of aliases in `mariadbd --verbose --help` is highly redundant
- Stalled
- relates to
-
MDEV-30332 PLUGIN_VAR_DEPRECATED fails to throw a warning on startup
- Closed
-
MDEV-33503 innodb_log_files_in_group is quietly ignored
- Confirmed