Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-howto.html
It is not mandatory to have binary logging enabled in order to use GTIDs when using the mysql.gtid_executed Table. Source servers must always have binary logging enabled in order to be able to replicate. This section describes a process for ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks-account.html
In order to execute specific replicated transactions from the relay log, or transactions from mysqlbinlog output as required, the PRIVILEGE_CHECKS_USER account must have the following privileges: For a row insertion logged in row format (which are ... The user account that is specified using the CHANGE REPLICATION SOURCE TO statement as the PRIVILEGE_CHECKS_USER account for a replication channel must have the REPLICATION_APPLIER privilege, otherwise the replication applier thread does not ...
https://dev.mysql.com/doc/refman/8.4/en/scheduler-component.html
The scheduler component implements the service using these elements: A priority queue of the registered, inactive scheduled tasks sorted by the next time to run (in ascending order). The component service calls each application-provided callback ...
https://dev.mysql.com/doc/refman/8.4/en/source-configuration-options.html
-DLINK_RANDOMIZE=bool Whether to randomize the order of symbols in the mysqld binary. If tooling is enabled, the LOCK_ORDER tool is available and can be used as described in Section 7.9.3, “The LOCK_ORDER Tool”. Note With the WITH_LOCK_ORDER ...
https://dev.mysql.com/doc/refman/8.4/en/sql-mode.html
ONLY_FULL_GROUP_BY Reject queries for which the select list, HAVING condition, or ORDER BY list refer to nonaggregated columns that are neither named in the GROUP BY clause nor are functionally dependent on (uniquely determined by) GROUP BY columns.
https://dev.mysql.com/doc/refman/8.4/en/stored-program-restrictions.html
A stored function acquires table locks before executing, to avoid inconsistency in the binary log due to mismatch of the order in which statements execute and when they appear in the log. There is no way to cause events scheduled to occur at the ...
https://dev.mysql.com/doc/refman/8.4/en/subquery-materialization.html
MySQL can also apply subquery materialization to a single-table UPDATE or DELETE statement that uses a [NOT] IN or [NOT] EXISTS subquery predicate, provided that the statement does not use ORDER BY or LIMIT, and that subquery materialization is ...
https://dev.mysql.com/doc/refman/8.4/en/telemetry-metrics-meter-metrics.html
read_next Handler_read_next ASYNC COUNTER The number of requests to read the next row in key order. read_prev Handler_read_prev ASYNC COUNTER The number of requests to read the previous row in key order. The following server metrics are registered ...
https://dev.mysql.com/doc/refman/8.4/en/temporary-files.html
On Windows, MySQL checks in order the values of the TMPDIR, TEMP, and TMP environment variables. (In such cases, lsof +L1 may be helpful in identifying large files associated with mysqld.) When sorting (ORDER BY or GROUP BY), MySQL normally uses one ... On Unix, MySQL uses the value of the TMPDIR environment variable as the path name of the directory in which to store temporary ...
https://dev.mysql.com/doc/refman/8.4/en/trigger-syntax.html
By default, triggers that have the same trigger event and action time activate in the order they were created. To affect trigger order, specify a clause after FOR EACH ROW that indicates FOLLOWS or PRECEDES and the name of an existing trigger that ... To create a trigger or drop a trigger, use the CREATE TRIGGER or DROP TRIGGER statement, described in Section 15.1.22, “CREATE TRIGGER Statement”, and Section 15.1.34, “DROP TRIGGER ...