content_image/848492.jpg content_image/848493.jpg
The log_status  table provides information that enables an online backup tool to copy the required log files without locking those resources for the duration of the copy process. 

When the log_status  table is queried, the server blocks logging and related administrative changes for just long enough to populate the table, then releases the resources. The log_status  table informs the online backup which point it should copy up to in the source’s binary log and gtid_executed  record, and the relay log for each replication channel. It also provides relevant information for individual storage engines, such as the last log sequence number (LSN) and the LSN of the last checkpoint taken for the InnoDB  storage engine. 

The log_status  table has these columns: 

• SERVER_UUID 

The server UUID for this server instance. This is the generated unique value of the read-only system variable server_uuid . 

• LOCAL 

The log position state information from the source, provided as a single JSON object with the following keys: 

<img src='content_image/848492.jpg'>

• REPLICATION 

A JSON array of channels, each with the following information: 

<img src='content_image/848493.jpg'>

• STORAGE_ENGINES 

Relevant information from individual storage engines, provided as a JSON object with one key for each applicable storage engine. 

The log_status  table has no indexes. 

The BACKUP_ADMIN  privilege, as well as the SELECT  privilege, is required for access to the log_status table. 

## 27.12.21.4 The performance_timers Table 

TRUNCATE TABLE  is not permitted for the log_status  table. 

