Search Results
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-log-status-table.html
The log_status table has these columns: SERVER_UUID The server UUID for this server instance. This is the generated unique value of the read-only system variable server_uuid. The log_status table provides information that enables an online backup ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-replication-group-member-stats-table.html
The replication_group_member_stats table has these columns: CHANNEL_NAME Name of the Group Replication channel VIEW_ID Current view identifier for this group. This has a different value for each member in the group. This also serves as a key because ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-replication-group-members-table.html
This table shows network and status information for replication group members. The network addresses shown are the addresses used to connect clients to the group, and should not be confused with the member's internal group communication address ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-replication-tables.html
The following fields are based on server_id, not server_uuid, and are not preserved: Master_Server_Id Replicate_Ignore_Server_Ids The Skip_Counter field is based on event counts, not GTIDs, and is not preserved. This is similar to the information ...
https://dev.mysql.com/doc/refman/8.4/en/privileges-provided.html
TRANSACTION_GTID_TAG Required for setting the gtid_next system variable to AUTOMATIC:TAG or UUID:TAG:NUMBER on a replication source server. The privileges granted to a MySQL account determine which operations the account can perform. MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-auto-positioning.html
If during the exchange of transactions it is found that the replica has received or committed transactions with the source's UUID in the GTID, but the source itself does not have a record of them, the source sends the error ... GTIDs replace the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options-binary-log.html
For example, this happens when statements contain loadable functions or the UUID() function. Startup Options Used with Binary Logging System Variables Used with Binary Logging You can use the mysqld options and system variables that are described ...
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
These functions include FOUND_ROWS(), GET_LOCK(), IS_FREE_LOCK(), IS_USED_LOCK(), LOAD_FILE(), RAND(), RELEASE_LOCK(), ROW_COUNT(), SESSION_USER(), SLEEP(), SOURCE_POS_WAIT(), SYSDATE(), SYSTEM_USER(), USER(), UUID(), and UUID_SHORT(). The ...
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/server-status-variables.html
The MySQL server maintains many status variables that provide information about its operation. You can view these variables and their values by using the SHOW [GLOBAL | SESSION] STATUS statement (see Section 15.7.7.37, “SHOW STATUS Statement”).