Search Results
https://dev.mysql.com/doc/refman/8.4/en/persisted-system-variables.html
The MySQL server maintains system variables that configure its operation. A system variable can have a global value that affects server operation as a whole, a session value that affects the current session, or both. Many system variables are ...
https://dev.mysql.com/doc/refman/8.4/en/postinstallation.html
This section discusses tasks that you should perform after installing MySQL: If necessary, initialize the data directory and create the MySQL grant tables. For some MySQL installation methods, data directory initialization may be done for you ...
https://dev.mysql.com/doc/refman/8.4/en/replication-asynchronous-connection-failover-source.html
To activate asynchronous connection failover for a replication channel set SOURCE_CONNECTION_AUTO_FAILOVER=1 in a CHANGE REPLICATION SOURCE TO statement for this channel. GTID auto-positioning must be in use for the channel (SOURCE_AUTO_POSITION = ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-timeout.html
The global value of the system variable replica_transaction_retries sets the maximum number of times for applier threads on a single-threaded or multithreaded replica to automatically retry failed transactions before stopping. Transactions are ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-concepts.html
A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server of origin (the source). This identifier is unique not only to the server on which it originated, but is unique across ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-lifecycle.html
The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the source. This client transaction is assigned a GTID composed of the source's UUID and the smallest nonzero transaction sequence number not yet ...
https://dev.mysql.com/doc/refman/8.4/en/replication-mode-change-online-verify-transactions.html
This section explains how to monitor a replication topology and verify that all anonymous transactions have been replicated. This is helpful when changing the replication mode online as you can verify that it is safe to change to GTID transactions.
https://dev.mysql.com/doc/refman/8.4/en/replication-sbr-rbr.html
For most users, the mixed replication format should provide the best combination of data integrity and performance. If, however, you want to take advantage of the features specific to the statement-based or row-based replication format when ...
https://dev.mysql.com/doc/refman/8.4/en/show-triggers.html
SHOW TRIGGERS [{FROM | IN} db_name] [LIKE 'pattern' | WHERE expr] SHOW TRIGGERS lists the triggers currently defined for tables in a database (the default database unless a FROM clause is given). This statement returns results only for databases ...