Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 44.5Mb
PDF (A4) - 44.5Mb
PDF (RPM) - 40.2Mb
HTML Download (TGZ) - 10.5Mb
HTML Download (Zip) - 10.5Mb
HTML Download (RPM) - 9.1Mb
Man Pages (TGZ) - 204.6Kb
Man Pages (Zip) - 311.6Kb
Info (Gzip) - 3.9Mb
Info (Zip) - 3.9Mb
Excerpts from this Manual The log_status Table

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 master'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:


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


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


    The name of the current binary log file.


    The current binary log position at the time the log_status table was accessed.


    The current value of the global server variable gtid_executed at the time the log_status table was accessed. This information is consistent with the binary_log_file and binary_log_position keys.


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


    The name of the replication channel. The default replication channel's name is the empty string ().


    The name of the current relay log file for the replication channel.


    The current relay log position at the time the log_status table was accessed.


    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 is required for access to the log_status table.

TRUNCATE TABLE is not permitted for the log_status table.

User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.