ma 28. tammik. 2019 klo 18.45 Olaf van der Spek ([email protected]) kirjoitti: > > Op ma 28 jan. 2019 om 17:17 schreef Marko Mäkelä <[email protected]>: > > > > I filed and fixed the following ticket in the upcoming MariaDB 10.3.13 > > release: > > https://jira.mariadb.org/browse/MDEV-18399 > > MDEV-18399 Recognize the deprecated parameters innodb_file_format, > > innodb_large_prefix > > Wow that was quick, thanks a lot! Got a link to the changes?
https://github.com/MariaDB/server/commit/36be0a5aef0376c526d68007da1c11ac440f0d8b > I'm curious, what's the cost of retaining removed settings? Can't be > much more than a string in an array.. The cost is not that big. Unfortunately we do not have any common infrastructure for deprecated variables that have no effect. The code is scattered in a few places, as you can see in the above change. I guess that the problem mostly exists in InnoDB and XtraDB, where parameters have been added rather liberally, without carefully considering sensible default values or deprecation policies. When I was working on MySQL at Oracle until 2016, new parameters could be added pretty much arbitrarily, but removing the parameters involved following a more rigid procedure (which, as demonstrated by this bug report, might be too lenient). My pet hate are InnoDB parameters that affect the way how DDL statements work (such as these two). The first such parameter (innodb_file_per_table) is still there. Marko -- Marko Mäkelä, Lead Developer InnoDB MariaDB Corporation
