PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.5Kb
Man Pages (Zip)
- 401.9Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-metrics-table.html
Each monitor represents a point within the InnoDB source code that is instrumented to gather counter information. The INNODB_METRICS table provides a wide variety of InnoDB performance information, complementing the specific focus areas of the ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-st-geometry-columns-table.html
Permitted values are: geometry, point, linestring, polygon, multipoint, multilinestring, multipolygon, geometrycollection. The ST_GEOMETRY_COLUMNS table provides information about table columns that store spatial data. This table is based on the ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-and-mysql-replication.html
It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica.
https://dev.mysql.com/doc/refman/8.0/en/innodb-auto-increment-handling.html
The current maximum auto-increment counter value is written to the redo log each time it changes and saved to the data dictionary on each checkpoint. On a server restart during crash recovery, InnoDB initializes the in-memory auto-increment counter ... InnoDB provides a configurable locking mechanism that can significantly improve scalability and performance of SQL statements that add rows to tables with AUTO_INCREMENT ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-backup-recovery.html
For information about point-in-time recovery, recovery from disk failure or corruption, and how InnoDB performs crash recovery, see Section 17.18.2, “InnoDB Recovery”. This section covers topics related to InnoDB backup and recovery. For ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-backup.html
In conjunction with the MySQL binary log, users can perform point-in-time recovery. The key to safe database management is making regular backups. Hot and cold backups are physical backups that copy actual data files, which can be used directly by ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-compression-tuning.html
On the other hand, tables containing mostly binary data (integers or floating point numbers) or data that is previously compressed (for example JPEG or PNG images) may not generally compress well, significantly or at all. Most often, the internal ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-configuring-io-capacity.html
Ignoring I/O Capacity at Checkpoints The innodb_flush_sync variable, which is enabled by default, causes the innodb_io_capacity setting to be ignored during bursts of I/O activity that occur at checkpoints. When configuring innodb_io_capacity_max, ... The InnoDB master thread and other threads perform various tasks in the background, most of which are I/O related, such as flushing dirty pages from the buffer pool and writing changes from the change buffer to the appropriate secondary ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-file-space.html
The 768-byte prefix is accompanied by a 20-byte value that stores the true length of the column and points into the overflow list where the rest of the value is stored. DYNAMIC and COMPRESSED Row Formats When a variable-length column is chosen for ... The data files that you define in the configuration file using the innodb_data_file_path configuration option form the InnoDB system ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-introduction.html
InnoDB is a general-purpose storage engine that balances high reliability and high performance. Unless you have configured a different default storage engine, issuing a CREATE TABLE statement without an ENGINE clause creates an InnoDB table. Key ...