Replication and Binary Logging Options and Variables SHOW REPLICA | SLAVE STATUS . The value of this variable is a GTID set, see GTID Sets for more information. When the server starts,  @@GLOBAL.gtid_executed  is initialized. See binlog_gtid_simple_recovery  for more information on how binary logs are iterated to populate gtid_executed . GTIDs are then added to the set as transactions are executed, or if any  SET gtid_purged  statement is executed. The set of transactions that can be found in the binary logs at any given time is equal to GTID_SUBTRACT(@@GLOBAL.gtid_executed, @@GLOBAL.gtid_purged) ; that is, to all transactions in the binary log that have not yet been purged. Issuing  RESET MASTER causes the global value (but not the session value) of this variable to be reset to an empty string. GTIDs are not otherwise removed from this set other than when the set is cleared due to  RESET MASTER . In some older releases, this variable could also be used with session scope, where it contained a representation of the set of transactions that are written to the cache in the current session. The session scope is now deprecated. Compress the  mysql.gtid_executed  table each time this many transactions have been processed. When binary logging is enabled on the server, this compression method is not used, and instead the mysql.gtid_executed  table is compressed on each binary log rotation. When binary logging is disabled on the server, the compression thread sleeps until the specified number of transactions have been executed, then wakes up to perform compression of the  mysql.gtid_executed  table. Setting the value of this system variable to 0 means that the thread never wakes up, so this explicit compression method is not used. Instead, compression occurs implicitly as required. From MySQL 8.0.17,  InnoDB  transactions are written to the  mysql.gtid_executed  table by a separate process to non- InnoDB  transactions. If the server has a mix of  InnoDB  transactions and non- InnoDB  transactions, the compression controlled by this system variable interferes with the work of this process and can slow it significantly. For this reason, from that release it is recommended that you set  gtid_executed_compression_period  to 0. From MySQL 8.0.23,  InnoDB  and non- InnoDB  transactions are written to the  mysql.gtid_executed table by the same process, and the  gtid_executed_compression_period  default value is 0. See mysql.gtid_executed Table Compression for more information. 3573 • gtid_executed_compression_period Command-Line Format --gtid-executed-compression-period=# System Variable gtid_executed_compression_period Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value ( ≥  8.0.23) 0 Default Value ( ≤  8.0.22) 1000 Minimum Value 0 Maximum Value 4294967295