PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-log-status-table.html
The log_status table provides information that enables an online backup tool to copy the required log files without locking those resources for the duration of the copy process. When the log_status table is queried, the server blocks logging and ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-metadata-locks-table.html
Metadata locking applies not just to tables, but also to schemas, stored programs (procedures, functions, triggers, scheduled events), tablespaces, user locks acquired with the GET_LOCK() function (see Section 14.14, “Locking Functions”), and ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-socket-instances-table.html
The socket_instances table provides a real-time snapshot of the active connections to the MySQL server. The table contains one row per TCP/IP or Unix socket file connection. Information available in this table provides a real-time snapshot of the ...row *************************** EVENT_NAME: wait/io/socket/sql/server_unix_socket OBJECT_INSTANCE_BEGIN: 4316619408 THREAD_ID: 1 SOCKET_ID: 16 IP: PORT: 0 STATE: ACTIVE *************************** ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-socket-summary-tables.html
These socket summary tables aggregate timer and byte count information for socket operations: socket_summary_by_event_name: Aggregate timer and byte count statistics generated by the wait/io/socket/* instruments for all socket I/O operations, per ...socket_summary_by_instance: Aggregate timer and byte count statistics generated by the wait/io/socket/* instruments for all socket I/O operations, per socket ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-table-reference.html
The following table summarizes all available Performance Schema tables. For greater detail, see the individual table descriptions. Table 29.1 Performance Schema Tables Table Name Description accounts Connection statistics per client account ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-wait-tables.html
These tables store wait events: events_waits_current: The current wait event for each thread. There are also summary tables that aggregate information about wait events; see Section 29.12.20.1, “Wait Event Summary Tables”. For more information ... The Performance Schema instruments waits, which are events that take ...
https://dev.mysql.com/doc/refman/8.0/en/repair-table-optimization.html
An alternative that avoids this problem is to use a separate key cache, assign to it the indexes from the table to be repaired, and deallocate it when the repair is complete. REPAIR TABLE for MyISAM tables is similar to using myisamchk for repair ...You may be able to its improve performance by setting these variables, as described in Section 6.6.4.6, “myisamchk Memory ...
https://dev.mysql.com/doc/refman/8.0/en/thread-pool-information-schema-tables.html
Note As of MySQL 8.0.14, the INFORMATION_SCHEMA thread pool tables are also available as Performance Schema tables. (See Section 29.12.16, “Performance Schema Thread Pool Tables”.) The INFORMATION_SCHEMA tables are deprecated; expect them be ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-innodb-bulk-data-loading.html
COMMIT; The mysqldump option --opt creates dump files that are fast to import into an InnoDB table, even without wrapping them with the SET autocommit and COMMIT statements. If you have UNIQUE constraints on secondary keys, you can speed up table ...
https://dev.mysql.com/doc/refman/8.0/en/storage-engine-setting.html
To convert a table from one storage engine to another, use an ALTER TABLE statement that indicates the new engine: ALTER TABLE t ENGINE = InnoDB; See Section 15.1.20, “CREATE TABLE Statement”, and Section 15.1.9, “ALTER TABLE Statement”. By ... When you create a new table, you can specify which storage engine to use by adding an ENGINE table option to the CREATE TABLE statement: -- ENGINE=INNODB not needed unless you have set a different -- default storage ...