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

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

主站蜘蛛池模板: 沐川县| 壤塘县| 仁布县| 宁乡县| 中西区| 永兴县| 军事| 婺源县| 柳江县| 金平| 图们市| 新田县| 灵山县| 徐闻县| 舞钢市| 开平市| 定边县| 黄冈市| 仲巴县| 仲巴县| 越西县| 潮安县| 利辛县| 商城县| 日照市| 靖宇县| 保定市| 新竹县| 金塔县| 措美县| 吉安市| 阳泉市| 平顶山市| 左贡县| 淅川县| 繁峙县| 琼中| 达日县| 海安县| 台南县| 德惠市|