PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations-locking.html
TRUNCATE PARTITION prunes locks; only the partitions to be emptied are locked. In MySQL 5.7, partition lock pruning eliminates unneeded locks in many cases, and most statements reading from or updating a partitioned MyISAM table cause only the ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-limitations.html
Starting in MySQL 5.7.2, ANALYZE, CHECK, OPTIMIZE, REPAIR, and TRUNCATE operations are supported with subpartitions. This section discusses current restrictions and limitations on MySQL partitioning support. The following constructs are not ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-management.html
MySQL 5.7 provides a number of ways to modify partitioned tables. It is possible to add, drop, redefine, merge, or split existing partitions. All of these actions can be carried out using the partitioning extensions to the ALTER TABLE statement.
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-accounts-table.html
For a description of how the Performance Schema maintains rows in this table, including the effect of TRUNCATE TABLE, see Section 25.12.8, “Performance Schema Connection Tables”. The accounts table contains a row for each account that has ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-cond-instances-table.html
The cond_instances table lists all the conditions seen by the Performance Schema while the server executes. A condition is a synchronization mechanism used in the code to signal that a specific event has happened, so that a thread waiting for this ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-events-stages-current-table.html
The table stores one row per thread showing the current status of the thread's most recent monitored stage event, so there is no system variable for configuring the table size. Of the tables that contain stage event rows, events_stages_current is ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-events-stages-history-long-table.html
The events_stages_history_long table contains the N most recent stage events that have ended globally, across all threads. Stage events are not added to the table until they have ended. When the table becomes full, the oldest row is discarded when ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-events-stages-history-table.html
The events_stages_history table contains the N most recent stage events that have ended per thread. Stage events are not added to the table until they have ended. When the table contains the maximum number of rows for a given thread, the oldest ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-events-statements-current-table.html
The table stores one row per thread showing the current status of the thread's most recent monitored statement event, so there is no system variable for configuring the table size. Of the tables that contain statement event rows, ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-events-statements-history-long-table.html
The events_statements_history_long table contains the N most recent statement events that have ended globally, across all threads. Statement events are not added to the table until they have ended. When the table becomes full, the oldest row is ...