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/problems-with-alias.html
This restriction is imposed because when the WHERE clause is evaluated, the column value may not yet have been determined. An alias can be used in a query select list to give a column a different name. In the select list of a query, a quoted column ...
https://dev.mysql.com/doc/refman/8.0/en/processlist-access.html
The other sources have negative performance consequences because they require a mutex. Privileges Required to Access the Process List For most sources of process information, if you have the PROCESS privilege, you can see all threads, even those ...
https://dev.mysql.com/doc/refman/8.0/en/replication-administration-status.html
The most common task when managing a replication process is to ensure that replication is taking place and that there have been no errors between the replica and the source. Normally, you want this to be Yes unless you have not yet started ...The ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-concepts.html
Client transactions are guaranteed to have monotonically increasing GTIDs without gaps between the generated numbers. It is not possible for a transaction to have 0 as a sequence number in a GTID. It enables a replica to use GTIDs when binary ... A ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-functions.html
WAIT_FOR_EXECUTED_GTID_SET(): Waits until all transactions in a given GTID set have been executed. gtid_purged contains the GTIDs of all the transactions that have been committed on a given server but which do not exist in any binary log file on the ... This section provides examples of stored functions (see Chapter 27, Stored Objects) which you can create using some of the built-in functions provided by MySQL for use with GTID-based replication, listed here: GTID_SUBSET(): Shows whether one GTID set is a subset of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-slavebaseconfig.html
Each replica must have a unique server ID, as specified by the server_id system variable. If you are setting up multiple replicas, each one must have a unique server_id value that differs from that of the source and from any of the other replicas.
https://dev.mysql.com/doc/refman/8.0/en/replication-rbr-safe-unsafe.html
Whenever the 50 most recent ER_BINLOG_UNSAFE_STATEMENT warnings have been generated more than 50 times in any 50-second period, warning suppression is enabled. Since we have no control over what a loadable function does, we must assume that it is ...
https://dev.mysql.com/doc/refman/8.0/en/replication-snapshot-method.html
Employing this method with a table using a storage engine that has complex caching or logging algorithms requires extra steps to produce a perfect “point in time” snapshot: the initial copy command could leave out cache information and logging ... If the source database contains existing data it is necessary to copy this data to each ...
https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-backups-rawdata.html
If you want to be able to restore the data and operate as a replica (for example, in the event of failure of the replica), in addition to the data, you need to have the replica's connection metadata repository and applier metadata repository, and ...
https://dev.mysql.com/doc/refman/8.0/en/revoke.html
To use the first REVOKE syntax, you must have the GRANT OPTION privilege, and you must have the privileges that you are revoking. To use these REVOKE statements, you must have the global CREATE USER privilege, or the UPDATE privilege for the mysql ...[IGNORE UNKNOWN USER] REVOKE [IF EXISTS] ALL [PRIVILEGES], GRANT OPTION FROM user_or_role [, user_or_role] ...