<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="performance-schema-replication-tables">
      </a>
      29.12.11 Performance Schema Replication Tables
     </h3>
    </div>
   </div>
  </div>
  <div class="toc">
   <dl class="toc">
    <dt>
     <span class="section">
      <a href="performance-schema-binary-log-transaction-compression-stats-table.html">
       29.12.11.1 The binary_log_transaction_compression_stats Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-applier-configuration-table.html">
       29.12.11.2 The replication_applier_configuration Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-applier-filters-table.html">
       29.12.11.3 The replication_applier_filters Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-applier-global-filters-table.html">
       29.12.11.4 The replication_applier_global_filters Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-applier-status-table.html">
       29.12.11.5 The replication_applier_status Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-applier-status-by-coordinator-table.html">
       29.12.11.6 The replication_applier_status_by_coordinator Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-applier-status-by-worker-table.html">
       29.12.11.7 The replication_applier_status_by_worker Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-asynchronous-connection-failover-table.html">
       29.12.11.8 The replication_asynchronous_connection_failover Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-asynchronous-connection-failover-managed-table.html">
       29.12.11.9 The replication_asynchronous_connection_failover_managed Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-group-communication-information-table.html">
       29.12.11.10 The replication_group_communication_information Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-connection-configuration-table.html">
       29.12.11.11 The replication_connection_configuration Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-group-configuration-version-table.html">
       29.12.11.12 The replication_group_configuration_version Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-connection-status-table.html">
       29.12.11.13 The replication_connection_status Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-group-member-actions-table.html">
       29.12.11.14 The replication_group_member_actions Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-group-member-stats-table.html">
       29.12.11.15 The replication_group_member_stats Table
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="performance-schema-replication-group-members-table.html">
       29.12.11.16 The replication_group_members Table
      </a>
     </span>
    </dt>
   </dl>
  </div>
  <p>
   The Performance Schema provides tables that expose replication
        information. This is similar to the information available from
        the
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW
        REPLICA STATUS
    </code>
   </a>
   statement, but representation in table
        form is more accessible and has usability benefits:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
       <code class="literal">
        SHOW
            REPLICA STATUS
       </code>
      </a>
      output is useful for visual
            inspection, but not so much for programmatic use. By
            contrast, using the Performance Schema tables, information
            about replica status can be searched using general
      <a class="link" href="select.html" title="15.2.13 SELECT Statement">
       <code class="literal">
        SELECT
       </code>
      </a>
      queries, including
            complex
      <code class="literal">
       WHERE
      </code>
      conditions, joins, and so
            forth.
     </p>
    </li>
    <li class="listitem">
     <p>
      Query results can be saved in tables for further analysis,
            or assigned to variables and thus used in stored procedures.
     </p>
    </li>
    <li class="listitem">
     <p>
      The replication tables provide better diagnostic
            information. For multithreaded replica operation,
      <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
       <code class="literal">
        SHOW
            REPLICA STATUS
       </code>
      </a>
      reports all coordinator and worker
            thread errors using the
      <code class="literal">
       Last_SQL_Errno
      </code>
      and
      <code class="literal">
       Last_SQL_Error
      </code>
      fields, so only the
            most recent of those errors is visible and information can
            be lost. The replication tables store errors on a per-thread
            basis without loss of information.
     </p>
    </li>
    <li class="listitem">
     <p>
      The last seen transaction is visible in the replication
            tables on a per-worker basis. This is information not
            available from
      <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
       <code class="literal">
        SHOW
            REPLICA STATUS
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      Developers familiar with the Performance Schema interface
            can extend the replication tables to provide additional
            information by adding rows to the tables.
     </p>
    </li>
   </ul>
  </div>
  <h4>
   <a name="idm46045071758896">
   </a>
   Replication Table Descriptions
  </h4>
  <p>
   The Performance Schema provides the following
        replication-related tables:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      Tables that contain information about the connection of the
            replica to the source:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-connection-configuration-table.html" title="29.12.11.11 The replication_connection_configuration Table">
          <code class="literal">
           replication_connection_configuration
          </code>
         </a>
         :
                Configuration parameters for connecting to the source
        </p>
       </li>
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-connection-status-table.html" title="29.12.11.13 The replication_connection_status Table">
          <code class="literal">
           replication_connection_status
          </code>
         </a>
         :
                Current status of the connection to the source
        </p>
       </li>
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-asynchronous-connection-failover-table.html" title="29.12.11.8 The replication_asynchronous_connection_failover Table">
          <code class="literal">
           replication_asynchronous_connection_failover
          </code>
         </a>
         :
                Source lists for the asynchronous connection failover
                mechanism
        </p>
       </li>
      </ul>
     </div>
    </li>
    <li class="listitem">
     <p>
      Tables that contain general (not thread-specific)
            information about the transaction applier:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-applier-configuration-table.html" title="29.12.11.2 The replication_applier_configuration Table">
          <code class="literal">
           replication_applier_configuration
          </code>
         </a>
         :
                Configuration parameters for the transaction applier on
                the replica.
        </p>
       </li>
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-applier-status-table.html" title="29.12.11.5 The replication_applier_status Table">
          <code class="literal">
           replication_applier_status
          </code>
         </a>
         :
                Current status of the transaction applier on the
                replica.
        </p>
       </li>
      </ul>
     </div>
    </li>
    <li class="listitem">
     <p>
      Tables that contain information about specific threads
            responsible for applying transactions received from the
            source:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-applier-status-by-coordinator-table.html" title="29.12.11.6 The replication_applier_status_by_coordinator Table">
          <code class="literal">
           replication_applier_status_by_coordinator
          </code>
         </a>
         :
                Status of the coordinator thread (empty unless the
                replica is multithreaded).
        </p>
       </li>
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-applier-status-by-worker-table.html" title="29.12.11.7 The replication_applier_status_by_worker Table">
          <code class="literal">
           replication_applier_status_by_worker
          </code>
         </a>
         :
                Status of the applier thread or worker threads if the
                replica is multithreaded.
        </p>
       </li>
      </ul>
     </div>
    </li>
    <li class="listitem">
     <p>
      Tables that contain information about channel based
            replication filters:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-applier-filters-table.html" title="29.12.11.3 The replication_applier_filters Table">
          <code class="literal">
           replication_applier_filters
          </code>
         </a>
         :
                Provides information about the replication filters
                configured on specific replication channels.
        </p>
       </li>
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-applier-global-filters-table.html" title="29.12.11.4 The replication_applier_global_filters Table">
          <code class="literal">
           replication_applier_global_filters
          </code>
         </a>
         :
                Provides information about global replication filters,
                which apply to all replication channels.
        </p>
       </li>
      </ul>
     </div>
    </li>
    <li class="listitem">
     <p>
      Tables that contain information about Group Replication
            members:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-group-members-table.html" title="29.12.11.16 The replication_group_members Table">
          <code class="literal">
           replication_group_members
          </code>
         </a>
         :
                Provides network and status information for group
                members.
        </p>
       </li>
       <li class="listitem">
        <p>
         <a class="link" href="performance-schema-replication-group-member-stats-table.html" title="29.12.11.15 The replication_group_member_stats Table">
          <code class="literal">
           replication_group_member_stats
          </code>
         </a>
         :
                Provides statistical information about group members and
                transactions in which they participate.
        </p>
       </li>
      </ul>
     </div>
     <p>
      For more information see
      <a class="xref" href="group-replication-monitoring.html" title="20.4 Monitoring Group Replication">
       Section 20.4, “Monitoring Group Replication”
      </a>
      .
     </p>
    </li>
   </ul>
  </div>
  <p>
   The following Performance Schema replication tables continue to
        be populated when the Performance Schema is disabled:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-replication-connection-configuration-table.html" title="29.12.11.11 The replication_connection_configuration Table">
       <code class="literal">
        replication_connection_configuration
       </code>
      </a>
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-replication-connection-status-table.html" title="29.12.11.13 The replication_connection_status Table">
       <code class="literal">
        replication_connection_status
       </code>
      </a>
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-replication-asynchronous-connection-failover-table.html" title="29.12.11.8 The replication_asynchronous_connection_failover Table">
       <code class="literal">
        replication_asynchronous_connection_failover
       </code>
      </a>
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-replication-applier-configuration-table.html" title="29.12.11.2 The replication_applier_configuration Table">
       <code class="literal">
        replication_applier_configuration
       </code>
      </a>
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-replication-applier-status-table.html" title="29.12.11.5 The replication_applier_status Table">
       <code class="literal">
        replication_applier_status
       </code>
      </a>
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-replication-applier-status-by-coordinator-table.html" title="29.12.11.6 The replication_applier_status_by_coordinator Table">
       <code class="literal">
        replication_applier_status_by_coordinator
       </code>
      </a>
     </p>
    </li>
    <li class="listitem">
     <p>
      <a class="link" href="performance-schema-replication-applier-status-by-worker-table.html" title="29.12.11.7 The replication_applier_status_by_worker Table">
       <code class="literal">
        replication_applier_status_by_worker
       </code>
      </a>
     </p>
    </li>
   </ul>
  </div>
  <p>
   The exception is local timing information (start and end
        timestamps for transactions) in the replication tables
   <a class="link" href="performance-schema-replication-connection-status-table.html" title="29.12.11.13 The replication_connection_status Table">
    <code class="literal">
     replication_connection_status
    </code>
   </a>
   ,
   <a class="link" href="performance-schema-replication-applier-status-by-coordinator-table.html" title="29.12.11.6 The replication_applier_status_by_coordinator Table">
    <code class="literal">
     replication_applier_status_by_coordinator
    </code>
   </a>
   ,
        and
   <a class="link" href="performance-schema-replication-applier-status-by-worker-table.html" title="29.12.11.7 The replication_applier_status_by_worker Table">
    <code class="literal">
     replication_applier_status_by_worker
    </code>
   </a>
   .
        This information is not collected when the Performance Schema is
        disabled.
  </p>
  <p>
   The following sections describe each replication table in more
        detail, including the correspondence between the columns
        produced by
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW
        REPLICA STATUS
    </code>
   </a>
   and the replication table columns in
        which the same information appears.
  </p>
  <p>
   The remainder of this introduction to the replication tables
        describes how the Performance Schema populates them and which
        fields from
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW
        REPLICA STATUS
    </code>
   </a>
   are not represented in the tables.
  </p>
  <h4>
   <a name="idm46045071701552">
   </a>
   Replication Table Life Cycle
  </h4>
  <p>
   The Performance Schema populates the replication tables as
        follows:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      Prior to execution of
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE
            REPLICATION SOURCE TO
       </code>
      </a>
      , the tables are empty.
     </p>
    </li>
    <li class="listitem">
     <p>
      After
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION SOURCE
            TO
       </code>
      </a>
      , the configuration parameters can be seen in
            the tables. At this time, there are no active replication
            threads, so the
      <code class="literal">
       THREAD_ID
      </code>
      columns are
      <code class="literal">
       NULL
      </code>
      and the
      <code class="literal">
       SERVICE_STATE
      </code>
      columns have a value of
      <code class="literal">
       OFF
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      After
      <a class="link" href="start-replica.html" title="15.4.2.4 START REPLICA Statement">
       <code class="literal">
        START
            REPLICA
       </code>
      </a>
      , non-null
      <code class="literal">
       THREAD_ID
      </code>
      values can be seen. Threads that are idle or active have a
      <code class="literal">
       SERVICE_STATE
      </code>
      value of
      <code class="literal">
       ON
      </code>
      . The thread that connects to the
            source has a value of
      <code class="literal">
       CONNECTING
      </code>
      while it
            establishes the connection, and
      <code class="literal">
       ON
      </code>
      thereafter as long as the connection lasts.
     </p>
    </li>
    <li class="listitem">
     <p>
      After
      <a class="link" href="stop-replica.html" title="15.4.2.5 STOP REPLICA Statement">
       <code class="literal">
        STOP
            REPLICA
       </code>
      </a>
      , the
      <code class="literal">
       THREAD_ID
      </code>
      columns
            become
      <code class="literal">
       NULL
      </code>
      and the
      <code class="literal">
       SERVICE_STATE
      </code>
      columns for threads that no
            longer exist have a value of
      <code class="literal">
       OFF
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      The tables are preserved after
      <a class="link" href="stop-replica.html" title="15.4.2.5 STOP REPLICA Statement">
       <code class="literal">
        STOP
            REPLICA
       </code>
      </a>
      or threads stopping due to an error.
     </p>
    </li>
    <li class="listitem">
     <p>
      The
      <a class="link" href="performance-schema-replication-applier-status-by-worker-table.html" title="29.12.11.7 The replication_applier_status_by_worker Table">
       <code class="literal">
        replication_applier_status_by_worker
       </code>
      </a>
      table is nonempty only when the replica is operating in
            multithreaded mode. That is, if the
      <a class="link" href="replication-options-replica.html#sysvar_replica_parallel_workers">
       <code class="literal">
        replica_parallel_workers
       </code>
      </a>
      system variable is greater than 0, this table is populated
            when
      <a class="link" href="start-replica.html" title="15.4.2.4 START REPLICA Statement">
       <code class="literal">
        START
            REPLICA
       </code>
      </a>
      is executed, and the number of rows shows
            the number of workers.
     </p>
    </li>
   </ul>
  </div>
  <h4>
   <a name="idm46045071674896">
   </a>
   Replica Status Information Not In the Replication Tables
  </h4>
  <p>
   The information in the Performance Schema replication tables
        differs somewhat from the information available from
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW
        REPLICA STATUS
    </code>
   </a>
   because the tables are oriented toward
        use of global transaction identifiers (GTIDs), not file names
        and positions, and they represent server UUID values, not server
        ID values. Due to these differences, several
   <a class="link" href="show-replica-status.html" title="15.7.7.35 SHOW REPLICA STATUS Statement">
    <code class="literal">
     SHOW
        REPLICA STATUS
    </code>
   </a>
   columns are not preserved in the
        Performance Schema replication tables, or are represented a
        different way:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      The following fields refer to file names and positions and
            are not preserved:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-none"><div class="docs-select-all right" id="sa55666917"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none">Master_Log_File
