[MDEV-12335] Server should not update 'innodb_defragment_fill_factor_n_recs' when wrong system variable provided Created: 2017-03-22 Updated: 2017-03-22 Resolved: 2017-03-22 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Venu Matcha | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
OS : Linux ubuntu16 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
||
| Attachments: |
|
| Description |
|
Steps:
Actual Result:
Attached the log vmatcha_ubuntu_mysqld_10.2.4-logerror_2.txt Expected Result:
|
| Comments |
| Comment by Elena Stepanova [ 2017-03-22 ] | |
|
Historically, MySQL/MariaDB server by default accepts unambiguous option prefixes – incomplete option names which uniquely identify the implied variable. With the current set of variables, innodb-defragment-fill-factor- is such a prefix for innodb-defragment-fill-factor-n-recs. This capability is considered a rather unfortunate legacy, and using it is discouraged, which is what the first line in vmatcha_ubuntu_mysqld_10.2.4-logerror_2.txt says:
It can be turned off by using the startup option getopt-prefix-matching=0 |