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
For statements affecting partitioned tables using storage engines such as InnoDB, that employ row-level locking and do not actually perform (or need to perform) the locks prior to partition pruning, this is not an issue. In MySQL 5.7, partition lock ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-list.html
For an InnoDB table, the statement is considered a single transaction, so the presence of any unmatched values causes the statement to fail completely, and no rows are inserted. List partitioning in MySQL is similar to range partitioning in many ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-maintenance.html
Some MySQL storage engines, including InnoDB, do not support per-partition optimization; in these cases, ALTER TABLE ... A number of table and partition maintenance tasks can be carried out using SQL statements intended for such purposes on ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-pruning.html
This limitation does not apply to partitioned tables using other MySQL storage engines such as InnoDB. The core concept behind partition pruning is relatively simple, and can be described as “Do not scan partitions where there can be no matching ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-filtering-names.html
Even less suitable is the pattern '%file%' because it matches instruments with 'file' anywhere in the name, such as wait/synch/mutex/innodb/file_open_mutex. Names given for filtering operations can be as specific or general as required. For ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-instrument-naming.html
Suffixes may include levels such as these: A name for the major element (a server module such as myisam, innodb, mysys, or sql) or a plugin name. An instrument name consists of a sequence of elements separated by '/' characters. Example names: ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-processlist-table.html
For use with MySQL HeatWave Service and MySQL HeatWave, where the PRIMARY engine is InnoDB and the SECONDARY engine is MySQL HeatWave (RAPID). Note The processlist table is automatically created in the Performance Schema for new installations of ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-threads-table.html
Examples are internal InnoDB threads, “binlog dump” threads sending information to replicas, and replication I/O and SQL threads. The threads table contains a row for each server thread. Each row contains information about a thread and ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-transaction-tables.html
Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store transaction events: events_transactions_current: The current transaction event for each ...
https://dev.mysql.com/doc/refman/5.7/en/primary-key-optimization.html
With the InnoDB storage engine, the table data is physically organized to do ultra-fast lookups and sorts based on the primary key column or columns. The primary key for a table represents the column or set of columns that you use in your most ...