Read_Master_Log_Pos
Relay_Log_File
Relay_Log_Pos
Relay_Master_Log_File
Exec_Master_Log_Pos
Until_Condition
Until_Log_File
Until_Log_Pos</code></pre>
     </div>
    </li>
    <li class="listitem">
     <p>
      The
      <code class="literal">
       Master_Info_File
      </code>
      field is not
            preserved. It refers to the
      <code class="filename">
       master.info
      </code>
      file used for the replica's source metadata repository,
            which has been superseded by the use of crash-safe tables
            for the repository.
     </p>
    </li>
    <li class="listitem">
     <p>
      The following fields are based on
      <a class="link" href="replication-options.html#sysvar_server_id">
       <code class="literal">
        server_id
       </code>
      </a>
      , not
      <a class="link" href="replication-options.html#sysvar_server_uuid">
       <code class="literal">
        server_uuid
       </code>
      </a>
      , and are not
            preserved:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-none"><div class="docs-select-all right" id="sa7404917"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none">Master_Server_Id
Replicate_Ignore_Server_Ids</code></pre>
     </div>
    </li>
    <li class="listitem">
     <p>
      The
      <code class="literal">
       Skip_Counter
      </code>
      field is based on event
            counts, not GTIDs, and is not preserved.
     </p>
    </li>
    <li class="listitem">
     <p>
      These error fields are aliases for
      <code class="literal">
       Last_SQL_Errno
      </code>
      and
      <code class="literal">
       Last_SQL_Error
      </code>
      , so they are not
            preserved:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-none"><div class="docs-select-all right" id="sa37235329"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none">Last_Errno
