Movatterモバイル変換

CACHE INDEX {tbl_index_list [,tbl_index_list] ...    |tbl_name PARTITION (partition_list)  }  INkey_cache_nametbl_index_list:tbl_name [{INDEX|KEY} (index_name[,index_name] ...)]partition_list: {partition_name[,partition_name] ...  | ALL}

TheCACHE INDEX statement assigns table indexes to a specific key cache. It applies only toMyISAM tables, including partitionedMyISAM tables. After the indexes have been assigned, they can be preloaded into the cache if desired withLOAD INDEX INTO CACHE.

The following statement assigns indexes from the tablest1,t2, andt3 to the key cache namedhot_cache:

mysql> CACHE INDEX t1, t2, t3 IN hot_cache;+---------+--------------------+----------+----------+| Table   | Op                 | Msg_type | Msg_text |+---------+--------------------+----------+----------+| test.t1 | assign_to_keycache | status   | OK       || test.t2 | assign_to_keycache | status   | OK       || test.t3 | assign_to_keycache | status   | OK       |+---------+--------------------+----------+----------+

The syntax ofCACHE INDEX enables you to specify that only particular indexes from a table should be assigned to the cache. However, the implementation assigns all the table's indexes to the cache, so there is no reason to specify anything other than the table name.

The key cache referred to in aCACHE INDEX statement can be created by setting its size with a parameter setting statement or in the server parameter settings. For example:

SET GLOBAL keycache1.key_buffer_size=128*1024;

Key cache parameters are accessed as members of a structured system variable. SeeSection 7.1.9.5, “Structured System Variables”.

A key cache must exist before you assign indexes to it, or an error occurs:

mysql> CACHE INDEX t1 IN non_existent_cache;ERROR 1284 (HY000): Unknown key cache 'non_existent_cache'

By default, table indexes are assigned to the main (default) key cache created at the server startup. When a key cache is destroyed, all indexes assigned to it are reassigned to the default key cache.

Index assignment affects the server globally: If one client assigns an index to a given cache, this cache is used for all queries involving the index, no matter which client issues the queries.

CACHE INDEX is supported for partitionedMyISAM tables. You can assign one or more indexes for one, several, or all partitions to a given key cache. For example, you can do the following:

CREATE TABLE pt (c1 INT, c2 VARCHAR(50), INDEX i(c1))    ENGINE=MyISAM    PARTITION BY HASH(c1)    PARTITIONS 4;SET GLOBAL kc_fast.key_buffer_size = 128 * 1024;SET GLOBAL kc_slow.key_buffer_size = 128 * 1024;CACHE INDEX pt PARTITION (p0) IN kc_fast;CACHE INDEX pt PARTITION (p1, p3) IN kc_slow;

The previous set of statements performs the following actions:

If you wish instead to assign the indexes for all partitions in tablept to a single key cache namedkc_all, you can use either of the following two statements:

CACHE INDEX pt PARTITION (ALL) IN kc_all;CACHE INDEX pt IN kc_all;

The two statements just shown are equivalent, and issuing either one has exactly the same effect. In other words, if you wish to assign indexes for all partitions of a partitioned table to the same key cache, thePARTITION (ALL) clause is optional.

When assigning indexes for multiple partitions to a key cache, the partitions need not be contiguous, and you need not list their names in any particular order. Indexes for any partitions not explicitly assigned to a key cache automatically use the server default key cache.

Index preloading is also supported for partitionedMyISAM tables. For more information, seeSection 15.7.8.5, “LOAD INDEX INTO CACHE Statement”.