<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="performance-schema-setup-tables">
      </a>
      29.12.2 Performance Schema Setup Tables
     </h3>
    </div>
   </div>
  </div>
  <div class="toc">
   <dl class="toc">
    <dt>
     <span class="section">
      <a href="performance-schema-setup-actors-table.html">
       29.12.2.1 The setup_actors Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-setup-consumers-table.html">
       29.12.2.2 The setup_consumers Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-setup-instruments-table.html">
       29.12.2.3 The setup_instruments Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-setup-objects-table.html">
       29.12.2.4 The setup_objects Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-setup-threads-table.html">
       29.12.2.5 The setup_threads Table
      </a>
     </span>
    </dt>
   </dl>
  </div>
  <p>
   The setup tables provide information about the current
        instrumentation and enable the monitoring configuration to be
        changed. For this reason, some columns in these tables can be
        changed if you have the
   <a class="link" href="privileges-provided.html#priv_update">
    <code class="literal">
     UPDATE
    </code>
   </a>
   privilege.
  </p>
  <p>
   The use of tables rather than individual variables for setup
        information provides a high degree of flexibility in modifying
        Performance Schema configuration. For example, you can use a
        single statement with standard SQL syntax to make multiple
        simultaneous configuration changes.
  </p>
  <p>
   These setup tables are available:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-setup-actors-table.html" title="29.12.2.1 The setup_actors Table">
       <code class="literal">
        setup_actors
       </code>
      </a>
      : How to initialize
            monitoring for new foreground threads
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-setup-consumers-table.html" title="29.12.2.2 The setup_consumers Table">
       <code class="literal">
        setup_consumers
       </code>
      </a>
      : The
            destinations to which event information can be sent and
            stored
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-setup-instruments-table.html" title="29.12.2.3 The setup_instruments Table">
       <code class="literal">
        setup_instruments
       </code>
      </a>
      : The classes
            of instrumented objects for which events can be collected
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-setup-objects-table.html" title="29.12.2.4 The setup_objects Table">
       <code class="literal">
        setup_objects
       </code>
      </a>
      : Which objects
            should be monitored
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-setup-threads-table.html" title="29.12.2.5 The setup_threads Table">
       <code class="literal">
        setup_threads
       </code>
      </a>
      : Instrumented
            thread names and attributes
     </p>
    </li>
   </ul>
  </div>
 </div>
 <br/>
</div>
