Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-12472

InnoDB should accept XtraDB parameters, warning that they are ignored



      MariaDB Server 10.2 will not ship with Percona XtraDB at all, but only with Oracle InnoDB.
      However, XtraDB was the built-in InnoDB implementation in MariaDB Server 10.0 and 10.1.
      To ease upgrades, InnoDB in MariaDB Server 10.2 should accept the XtraDB options that were available in 10.1, and display warnings about them. Here is a list obtained with

      diff -u <(sed -ne 's/^  MYSQL_SYSVAR(\(.*\)),/\1/p' storage/xtradb/handler/ha_innodb.cc|sort) <(sed -ne 's/^  MYSQL_SYSVAR(\(.*\)),/\1/p' storage/innobase/handler/ha_innodb.cc|sort)|grep '^-[a-z]'


      Some discretion could be used. The innodb_api* settings never did anything useful in MariaDB, and they were removed in MDEV-12050 along with the unused Memcached hooks.

      innodb_additional_mem_pool_size and innodb_use_sys_malloc can be removed, because they were deprecated in Oracle MySQL 5.6 (thus, MariaDB 10.0 already) and removed in 5.7.

      innodb_adaptive_hash_index_partitions was implemented in MySQL 5.7 as innodb_adaptive_hash_index_parts. We should have an alias for that.

      The Percona setting innodb_log_checksum_algorithm (a choice of values) was replaced by the Boolean innodb_log_checksums (offering CRC-32C or none). We could map the value "none" to OFF and everything else to ON.

      The remaining parameters look like Percona additions which we can choose to ignore (issuing a warning). Perhaps some features could be ported from Percona 5.7.


          Issue Links



              • Assignee:
                sanja Oleksandr Byelkin
                marko Marko Mäkelä
              • Votes:
                0 Vote for this issue
                8 Start watching this issue


                • Created: