Performance Schema Setup Tables 27.12.2.2 The setup_consumers Table 27.12.2.3 The setup_instruments Table 4946 TRUNCATE TABLE  is not permitted for the  setup_consumers  table. Whether the consumer is enabled. The value is  YES  or  NO . This column can be modified. If you disable a consumer, the server does not spend time adding event information to it. The  setup_consumers  table has these indexes: The consumer name. The  setup_consumers  table has these columns: Modifications to the  setup_consumers  table affect monitoring immediately. The consumer settings in the  setup_consumers  table form a hierarchy from higher levels to lower. For detailed information about the effect of enabling different consumers, see Section 27.4.7, “Pre-Filtering by Consumer” . The  setup_consumers  table lists the types of consumers for which event information can be stored and which are enabled: TRUNCATE TABLE  is permitted for the  setup_actors  table. It removes the rows. The  setup_actors  table has these indexes: Whether to log historical events for foreground threads matched by the row. The value is  YES  or  NO . • HISTORY •Primary key on ( HOST ,  USER ,  ROLE ) • NAME • ENABLED •Primary key on ( NAME ) mysql>  SELECT * FROM performance_schema.setup_consumers; +----------------------------------+---------+ | NAME | ENABLED | +----------------------------------+---------+ | events_stages_current | NO | | events_stages_history | NO | | events_stages_history_long | NO | | events_statements_current | YES | | events_statements_history | YES | | events_statements_history_long | NO | | events_transactions_current | YES | | events_transactions_history | YES | | events_transactions_history_long | NO | | events_waits_current | NO | | events_waits_history | NO | | events_waits_history_long | NO | | global_instrumentation | YES | | thread_instrumentation | YES | | statements_digest | YES | +----------------------------------+---------+