<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h4 class="title">
      <a name="performance-schema-events-transactions-history-long-table">
      </a>
      29.12.7.3 The events_transactions_history_long Table
     </h4>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045072215232">
  </a>
  <a class="indexterm" name="idm46045072213776">
  </a>
  <p>
   The
   <a class="link" href="performance-schema-events-transactions-history-long-table.html" title="29.12.7.3 The events_transactions_history_long Table">
    <code class="literal">
     events_transactions_history_long
    </code>
   </a>
   table contains the
   <em class="replaceable">
    <code>
     N
    </code>
   </em>
   most recent
          transaction events that have ended globally, across all
          threads. Transaction events are not added to the table until
          they have ended. When the table becomes full, the oldest row
          is discarded when a new row is added, regardless of which
          thread generated either row.
  </p>
  <p>
   The Performance Schema autosizes the value of
   <em class="replaceable">
    <code>
     N
    </code>
   </em>
   is autosized at server startup.
          To set the table size explicitly, set the
   <a class="link" href="performance-schema-system-variables.html#sysvar_performance_schema_events_transactions_history_long_size">
    <code class="literal">
     performance_schema_events_transactions_history_long_size
    </code>
   </a>
   system variable at server startup.
  </p>
  <p>
   The
   <a class="link" href="performance-schema-events-transactions-history-long-table.html" title="29.12.7.3 The events_transactions_history_long Table">
    <code class="literal">
     events_transactions_history_long
    </code>
   </a>
   table has the same columns as
   <a class="link" href="performance-schema-events-transactions-current-table.html" title="29.12.7.1 The events_transactions_current Table">
    <code class="literal">
     events_transactions_current
    </code>
   </a>
   . See
   <a class="xref" href="performance-schema-events-transactions-current-table.html" title="29.12.7.1 The events_transactions_current Table">
    Section 29.12.7.1, “The events_transactions_current Table”
   </a>
   .
          Unlike
   <a class="link" href="performance-schema-events-transactions-current-table.html" title="29.12.7.1 The events_transactions_current Table">
    <code class="literal">
     events_transactions_current
    </code>
   </a>
   ,
   <a class="link" href="performance-schema-events-transactions-history-long-table.html" title="29.12.7.3 The events_transactions_history_long Table">
    <code class="literal">
     events_transactions_history_long
    </code>
   </a>
   has no indexing.
  </p>
  <p>
   <a class="link" href="truncate-table.html" title="15.1.37 TRUNCATE TABLE Statement">
    <code class="literal">
     TRUNCATE TABLE
    </code>
   </a>
   is permitted for
          the
   <a class="link" href="performance-schema-events-transactions-history-long-table.html" title="29.12.7.3 The events_transactions_history_long Table">
    <code class="literal">
     events_transactions_history_long
    </code>
   </a>
   table. It removes the rows.
  </p>
  <p>
   For more information about the relationship between the three
          transaction event tables, see
   <a class="xref" href="performance-schema-event-tables.html" title="29.9 Performance Schema Tables for Current and Historical Events">
    Section 29.9, “Performance Schema Tables for Current and Historical Events”
   </a>
   .
  </p>
  <p>
   For information about configuring whether to collect
          transaction events, see
   <a class="xref" href="performance-schema-transaction-tables.html" title="29.12.7 Performance Schema Transaction Tables">
    Section 29.12.7, “Performance Schema Transaction Tables”
   </a>
   .
  </p>
 </div>
 <br/>
</div>
