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
Search Results
https://dev.mysql.com/doc/refman/8.0/en/group-replication-functions-for-member-actions.html
The member actions configuration, consisting of all the member actions and whether they are enabled or disabled, is then propagated to other group members and joining members using Group Replication’s group messages. The changed setting is ... The ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-requirements.html
For certain Group Replication tasks that require communication between remote XCom instances, such as joining a group, the TCP network is still used, so network performance influences the group's performance. Group members need to log transactions ... Infrastructure Server Instance Configuration Server instances that you want to use for Group Replication must satisfy the following ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-restarting-group.html
A member cannot join a group if it has transactions that are not present on the other group members. The members with fewer transactions can then join and catch up with the transactions they are missing through distributed recovery. Group ...
https://dev.mysql.com/doc/refman/8.0/en/group-replication-server-states.html
RECOVERING The server has joined a group and is in the process of becoming an active member. This status may briefly occur while a member is joining or rejoining a group. While a member is joining or rejoining a replication group, its status can be ... The state of a Group Replication group member shows its current role in the ...
https://dev.mysql.com/doc/refman/8.0/en/identifier-qualifiers.html
An unqualified name is permitted in contexts where interpretation of the name is unambiguous. A qualified name includes at least one qualifier to clarify the interpretive context by overriding a default context or providing missing context. For ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-best-practices.html
Use joins wherever data is pulled from multiple tables based on identical ID values from those tables. For fast join performance, define foreign keys on the join columns, and declare those columns with the same data type in each table. Specify a ...
https://dev.mysql.com/doc/refman/8.0/en/known-issues.html
For example, the following does not work: mysql> SELECT * FROM temp_table, temp_table AS t2; ERROR 1137: Can't reopen table: 'temp_table' The optimizer may handle DISTINCT differently when you are using “hidden” columns in a join than when you ... This section lists known issues in recent versions of ...
https://dev.mysql.com/doc/refman/8.0/en/myisam-optimization.html
This improves join performance by enabling the join optimizer to better choose the order in which to join the tables and which indexes it should use. To coalesce fragmented rows and eliminate wasted space that results from deleting or updating ...
https://dev.mysql.com/doc/refman/8.0/en/myisamchk-other-options.html
This improves join performance by enabling the join optimizer to better choose the order in which to join the tables and which indexes it should use. myisamchk supports the following options for actions other than table checks and repairs: ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-mgm-client-commands.html
CREATE NODEGROUP nodeid[, nodeid, ...] Creates a new NDB Cluster node group and causes data nodes to join it. This command is used after adding new data nodes online to an NDB Cluster, and causes them to join a new node group and thus to begin ...