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/innodb-information-schema-buffer-pool-tables.html
The InnoDB INFORMATION_SCHEMA buffer pool tables provide buffer pool status information and metadata about the pages within the InnoDB buffer pool. The InnoDB INFORMATION_SCHEMA buffer pool tables include those listed below: mysql> SHOW TABLES FROM ...Do not query these tables on a production system unless you are aware of the performance impact and have determined it to be ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-row-format.html
The InnoDB storage engine supports four row formats: REDUNDANT, COMPACT, DYNAMIC, and COMPRESSED. The REDUNDANT row format is supported by both InnoDB file formats (Antelope and Barracuda). The COMPACT row format is supported by both InnoDB file ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-limits.html
This section describes limits for InnoDB tables, indexes, tablespaces, and other aspects of the InnoDB storage engine. If innodb_large_prefix is enabled (the default), the index key prefix limit is 3072 bytes for InnoDB tables that use the DYNAMIC ...A table can contain a maximum of 1017 columns (raised in MySQL 5.6.9 from the earlier limit of ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-performance-use_sys_malloc.html
When InnoDB was developed, the memory allocators supplied with operating systems and run-time libraries were often lacking in performance and scalability. Therefore, InnoDB implemented its own memory allocator in the mem subsystem. InnoDB also ...
https://dev.mysql.com/doc/refman/5.7/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 5.4.2, “The Error Log”). Server Error Message Reference provides ...When ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-benefits.html
The combination of InnoDB tables and memcached offers advantages over using either by themselves. Direct access to the InnoDB storage engine avoids the parsing and planning overhead of SQL. Data written using the memcached protocol is transparently ...Running memcached in the same process space as the MySQL server avoids the network overhead of passing requests back and ...
https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
Serious corruption might cause SELECT * FROM tbl_name statements or InnoDB background operations to unexpectedly exit or assert, or even cause InnoDB roll-forward recovery to crash. In such cases, you can use the innodb_force_recovery option to ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-disk-io.html
InnoDB uses asynchronous disk I/O where possible, by creating a number of threads to handle I/O operations, while permitting other database operations to proceed while the I/O is still in progress. On Linux and Windows platforms, InnoDB uses the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
As InnoDB evolves, data file formats that are not compatible with prior versions of InnoDB are sometimes required to support new features. To help manage compatibility in upgrade and downgrade situations, and systems that run different versions of ...General tablespaces provide support for all row formats and associated ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-locking-transaction-model.html
To implement a large-scale, busy, or highly reliable database application, to port substantial code from a different database system, or to tune MySQL performance, it is important to understand InnoDB locking and the InnoDB transaction model. This ...It also discusses the use of autocommit, consistent non-locking reads, and locking ...