The
          events_transactions_history_long
          table contains the N 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.
        
          The Performance Schema autosizes the value of
          N is autosized at server startup.
          To set the table size explicitly, set the
          performance_schema_events_transactions_history_long_size
          system variable at server startup.
        
          The
          events_transactions_history_long
          table has the same columns as
          events_transactions_current. See
          Section 25.12.7.1, “The events_transactions_current Table”.
        
          TRUNCATE TABLE is permitted for
          the
          events_transactions_history_long
          table. It removes the rows.
        
For more information about the relationship between the three transaction event tables, see Section 25.9, “Performance Schema Tables for Current and Historical Events”.
For information about configuring whether to collect transaction events, see Section 25.12.7, “Performance Schema Transaction Tables”.