The INFORMATION_SCHEMA INNODB_FT_CONFIG Table 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.10.6, “Fine-Tuning MySQL Full-Text Search” . This table is empty initially. Before querying it, set the value of the  innodb_ft_aux_table  system variable to the name (including the database name) of the table that contains the  FULLTEXT index (for example,  test/articles ). The output appears similar to the example provided for the INNODB_FT_DELETED  table. For related usage information and examples, see Section 15.15.4, “InnoDB INFORMATION_SCHEMA FULLTEXT Index Tables” . The  INNODB_FT_BEING_DELETED  table has these columns: • 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 contains no suitable column. This value is used when you perform text searches, to skip rows in the  INNODB_FT_INDEX_TABLE  table before data for deleted rows is physically removed from the  FULLTEXT  index by an  OPTIMIZE TABLE  statement. For more information, see Optimizing InnoDB Full-Text Indexes. Notes •Use the  INFORMATION_SCHEMA COLUMNS  table or the  SHOW COLUMNS  statement 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 15.6.2.4, “InnoDB Full-Text Indexes” , and Section 12.10, “Full-Text Search Functions” . 26.4.15 The INFORMATION_SCHEMA INNODB_FT_CONFIG Table The  INNODB_FT_CONFIG  table provides metadata about the  FULLTEXT  index and associated processing for an  InnoDB  table. This table is empty initially. Before querying it, set the value of the  innodb_ft_aux_table  system variable to the name (including the database name) of the table that contains the  FULLTEXT  index (for example,  test/articles ). For related usage information and examples, see Section 15.15.4, “InnoDB INFORMATION_SCHEMA FULLTEXT Index Tables” . The  INNODB_FT_CONFIG  table has these columns: • KEY • optimize_checkpoint_limit : The number of seconds after which an  OPTIMIZE TABLE  run stops. 4862 The name designating an item of metadata for an  InnoDB  table containing a  FULLTEXT  index. The values for this column might change, depending on the needs for performance tuning and debugging for  InnoDB  full-text processing. The key names and their meanings include: