Movatterモバイル変換

RESET BINARY LOGS AND GTIDS [TObinary_log_file_index_number]

RESET BINARY LOGS AND GTIDS requires theRELOAD privilege.

For a server where binary logging is enabled (log_bin isON),RESET BINARY LOGS AND GTIDS deletes all existing binary log files and resets the binary log index file, resetting the server to its state before binary logging was started. A new empty binary log file is created so that binary logging can be restarted.

For a server where GTIDs are in use (gtid_mode isON), issuingRESET BINARY LOGS AND GTIDS resets the GTID execution history. The value of thegtid_purged system variable is set to an empty string (''), the global value (but not the session value) of thegtid_executed system variable is set to an empty string, and themysql.gtid_executed table is cleared (seemysql.gtid_executed Table). If the GTID-enabled server has binary logging enabled,RESET BINARY LOGS AND GTIDS also resets the binary log as described above. Note thatRESET BINARY LOGS AND GTIDS is the method to reset the GTID execution history even if the GTID-enabled server is a replica where binary logging is disabled;RESET REPLICA has no effect on the GTID execution history. For more information on resetting the GTID execution history, seeResetting the GTID Execution History.

IssuingRESET BINARY LOGS AND GTIDS without the optionalTO clause deletes all binary log files listed in the index file, resets the binary log index file to be empty, and creates a new binary log file starting at1. Use the optionalTO clause to start the binary log file index from a number other than1 after the reset.

Check that you are using a reasonable value for the index number. If you enter an incorrect value, you can correct this by issuing anotherRESET BINARY LOGS AND GTIDS statement with or without theTO clause. If you do not correct a value that is out of range, the server cannot be restarted.

The following example demonstratesTO clause usage:

RESET BINARY LOGS AND GTIDS TO 1234;SHOW BINARY LOGS;+-------------------+-----------+-----------+| Log_name          | File_size | Encrypted |+-------------------+-----------+-----------+| source-bin.001234 |       154 | No        |+-------------------+-----------+-----------+

RESET BINARY LOGS AND GTIDS without theTO clause can prove useful when you first set up a source and replica, so that you can verify the setup as follows:

After verifying the setup, resetting the source and replica and ensuring that no unwanted data or binary log files generated by testing remain on the source or replica, you can start the replica and begin replicating.