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/persisted-system-variables.html
The MySQL server maintains system variables that configure its operation. A system variable can have a global value that affects server operation as a whole, a session value that affects the current session, or both. Many system variables are ...
https://dev.mysql.com/doc/refman/8.0/en/prepare.html
PREPARE stmt_name FROM preparable_stmt The PREPARE statement prepares a SQL statement and assigns it a name, stmt_name, by which to refer to the statement later. The prepared statement is executed with EXECUTE and released with DEALLOCATE PREPARE.
https://dev.mysql.com/doc/refman/8.0/en/processlist-access.html
The following discussion enumerates the sources of process information, the privileges required to see process information, and describes the content of process list entries. The other sources have negative performance consequences because they ...
https://dev.mysql.com/doc/refman/8.0/en/program-options.html
There are several ways to specify options for MySQL programs: List the options on the command line following the program name. This is common for options that apply to a specific invocation of the program. List the options in an option file that ...
https://dev.mysql.com/doc/refman/8.0/en/programs-overview.html
Later sections provide a more detailed description of each one, with the exception of NDB Cluster programs. Each program's description indicates its invocation syntax and the options that it supports. Section 25.5, “NDB Cluster Programs”, ...
https://dev.mysql.com/doc/refman/8.0/en/query-log.html
The general query log is a general record of what mysqld is doing. The server writes information to this log when clients connect or disconnect, and it logs each SQL statement received from clients. The general query log can be very useful when you ...
https://dev.mysql.com/doc/refman/8.0/en/replication-administration-skip.html
If replication stops due to an issue with an event in a replicated transaction, you can resume replication by skipping the failed transaction on the replica. Before skipping a transaction, ensure that the replication I/O (receiver) thread is ...
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. The SHOW REPLICA STATUS statement, which you must execute on each replica, ...
https://dev.mysql.com/doc/refman/8.0/en/replication-bugs.html
When you have determined that there is no user error involved, and replication still either does not work at all or is unstable, it is time to send us a bug report. We need to obtain as much information as possible from you to be able to track down ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-lifecycle.html
The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the source. This client transaction is assigned a GTID composed of the source's UUID and the smallest nonzero transaction sequence number not yet ...