Search Results
https://dev.mysql.com/doc/refman/8.4/en/example-storage-engine.html
The EXAMPLE storage engine is a stub engine that does nothing. Its purpose is to serve as an example in the MySQL source code that illustrates how to begin writing new storage engines. To enable the EXAMPLE storage engine if you build MySQL from ...
https://dev.mysql.com/doc/refman/8.4/en/faqs-storage-engines.html
What are the unique benefits of the ARCHIVE storage engine? The ARCHIVE storage engine stores large amounts of data without indexes; it has a small footprint, and performs selects using table scans. Where can I obtain complete documentation for ...
https://dev.mysql.com/doc/refman/8.4/en/identifier-mapping.html
For the data and index files, the exact representation on disk is storage engine specific. There is a correspondence between database and table identifiers and names in the file system. For the basic structure, MySQL represents each database as a ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-table-constraints-table.html
The UNIQUE and PRIMARY KEY information is about the same as what you get from the Key_name column in the output from SHOW INDEX when the Non_unique column is 0. The TABLE_CONSTRAINTS table has these columns: CONSTRAINT_CATALOG The name of the ...
https://dev.mysql.com/doc/refman/8.4/en/innochecksum.html
This tool reads an InnoDB tablespace file, calculates the checksum for each page, compares the calculated checksum to the stored checksum, and reports mismatches, which indicate damaged pages. It was originally developed to speed up verifying the ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-optimization.html
InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory. Knowing how the InnoDB buffer pool works, and taking advantage of it to keep frequently accessed data in memory, is an important aspect of MySQL tuning.
https://dev.mysql.com/doc/refman/8.4/en/innodb-init-startup-configuration.html
Buffers specific to InnoDB are configured using the following parameters: innodb_buffer_pool_size defines size of the buffer pool, which is the memory area that holds cached data for InnoDB tables, indexes, and other auxiliary buffers. The first ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-monitor-types.html
There are two types of InnoDB monitor: The standard InnoDB Monitor displays the following types of information: Work done by the main background thread Semaphore waits Data about the most recent foreign key and deadlock errors Lock waits for ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-system-tablespace.html
It may also contain table and index data if tables are created in the system tablespace rather than file-per-table or general tablespaces. The system tablespace is the storage area for the change buffer. By default, a single system tablespace data ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-troubleshooting.html
The following general guidelines apply to troubleshooting InnoDB problems: When an operation fails or you suspect a bug, look at the MySQL server error log (see Section 7.4.2, “The Error Log”). Server Error Message Reference provides ...