Search Results
https://dev.mysql.com/doc/refman/8.4/en/recovery-from-backups.html
The full backup file is just a set of SQL statements, so restoring it is very easy: $> mysql < backup_sunday_1_PM.sql At this point, the data is restored to its state as of Sunday 1 p.m.. | mysql For more information about using mysqlbinlog to ...
https://dev.mysql.com/doc/refman/8.4/en/replication-administration-pausing.html
Stopping only the receiver thread enables the events in the relay log to be executed by the applier thread up to the point where the relay log ends. This can be useful when you want to pause execution to catch up with events already received from ...
https://dev.mysql.com/doc/refman/8.4/en/replication-administration-skip.html
For instructions to do this, see Section 9.5, “Point-in-Time (Incremental) Recovery”. Before skipping the transaction and restarting the replica, check these points: Is the transaction that stopped replication from an unknown or untrusted ... If ...
https://dev.mysql.com/doc/refman/8.4/en/replication-mode-change-online-disable-gtids.html
The only thing that differs is the point at which you wait for logged transactions to replicate. If you use binary logs for anything other than replication—for example, to perform point-in-time backup or restore—wait until you no longer need any ... This section describes how to disable GTID transactions on servers that are already ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-binary-log.html
Transactions are written to the binary log at the point when all the storage engines involved have confirmed that the transaction is prepared to commit. If you are using GTIDs for replication, this means that even when binary logging is later ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-gtids.html
If gtid_next=AUTOMATIC is used for the session, gtid_owned is populated only briefly during the execution of the commit statement for the transaction, so it cannot be observed from the session concerned, although it is listed if @@global.gtid_owned ... The MySQL Server system variables described in this section are used to monitor and control Global Transaction Identifiers ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-reference.html
replica_checkpoint_group: Maximum number of transactions processed by multithreaded replica before checkpoint operation is called to update progress status. replica_checkpoint_period: Update progress status of multithreaded replica and flush relay ... The following two sections provide basic information about the MySQL command-line options and system variables applicable to replication and the binary ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-replica.html
This variable works in combination with the replica_checkpoint_period system variable in such a way that, when either limit is exceeded, the checkpoint is executed and the counters tracking both the number of transactions and the time elapsed since ... This section explains the server options and system variables that apply to replica servers and contains the following: Startup Options for Replica Servers System Variables Used on Replica Servers Specify the options either on the command line or in an option ...
MySQL 8.4 Reference Manual :: 19.2.1.3 Determination of Safe and Unsafe Statements in Binary Logging
https://dev.mysql.com/doc/refman/8.4/en/replication-rbr-safe-unsafe.html
In addition, statements using results from floating-point math functions—which are hardware-dependent—are always considered unsafe (see Section 19.5.1.12, “Replication and Floating-Point Values”). The “safeness” of a statement in MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules-table-options.html
Having reached this point, if there are no table options, the replica simply executes all events. The starting point is the end of the evaluation of the database-level options, as described in Section 19.2.5.1, “Evaluation of Database-Level ...