Search Results
https://dev.mysql.com/doc/refman/8.4/en/plugin-loading.html
To uninstall a plugin that currently is loaded at server startup with a plugin-loading option, use this procedure. Server plugins must be loaded into the server before they can be used. It is also possible to control the activation state of loaded ...
https://dev.mysql.com/doc/refman/8.4/en/prepare.html
A statement prepared in stored program context cannot refer to stored procedure or function parameters or local variables because they go out of scope when the program ends and would be unavailable were the statement to be executed later outside the ... PREPARE stmt_name FROM preparable_stmt The PREPARE statement prepares a SQL statement and assigns it a name, stmt_name, by which to refer to the statement ...
https://dev.mysql.com/doc/refman/8.4/en/purge-binary-logs.html
To safely purge binary log files, follow this procedure: On each replica, use SHOW REPLICA STATUS to check which log file it is reading. PURGE BINARY LOGS { TO 'log_name' | BEFORE datetime_expr } The binary log is a set of files that contain ...
https://dev.mysql.com/doc/refman/8.4/en/repeat.html
[begin_label:] REPEAT statement_list UNTIL search_condition END REPEAT [end_label] The statement list within a REPEAT statement is repeated until the search_condition expression is true. statement_list consists of one or more statements, each ...
https://dev.mysql.com/doc/refman/8.4/en/replication-asynchronous-connection-failover.html
InnoDB ClusterSet and InnoDB Cluster are designed to abstract and simplify the procedures for setting up, managing, monitoring, recovering, and repairing replication groups. You can use the asynchronous connection failover mechanism to establish an ...
https://dev.mysql.com/doc/refman/8.4/en/replication-binlog-encryption-encryption-keys.html
The binary log encryption keys used to encrypt the file passwords for the log files are 256-bit keys that are generated specifically for each MySQL server instance using MySQL Server's keyring service (see Section 8.4.4, “The MySQL Keyring”).
https://dev.mysql.com/doc/refman/8.4/en/replication-bugs.html
If you have a “phantom” problem (one that you cannot duplicate at will), use the following procedure: Verify that no user error is involved. When you have determined that there is no user error involved, and replication still either does not ...
https://dev.mysql.com/doc/refman/8.4/en/replication-encrypted-connections.html
The connection procedure negotiates the use of the highest TLS version that both the source and the replica permit. To use an encrypted connection for the transfer of the binary log required during replication, both the source and the replica ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-functions.html
The procedure used is to back up server2 using mysqldump, then to restore this backup on server1. This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create using some of the built-in functions provided ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-howto.html
This is a “cold start” procedure that assumes either that you are starting the source server for the first time, or that it is possible to stop it; for information about provisioning replicas using GTIDs from a running source server, see Section ... This section describes a process for configuring and starting GTID-based replication in MySQL ...