PDF (US Ltr)
- 41.8Mb
PDF (A4)
- 41.9Mb
Man Pages (TGZ)
- 272.4Kb
Man Pages (Zip)
- 378.4Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/partitioning-limitations.html
Tables employing user-defined partitioning do not preserve the SQL mode in effect at the time that they were created. Therefore, a change in the SQL mode at any time after the creation of partitioned tables may lead to major changes in the behavior ... This section discusses current restrictions and limitations on MySQL partitioning ...
https://dev.mysql.com/doc/refman/9.7/en/partitioning-management-exchange.html
Exchanging Partitions Without Row-By-Row Validation To avoid time consuming validation when exchanging a partition with a table that has many rows, it is possible to skip the row-by-row validation step by appending WITHOUT VALIDATION to the ALTER ...
https://dev.mysql.com/doc/refman/9.7/en/pattern-matching.html
MySQL provides standard SQL pattern matching as well as a form of pattern matching based on extended regular expressions similar to those used by Unix utilities such as vi, grep, and sed. SQL pattern matching enables you to use _ to match any ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-consumer-filtering.html
If you disable a consumer, the server does not spend time maintaining destinations for that consumer. If checked, they act as follows: events_statements_cpu, if NO, disables measurement of CPU_TIME. If YES, and the instrumentation is enabled and ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-data-locks-table.html
Use the data_locks table to help diagnose performance problems that occur during times of heavy concurrent load. Lock ID formats are internal and subject to change at any time. For information about which lock requests are blocked by which held ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-event-tables.html
For wait, stage, statement, and transaction events, the Performance Schema can monitor and store current events. In addition, when events end, the Performance Schema can store them in history tables. For each event type, the Performance Schema uses ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-instrumentation-checking.html
It is always possible to determine what instruments the Performance Schema includes by checking the setup_instruments table. Changes to this code occur often, which also affects the set of instruments. It is not practical to list all the ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-mutex-instances-table.html
A mutex is a synchronization mechanism used in the code to enforce that only one thread at a given time can have access to some common resource. The work performed while holding a mutex is said to be in a “critical section,” and multiple queries ... The mutex_instances table lists all the mutexes seen by the Performance Schema while the server ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-replication-connection-status-table.html
LAST_ERROR_TIMESTAMP A timestamp in 'YYYY-MM-DD hh:mm:ss[.fraction]' format that shows when the most recent I/O error took place. LAST_HEARTBEAT_TIMESTAMP A timestamp in 'YYYY-MM-DD hh:mm:ss[.fraction]' format that shows when the most recent ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-replication-tables.html
The following Performance Schema replication tables continue to be populated when the Performance Schema is disabled: replication_connection_configuration replication_connection_status replication_asynchronous_connection_failover ...This is similar ...