PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/group-by-handling.html
SQL:1999 and later permits such nonaggregates per optional feature T301 if they are functionally dependent on GROUP BY columns: If such a relationship exists between name and custid, the query is legal. SQL-92 and earlier does not permit queries ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-configuring-instances.html
In other words, any existing data which is on the server bootstrapping the group is what is used as the data for the next joining member. If you bootstrap the group multiple times, for example when multiple server instances have this option set, ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-distributed-recovery-basics.html
Whenever a member joins a replication group, it connects to an existing member to carry out state transfer. The server joining the group transfers all the transactions that took place in the group before it joined, which are provided by the ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/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/5.7/en/group-replication-tuning-recovery.html
The following section explains how recovery works and how to tune the settings Donor Selection A random donor is selected from the existing online members in the group. Donor Connection Retries The recovery data transfer relies on the binary log and ... Whenever a new member joins a replication group, it connects to a suitable donor and fetches the data that it has missed up until the point it is declared ...
https://dev.mysql.com/doc/refman/5.7/en/gtid-functions.html
If no channel is named and no channels other than the default replication channel exist, the function applies to the default replication channel. If multiple replication channels exist, you must specify a channel as otherwise it is not known which ... The functions described in this section are used with GTID-based ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/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/5.7/en/innodb-file-format-compatibility-checking-table-access.html
The file format management capability in InnoDB 1.0 and higher (tablespace tagging and run-time checks) allows InnoDB to verify as soon as possible that the running version of software can properly process the tables existing in the database. When ...