PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/innodb-compression-tuning.html
Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed data. However, because the efficiency of compression depends on the nature of your data, you can make decisions ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-compression-usage.html
Compressed tables can be created in file-per-table tablespaces or in general tablespaces. The system tablespace (space 0, the .ibdata files) can contain user-created tables, but it also contains internal system data, which is never compressed.
https://dev.mysql.com/doc/refman/9.7/en/innodb-compression.html
This section provides information about the InnoDB table compression and InnoDB page compression features. The page compression feature is also referred to as transparent page compression. Using the compression features of InnoDB, you can create ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-data-encryption.html
InnoDB supports data-at-rest encryption for file-per-table tablespaces, general tablespaces, the mysql system tablespace, redo logs, and undo logs. You can set an encryption default for schemas and general tablespaces; this permits DBAs to control ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-disk-management.html
As a DBA, you must manage disk I/O to keep the I/O subsystem from becoming saturated, and manage disk space to avoid filling up storage devices. The ACID design model requires a certain amount of I/O that might seem redundant, but helps to ensure ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-doublewrite-buffer.html
The doublewrite buffer is a storage area where InnoDB writes pages flushed from the buffer pool before writing the pages to their proper positions in the InnoDB data files. If there is an operating system, storage subsystem, or unexpected mysqld ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-error-handling.html
InnoDB sometimes rolls back only the statement that failed, other times it rolls back the entire transaction. If you run out of file space in a tablespace, a MySQL Table is full error occurs and InnoDB rolls back the SQL statement. A transaction ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-file-defragmenting.html
Random insertions into or deletions from a secondary index can cause the index to become fragmented. Fragmentation means that the physical ordering of the index pages on the disk is not close to the index ordering of the records on the pages, or ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-information-schema-examples.html
This section describes the use of locking information as exposed by the Performance Schema data_locks and data_lock_waits tables. Identifying Blocking Transactions It is sometimes helpful to identify which transaction blocks another. The tables ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-locking.html
Shared and Exclusive Locks Intention Locks Record Locks Gap Locks Next-Key Locks Insert Intention Locks AUTO-INC Locks Predicate Locks for Spatial Indexes Shared and Exclusive Locks InnoDB implements standard row-level locking where there are two ...