Documentation Home
MySQL 8.4 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 40.2Mb
PDF (A4) - 40.3Mb
Man Pages (TGZ) - 262.0Kb
Man Pages (Zip) - 367.6Kb
Info (Gzip) - 4.0Mb
Info (Zip) - 4.0Mb


29.12.22.5 The log_status Table

Thelog_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 thelog_status table is queried, the server blocks logging and related administrative changes for just long enough to populate the table, then releases the resources. Thelog_status table informs the online backup which point it should copy up to in the source's binary log andgtid_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 theInnoDB storage engine.

Thelog_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 variableserver_uuid.

  • LOCAL

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

    binary_log_file

    The name of the current binary log file.

    binary_log_position

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

    gtid_executed

    The current value of the global server variablegtid_executed at the time thelog_status table was accessed. This information is consistent with thebinary_log_file andbinary_log_position keys.

  • REPLICATION

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

    channel_name

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

    relay_log_file

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

    relay_log_pos

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

  • STORAGE_ENGINES

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

Thelog_status table has no indexes.

TheBACKUP_ADMIN privilege, as well as theSELECT privilege, is required for access to thelog_status table.

TRUNCATE TABLE is not permitted for thelog_status table.