Beta Draft: 2017-02-25
MySQL supports invisible indexes; that is, indexes that are not
used by the optimizer. The feature applies to indexes other than
primary keys (either explicit or implicit). As of MySQL 8.0.1,
this feature is storage engine neutral (supported for any
engine). In MySQL 8.0.0, it applies only to
Indexes are visible by default. To control index invisibility
explicitly for a new index, use a
INVISIBLE keyword as part of the index
CREATE INDEX, or
CREATE TABLE t1 ( i INT, j INT, k INT, INDEX i_idx (i) INVISIBLE ) ENGINE = InnoDB; CREATE INDEX j_idx ON t1 (j) INVISIBLE; ALTER TABLE t1 ADD INDEX k_idx (k) INVISIBLE;
To alter the invisibility of an existing index, use a
keyword with the
ALTER TABLE ... ALTER INDEX
ALTER TABLE t1 ALTER INDEX i_idx INVISIBLE; ALTER TABLE t1 ALTER INDEX i_idx VISIBLE;
SELECT INDEX_NAME, IS_VISIBLE
WHERE TABLE_SCHEMA = 'db1' AND TABLE_NAME = 't1';+------------+------------+ | INDEX_NAME | IS_VISIBLE | +------------+------------+ | i_idx | YES | | j_idx | NO | | k_idx | NO | +------------+------------+
Invisible indexes make it possible to test the effect of removing an index on query performance, without making a destructive change that must be undone should the index turn out to be required. Dropping and re-adding an index can be expensive for a large table, whereas making it invisible and visible are fast, in-place operations.
If an index made invisible actually is needed or used by the optimizer, there are several ways to notice the effect of its absence on queries for the table:
Errors occur for queries that include index hints that refer to the invisible index.
Performance Schema data shows an increase in workload for affected queries.
Queries have different
Queries appear in the slow query log that did not appear there previously.
Index invisibility does not affect index maintenance. For example, an index continues to be updated per changes to table rows, and a unique index prevents insertion of duplicates into a column, regardless of whether the index is visible or invisible.
A table with no explicit primary key may still have an effective
implicit primary key if it has any
NOT NULL columns. In this case,
the first such index places the same constraint on table rows as
an explicit primary key and that index cannot be made invisible.
Consider the following table definition:
CREATE TABLE t2 ( i INT NOT NULL, j INT NOT NULL, UNIQUE j_idx (j) ) ENGINE = InnoDB;
The definition includes no explicit primary key, but the index
NOT NULL column
places the same constraint on rows as a primary key and cannot
be made invisible:
ALTER TABLE t2 ALTER INDEX j_idx INVISIBLE;ERROR 3522 (HY000): A primary key index cannot be invisible.
Now suppose that an explicit primary key is added to the table:
ALTER TABLE t2 ADD PRIMARY KEY (i);
The explicit primary key cannot be made invisible. In addition,
the unique index on
j no longer acts as an
implicit primary key and as a result can be made invisible:
ALTER TABLE t2 ALTER INDEX j_idx INVISIBLE;Query OK, 0 rows affected (0.03 sec)