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/innodb-page-compression.html
InnoDB supports page-level compression for tables that reside in file-per-table tablespaces. Page compression is enabled by specifying the COMPRESSION attribute with CREATE TABLE or ALTER TABLE. Supported Platforms Page compression requires sparse ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-compression-oltp.html
Traditionally, the InnoDB compression feature was recommended primarily for read-only or read-mostly workloads, such as in a data warehouse configuration. The rise of SSD storage devices, which are fast but relatively small and expensive, makes ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-performance-midpoint_insertion.html
Rather than using a strict LRU algorithm, InnoDB uses a technique to minimize the amount of data that is brought into the buffer pool and never accessed again. The goal is to make sure that frequently accessed (“hot”) pages remain in the buffer ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-persistent-stats.html
The persistent optimizer statistics feature improves plan stability by storing statistics to disk and making them persistent across server restarts so that the optimizer is more likely to make consistent choices each time for a given query.
https://dev.mysql.com/doc/refman/8.0/en/innodb-physical-structure.html
With the exception of spatial indexes, InnoDB indexes are B-tree data structures. Spatial indexes use R-trees, which are specialized data structures for indexing multi-dimensional data. Index records are stored in the leaf pages of their B-tree or ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-recovery.html
To achieve point-in-time recovery after restoring a backup, you can apply changes from the binary log that occurred after the backup was made. Recovery from Data Corruption or Disk Failure If your database becomes corrupted or disk failure occurs, ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html
The redo log is a disk-based data structure used during crash recovery to correct data written by incomplete transactions. During normal operations, the redo log encodes requests to change table data that result from SQL statements or low-level API ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-row-format.html
The row format of a table determines how its rows are physically stored, which in turn can affect the performance of queries and DML operations. As more rows fit into a single disk page, queries and index lookups can work faster, less cache memory ...
https://dev.mysql.com/doc/refman/8.0/en/internal-temporary-tables.html
In some cases, the server creates internal temporary tables while processing statements. The server creates temporary tables under conditions such as these: Evaluation of UNION statements, with some exceptions described later. Evaluation of some ...
https://dev.mysql.com/doc/refman/8.0/en/ipv6-remote-connections.html
The following procedure shows how to configure MySQL to permit IPv6 connections by remote clients. It is similar to the preceding procedure for local clients, but the server and client hosts are distinct and each has its own nonlocal IPv6 address.