官术网_书友最值得收藏!

Using extended keys with InnoDB and XtraDB

When creating an execution plan for a query, the MariaDB optimizer makes a cost-based decision about whether or not to use one or more indexes instead of reading through a table row-by-row. Indexes are often, but not always the faster choice. The extended key's optimization improves the index lookups for InnoDB and XtraDB tables.

How to do it...

  1. Launch the mysql command-line client application and connect it to our MariaDB server as the root user or as a user with the SUPER privilege.
  2. Enable the extended keys optimization with the following command:
    SET GLOBAL optimizer_switch='extended_keys=on';
    
  3. Add the following code to our my.cnf or my.ini file (or to an existing [mysqld] section):
    [mysqld]
  4. optimizer_switch = 'extended_keys=on' verifies that extended_keys is set to on with the following command:
    SHOW VARIABLES LIKE 'optimizer_switch'\G
    

How it works...

In this recipe, we turn on the extended_keys optimization globally for the running server and we then make the change permanent by adding it to our my.cnf config file. In this way, we turn the feature on, and then ensure that it stays on, without having to restart MariaDB.

There's more...

Many InnoDB or XtraDB tables have more than one key, for example, a primary key on the id column and a secondary key on the username column. Using the extended_keys optimization, MariaDB is able to create execution plans for some queries, which only touch the indexes of those keys. It does this by looking at the keys, and if all of the information that we are looking for is present, MariaDB uses that information instead of looking through tables row by row.

See also

主站蜘蛛池模板: 塔河县| 库伦旗| 丰城市| 习水县| 广灵县| 集贤县| 营山县| 卢龙县| 襄樊市| 周至县| 泗水县| 金坛市| 自治县| 白朗县| 曲靖市| 连州市| 云南省| 建昌县| 香河县| 治多县| 叙永县| 台安县| 巴林右旗| 本溪| 潜江市| 黎城县| 张家界市| 屏南县| 道孚县| 长葛市| 富平县| 平阴县| 黄平县| 宽城| 庄河市| 乐亭县| 太仆寺旗| 泾川县| 疏勒县| 滦平县| 聊城市|