Last_Error</code></pre>
     </div>
     <p>
      In the Performance Schema, this error information is
            available in the
      <code class="literal">
       LAST_ERROR_NUMBER
      </code>
      and
      <code class="literal">
       LAST_ERROR_MESSAGE
      </code>
      columns of the
      <a class="link" href="performance-schema-replication-applier-status-by-worker-table.html" title="29.12.11.7 The replication_applier_status_by_worker Table">
       <code class="literal">
        replication_applier_status_by_worker
       </code>
      </a>
      table (and
      <a class="link" href="performance-schema-replication-applier-status-by-coordinator-table.html" title="29.12.11.6 The replication_applier_status_by_coordinator Table">
       <code class="literal">
        replication_applier_status_by_coordinator
       </code>
      </a>
      if the replica is multithreaded). Those tables provide more
            specific per-thread error information than is available from
      <code class="literal">
       Last_Errno
      </code>
      and
      <code class="literal">
       Last_Error
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      Fields that provide information about command-line filtering
            options is not preserved:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-none"><div class="docs-select-all right" id="sa61238406"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none">Replicate_Do_DB
Replicate_Ignore_DB
Replicate_Do_Table
Replicate_Ignore_Table
Replicate_Wild_Do_Table
Replicate_Wild_Ignore_Table</code></pre>
     </div>
    </li>
    <li class="listitem">
     <p>
      The
      <code class="literal">
       Replica_IO_State
      </code>
      and
      <code class="literal">
       Replica_SQL_Running_State
      </code>
      fields are not
            preserved. If needed, these values can be obtained from the
            process list by using the
      <code class="literal">
       THREAD_ID
      </code>
      column of the appropriate replication table and joining it
            with the
      <code class="literal">
       ID
      </code>
      column in the
      <code class="literal">
       INFORMATION_SCHEMA
      </code>
      <a class="link" href="information-schema-processlist-table.html" title="28.3.23 The INFORMATION_SCHEMA PROCESSLIST Table">
       <code class="literal">
        PROCESSLIST
       </code>
      </a>
      table to select the
      <code class="literal">
       STATE
      </code>
      column of the latter table.
     </p>
    </li>
    <li class="listitem">
     <p>
      The
      <code class="literal">
       Executed_Gtid_Set
      </code>
      field can show a
            large set with a great deal of text. Instead, the
            Performance Schema tables show GTIDs of transactions that
            are currently being applied by the replica. Alternatively,
            the set of executed GTIDs can be obtained from the value of
            the
      <a class="link" href="replication-options-gtids.html#sysvar_gtid_executed">
       <code class="literal">
        gtid_executed
       </code>
      </a>
      system
            variable.
     </p>
    </li>
    <li class="listitem">
     <p>
      The
      <code class="literal">
       Seconds_Behind_Master
      </code>
      and
      <code class="literal">
       Relay_Log_Space
      </code>
      fields are in
            to-be-decided status and are not preserved.
     </p>
    </li>
   </ul>
  </div>
  <h4>
   <a name="idm46045071635792">
   </a>
   Replication Channels
  </h4>
  <p>
   The first column of the replication Performance Schema tables is
   <code class="literal">
    CHANNEL_NAME
   </code>
   . This enables the tables to be
        viewed per replication channel. In a non-multisource replication
        setup there is a single default replication channel. When you
        are using multiple replication channels on a replica, you can
        filter the tables per replication channel to monitor a specific
        replication channel. See
   <a class="xref" href="replication-channels.html" title="19.2.2 Replication Channels">
    Section 19.2.2, “Replication Channels”
   </a>
   and
   <a class="xref" href="replication-multi-source-monitoring.html" title="19.1.5.8 Monitoring Multi-Source Replication">
    Section 19.1.5.8, “Monitoring Multi-Source Replication”
   </a>
   for
        more information.
  </p>
 </div>
 <br/>
</div>
