Replication and Binary Logging Options and Variables • gtid_next : Specifies GTID for next statement to execute; see documentation for details. • gtid_owned : Set of GTIDs owned by this client (session), or by all clients, together with thread ID of owner (global). Read-only. • gtid_purged : Set of all GTIDs that have been purged from binary log. • init_slave : Statements that are executed when replica connects to source. • log_bin_trust_function_creators : If equal to 0 (default), then when --log-bin is used, stored function creation is allowed only to users having SUPER privilege and only if function created does not break binary logging. • log_statements_unsafe_for_binlog : Disables error 1592 warnings being written to error log. • master-info-file : Location and name of file that remembers source and where I/O replication thread is in source’s binary log. • master-retry-count : Number of tries replica makes to connect to source before giving up. • master_info_repository : Whether to write connection metadata repository, containing source information and replication I/O thread location in source’s binary log, to file or table. • max_relay_log_size : If nonzero, relay log is rotated automatically when its size exceeds this value. If zero, size at which rotation occurs is determined by value of max_binlog_size. • original_commit_timestamp : Time when transaction was committed on original source. • immediate_server_version : MySQL Server release number of server which is immediate replication source. • original_server_version : MySQL Server release number of server on which transaction was originally committed. • relay_log : Location and base name to use for relay logs. • relay_log_basename : Complete path to relay log, including file name. • relay_log_index : Location and name to use for file that keeps list of last relay logs. • relay_log_info_file : File name for applier metadata repository in which replica records information about relay logs. • relay_log_info_repository : Whether to write location of replication SQL thread in relay logs to file or table. • relay_log_purge : Determines whether relay logs are purged. • relay_log_recovery : Whether automatic recovery of relay log files from source at startup is enabled; must be enabled for crash-safe replica. • relay_log_space_limit : Maximum space to use for all relay logs. • replicate-do-db : Tells replication SQL thread to restrict replication to specified database. • replicate-do-table : Tells replication SQL thread to restrict replication to specified table. • replicate-ignore-db : Tells replication SQL thread not to replicate to specified database. • replicate-ignore-table : Tells replication SQL thread not to replicate to specified table. 3491