No cache version.

Caching disabled. Default setting for this page:enabled (code DEF204)
If the display is too slow, you can disable the user mode to view the cached version.

Rechercher dans le manuel MySQL

26.12.2.5 The setup_threads Table

Contents

The setup_threads table lists instrumented thread classes. It exposes thread class names and attributes:

  1. mysql> SELECT * FROM performance_schema.setup_threads\G
  2. *************************** 1. row ***************************
  3.          NAME: thread/performance_schema/setup
  4.       ENABLED: YES
  5.       HISTORY: YES
  6.    PROPERTIES: singleton
  7.    VOLATILITY: 0
  8. DOCUMENTATION: NULL
  9. ...
  10. *************************** 4. row ***************************
  11.          NAME: thread/sql/main
  12.       ENABLED: YES
  13.       HISTORY: YES
  14.    PROPERTIES: singleton
  15.    VOLATILITY: 0
  16. DOCUMENTATION: NULL
  17. *************************** 5. row ***************************
  18.          NAME: thread/sql/one_connection
  19.       ENABLED: YES
  20.       HISTORY: YES
  21.    PROPERTIES: user
  22.    VOLATILITY: 0
  23. DOCUMENTATION: NULL
  24. ...
  25. *************************** 10. row ***************************
  26.          NAME: thread/sql/event_scheduler
  27.       ENABLED: YES
  28.       HISTORY: YES
  29.    PROPERTIES: singleton
  30.    VOLATILITY: 0
  31. DOCUMENTATION: NULL

The setup_threads table has these columns:

  • NAME

    The instrument name. Thread instruments begin with thread (for example, thread/sql/parser_service or thread/performance_schema/setup).

  • ENABLED

    Whether the instrument is enabled. The value is YES or NO. This column can be modified, although setting ENABLED has no effect for threads that are already running.

    For background threads, setting the ENABLED value controls whether INSTRUMENTED is set to YES or NO for threads that are subsequently created for this instrument and listed in the threads table. For foreground threads, this column has no effect; the setup_actors table takes precedence.

  • HISTORY

    Whether to log historical events for the instrument. The value is YES or NO. This column can be modified, although setting HISTORY has no effect for threads that are already running.

    For background threads, setting the HISTORY value controls whether HISTORY is set to YES or NO for threads that are subsequently created for this instrument and listed in the threads table. For foreground threads, this column has no effect; the setup_actors table takes precedence.

  • PROPERTIES

    The instrument properties. This column uses the SET data type, so multiple flags from the following list can be set per instrument:

    • singleton: The instrument has a single instance. For example, there is only one thread for the thread/sql/main instrument.

    • user: The instrument is directly related to user workload (as opposed to system workload). For example, threads such as thread/sql/one_connection executing a user session have the user property to differentiate them from system threads.

  • VOLATILITY

    The instrument volatility. This column has the same meaning as in the setup_instruments table. See Section 26.12.2.3, “The setup_instruments Table”.

  • DOCUMENTATION

    A string describing the instrument purpose. The value is NULL if no description is available.

The setup_threads table has these indexes:

  • Primary key on (NAME)

TRUNCATE TABLE is not permitted for the setup_threads table.


Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-setup-threads-table.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut