Search Results
                    
                    
            https://dev.mysql.com/doc/refman/8.4/en/group-replication-functions-for-communication-protocol.html
                                The GROUP_REPLICATION_ADMIN privilege is required to use this function, and all existing group members must be online when you issue the statement, with no loss of majority. For an upgrade, specify the new MySQL Server version to which the existing ... The following functions enable you to inspect and configure the Group Replication communication protocol version that is used by a replication ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/group-replication-functions-for-new-primary.html
                                If a standard source to replica replication channel is running on the existing primary member in addition to the Group Replication channels, you must stop that replication channel before you can change the primary member. timeout: An integer ... The ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/group-replication-group-membership.html
                                If a server joins the group, it automatically brings itself up to date by fetching the missing state from an existing server. If existing members agree that a new server should become part of the group, the group is reconfigured to integrate that ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/group-replication-ipv6.html
                                To make a joining member present an IPv4 address for group communications, you can either change the value of group_replication_local_address to an IPv4 address, or configure your DNS to resolve the joining member's existing host name to an IPv4 ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/group-replication-online-upgrade-methods.html
                                This is because if a member joins a group when it is running a higher MySQL Server version than the lowest version that the existing group members are running, it automatically remains in read-only mode (super_read_only=ON).  Choose one of the ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/group-replication-restarting-group.html
                                However, if every member of a replication group leaves the group, and Group Replication is stopped on every member by a STOP GROUP_REPLICATION statement or system shutdown, the group now only exists in theory, as a configuration on the members. 
                                            
                https://dev.mysql.com/doc/refman/8.4/en/innochecksum.html
                                In this example, an existing innodb checksum is rewritten to set --allow-mismatches to 1. If the new checksum is identical to the existing checksum, the new checksum is not written to disk in order to minimize I/O. This tool reads an InnoDB ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/innodb-consistent-read.html
                                If other sessions simultaneously update the same table, the anomaly means that you might see the table in a state that never existed in the database. When you reissue a consistent read within a transaction, rows in the new table are not visible ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-examples-compression-sect.html
                                The smallest PAGE_SIZE in INNODB_CMPMEM is used for block descriptors of those compressed pages for which no uncompressed page exists in the buffer pool. Indirectly, we see that 259 (6169-5910) compressed pages also exist in the buffer pool in ...
                                            
                https://dev.mysql.com/doc/refman/8.4/en/innodb-locking-reads.html
                                Consistent reads ignore any locks set on the records that exist in the read view. First, use a consistent read to query the table PARENT and verify that the parent row exists.  If you query data and then insert or update related data within the same ...