The INNODB_FT_BEING_DELETED table is a snapshot
of the INNODB_FT_DELETED table that
is only used during an OPTIMIZE
TABLE maintenance operation. When
OPTIMIZE TABLE is run, the
INNODB_FT_BEING_DELETED table is emptied, and
DOC_IDs are removed from the
INNODB_FT_DELETED table. Because the
contents of INNODB_FT_BEING_DELETED typically
have a short lifetime, this table has limited utility for
monitoring or debugging. For information about running
OPTIMIZE TABLE on tables with
FULLTEXT indexes, see
Section 12.9.6, “Fine-Tuning MySQL Full-Text Search”.
This table initially appears empty, until you set the value of the
configuration variable
innodb_ft_aux_table. The output
appears similar to the example output provided for the
INNODB_FT_DELETED table.
For related usage information and examples, see Section 14.15.4, “InnoDB INFORMATION_SCHEMA FULLTEXT Index Tables”.
Table 21.7 INNODB_FT_BEING_DELETED Columns
| Column name | Description |
|---|---|
DOC_ID | The document ID of the row that is in the process of being deleted. This
value might reflect the value of an ID column that you
defined for the underlying table, or it can be a sequence
value generated by InnoDB when the
table does not contain a suitable column. This value is
used to skip rows in the
innodb_ft_index_table table,
when you do text searches before data for deleted rows is
physically removed from the FULLTEXT
index by an OPTIMIZE TABLE
statement. See Optimizing InnoDB Full-Text Indexes for
more information. |
Notes:
Use DESCRIBE or
SHOW COLUMNS to view additional
information about the columns of this table including data
types and default values.
You must have the PROCESS
privilege to query this table.
For more information about InnoDB
FULLTEXT search, see
Section 14.8.10, “InnoDB FULLTEXT Indexes”, and
Section 12.9, “Full-Text Search Functions”.