Search

Download this Manual
PDF (US Ltr) - 43.3Mb
PDF (A4) - 43.4Mb
Man Pages (TGZ) - 297.2Kb
Man Pages (Zip) - 402.4Kb
Info (Gzip) - 4.3Mb
Info (Zip) - 4.3Mb


Displaying 271 to 280 of 1321 total results
https://dev.mysql.com/doc/refman/8.0/en/group-by-functional-dependence.html
The following discussion provides several examples of the ways in which MySQL detects functional dependencies. The examples use this notation: {X} -> {Y} Understand this as “X uniquely determines Y,” which also means that Y is functionally ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-adding-instances.html
This member needs to have the same replication user configured in Section 20.2.1.3, “User Credentials For Distributed Recovery”. If you did not have binary logging enabled when you configured the user credentials on s1, and a remote cloning ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-flow-control.html
MySQL Group Replication ensures that a transaction commits only after a majority of the members in a group have received it and agreed on the relative order amongst all transactions sent concurrently. If it does, and some members have less write ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-member-actions.html
Member actions have a priority from 1 to 100, with lower values being actioned first. The server must be writeable (with the read_only system variable set to OFF) and have the Group Replication plugin installed. In this state, it does not accept ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-multi-primary-mode.html
This means that as soon as the incoming traffic slows down or stops, all group members have the same data content. While traffic is flowing, transactions can be externalized on some members before the others, especially if some members have less ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-requirements.html
Every table that is to be replicated by the group must have a defined primary key, or primary key equivalent where the equivalent is a non-null unique key. GTID-based replication is required for Group Replication, which uses global transaction ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-responses-failure-exit.html
When the member is in super read only mode, clients cannot make any updates, even if they have the CONNECTION_ADMIN privilege (or the deprecated SUPER privilege). When the member is in offline mode, connected client users are disconnected on their ... The group_replication_exit_state_action system variable, which is available from MySQL 8.0.12 and MySQL 5.7.24, specifies what Group Replication does when the member leaves the group unintentionally due to an error or problem, and either fails to auto-rejoin or does not ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-user-credentials.html
If group members have been set up to support the use of a remote cloning operation as part of distributed recovery, which is available in MySQL 8.0.17 and later, this replication user is also used as the clone user on the donor, and requires the ...
https://dev.mysql.com/doc/refman/8.0/en/gtid-functions.html
WAIT_FOR_EXECUTED_GTID_SET() Wait until the given GTIDs have executed on the replica. If a timeout is specified, and timeout seconds elapse before all of the transactions in the GTID set have been applied, the function stops waiting. timeout is ...
https://dev.mysql.com/doc/refman/8.0/en/index-statistics.html
For InnoDB and MyISAM tables, you have some control over collection of table statistics by means of the innodb_stats_method and myisam_stats_method system variables, respectively. These variables have three possible values, which differ as follows: ... Storage engines collect statistics about tables for use by the ...
Displaying 271 to 280 of 1321 total results