PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/optimizer-issues.html
To use it, just add the keyword EXPLAIN to the front of your SELECT statement: mysql> EXPLAIN SELECT * FROM t1, t2 WHERE t1.i = t2.i; EXPLAIN is discussed in more detail in Section 13.8.2, “EXPLAIN Statement”. Use FORCE INDEX for the scanned ...
https://dev.mysql.com/doc/refman/5.7/en/pam-pluggable-authentication.html
For example: mysql> SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE '%pam%'; +--------------------+---------------+ | PLUGIN_NAME | PLUGIN_STATUS | +--------------------+---------------+ | authentication_pam ... Note PAM pluggable authentication is an extension included in MySQL Enterprise Edition, a commercial ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations.html
This section discusses current restrictions and limitations on MySQL partitioning support. The following constructs are not permitted in partitioning expressions: Stored procedures, stored functions, loadable functions, or plugins. For a list of ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-filtering.html
The setup_instruments table lists the instruments for which events can be collected, whether they are enabled, and (for enabled instruments) whether to collect timing information: mysql> SELECT * FROM performance_schema.setup_instruments; ... Events ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-runtime-configuration.html
Specific Performance Schema features can be enabled at runtime to control which types of event collection occur. If you have the UPDATE privilege, you can change Performance Schema operation by modifying setup tables to affect how monitoring occurs. For additional details about these tables, see Section 25.12.2, “Performance Schema Setup ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-transaction-tables.html
To selectively examine transaction history, use the attribute columns in the transaction event tables: ACCESS_MODE, ISOLATION_LEVEL, and AUTOCOMMIT. Within the event hierarchy, wait events nest within stage events, which nest within statement ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-wait-tables.html
The Performance Schema instruments waits, which are events that take time. Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store wait events: ...
https://dev.mysql.com/doc/refman/5.7/en/proxy-users.html
mysql> SELECT USER(), CURRENT_USER(); +------------------+-------------------+ | USER() | CURRENT_USER() | +------------------+-------------------+ | myuser@localhost | manager@localhost | +------------------+-------------------+ For simplicity, ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-invoked.html
You can do this by storing in a separate table the event names from the SELECT statement shown previously, or using ALTER EVENT statements to rename the events with a common prefix such as replicated_ to identify them. If you rename the events, then ... Replication of invoked features such as loadable functions and stored programs (stored procedures and functions, triggers, and events) provides the following characteristics: The effects of the feature are always ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
SELECT statement is recorded in the binary log as one transaction with one GTID, but if ROW format is used, the statement is recorded as two transactions with two GTIDs. Because GTID-based replication is dependent on transactions, some features ...