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/performance-schema-statement-summary-tables.html
The Performance Schema maintains tables for collecting current and recent statement events, and aggregates that information in summary tables. Section 29.12.6, “Performance Schema Statement Event Tables” describes the events on which statement ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-system-variables.html
The Performance Schema automatically sizes the values of several of its parameters at server startup if they are not set explicitly. Performance Schema system variables have the following meanings: performance_schema Command-Line Format ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-transaction-tables.html
Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store transaction events: events_transactions_current: The current transaction event for each ...
https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html
The privileges granted to a MySQL account determine which operations the account can perform. MySQL privileges differ in the contexts in which they apply and at different levels of operation: Administrative privileges enable users to manage ...
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/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 ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids.html
This section explains transaction-based replication using global transaction identifiers (GTIDs). Because GTID-based replication is completely transaction-based, it is simple to determine whether sources and replicas are consistent; as long as all ...
https://dev.mysql.com/doc/refman/8.0/en/replication-implementation.html
Replication is based on the source server keeping track of all changes to its databases (updates, deletes, and so on) in its binary log. The binary log serves as a written record of all events that modify database structure or content (data) from ...