•the time a thread started processing a transaction 

•for the last processed transaction, the time the thread finished processing it 

In addition to the Performance Schema tables, the output of SHOW REPLICA | SLAVE STATUS  has three fields that show: 

• SQL_Delay : A nonnegative integer indicating the replication delay configured using CHANGE REPLICATION SOURCE TO SOURCE_DELAY= N  (from MySQL 8.0.23) or CHANGE MASTER TO MASTER_DELAY=N  (before MySQL 8.0.23), measured in seconds. 

• SQL_Remaining_Delay : When Replica_SQL_Running_State  is Waiting until MASTER_DELAY seconds after master executed event , this field contains an integer indicating the number of seconds left of the delay. At other times, this field is NULL . 

• Replica_SQL_Running_State : A string indicating the state of the SQL thread (analogous to Replica_IO_State ). The value is identical to the State  value of the SQL thread as displayed by SHOW PROCESSLIST . 

When the replication SQL thread is waiting for the delay to elapse before executing an event, SHOW PROCESSLIST  displays its State  value as Waiting until MASTER_DELAY seconds after master executed event . 

## 17.5 Replication Notes and Tips 

## 17.5.1 Replication Features and Issues 

The following sections provide information about what is supported and what is not in MySQL replication, and about specific issues and situations that may occur when replicating certain statements. 

Statement-based replication depends on compatibility at the SQL level between the source and replica. In other words, successful statement-based replication requires that any SQL features used be supported by both the source and the replica servers. If you use a feature on the source server that is available only in the current version of MySQL, you cannot replicate to a replica that uses an earlier version of MySQL. Such incompatibilities can also occur within a release series as well as between versions. 

If you are planning to use statement-based replication between MySQL 8.0 and a previous MySQL release series, it is a good idea to consult the edition of the MySQL Reference Manual  corresponding to the earlier release series for information regarding the replication characteristics of that series. 

With MySQL’s statement-based replication, there may be issues with replicating stored routines or triggers. You can avoid these issues by using MySQL’s row-based replication instead. For a detailed list of issues, see Section 25.7, “Stored Program Binary Logging” . For more information about row-based logging and row-based replication, see Section 5.4.4.1, “Binary Logging Formats” , and Section 17.2.1, “Replication Formats” . 

For additional information specific to replication and InnoDB , see Section 15.19, “InnoDB and MySQL Replication” . For information relating to replication with NDB Cluster, see Section 23.6, “NDB Cluster Replication” . 

## 17.5.1.1 Replication and AUTO_INCREMENT 

Statement-based replication of AUTO_INCREMENT , LAST_INSERT_ID() , and TIMESTAMP  values is carried out subject to the following exceptions: 

