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/kill.html
In most cases, it might take some time for the thread to die because the kill flag is checked only at specific intervals: During SELECT operations, for ORDER BY and GROUP BY loops, the flag is checked after reading a block of rows. ALTER TABLE ...
https://dev.mysql.com/doc/refman/8.0/en/monitor-innodb-mutex-waits-performance-schema.html
| wait/synch/mutex/innodb/master_key_id_mutex | YES | YES | +-------------------------------------------------------+---------+-------+ 49 rows in set (0.00 sec) Enable wait event consumers by updating the setup_consumers table. mysql> UPDATE ... A ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-backup-id.html
This table provides a way to find the ID of the backup started most recently for this cluster. The backup_id table contains a single column id, which corresponds to a backup ID taken using the ndb_mgm client START BACKUP command.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-tc-time-track-stats.html
tc_time_track_stats presents this information as rows, with a row for each instance of the following: Data node, using its ID TC block instance Other communicating data node or API node, using its ID Upper bound value Each row contains a value for ... The tc_time_track_stats table provides time-tracking information obtained from the DBTC block (TC) instances in the data nodes, through API nodes access ...
https://dev.mysql.com/doc/refman/8.0/en/optimizing-myisam-bulk-data-loading.html
To increase performance for MyISAM tables, for both LOAD DATA and INSERT, enlarge the key cache by increasing the key_buffer_size system variable. For a MyISAM table, you can use concurrent inserts to add rows at the same time that SELECT statements ... These performance tips supplement the general guidelines for fast inserts in Section 10.2.5.1, “Optimizing INSERT ...
https://dev.mysql.com/doc/refman/8.0/en/outer-join-simplification.html
(That is, it converts the outer join to an inner join.) A condition is said to be null-rejected for an outer join operation if it evaluates to FALSE or UNKNOWN for any NULL-complemented row generated for the operation. Table expressions in the FROM ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-component-scheduler-tasks-table.html
The component_scheduler_tasks table contains a row for each scheduled task. Each row contains information about the ongoing progress of a task that applications, components, and plugins can implement, optionally, using the scheduler component (see ...For example, the audit_log server plugin utilizes the scheduler component to run a regular, recurring flush of its memory cache: mysql> select * from performance_schema.component_scheduler_tasks\G *************************** ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-objects-summary-global-by-type-table.html
row *************************** OBJECT_TYPE: TABLE OBJECT_SCHEMA: test OBJECT_NAME: t COUNT_STAR: 3 SUM_TIMER_WAIT: 263126976 MIN_TIMER_WAIT: 1522272 AVG_TIMER_WAIT: 87708678 MAX_TIMER_WAIT: 258428280 ... row *************************** OBJECT_TYPE: ... The Performance Schema maintains the objects_summary_global_by_type table for aggregating object wait ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-setup-threads-table.html
row *************************** NAME: thread/performance_schema/setup ENABLED: YES HISTORY: YES PROPERTIES: singleton VOLATILITY: 0 DOCUMENTATION: NULL ... row *************************** NAME: thread/sql/main ENABLED: YES HISTORY: YES PROPERTIES: ...It exposes thread class names and attributes: mysql> SELECT * FROM performance_schema.setup_threads\G *************************** ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-socket-summary-tables.html
When a connection terminates, the row in socket_summary_by_instance corresponding to it is deleted. Except for events_statements_summary_by_digest, it resets the summary columns to zero rather than removing rows. These socket summary tables ...