PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 255.5Kb
Man Pages (Zip)
- 360.4Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.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/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-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/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 ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-ddl.html
You can access the underlying InnoDB table (which is test.demo_test by default) through standard SQL interfaces. However, there are some restrictions: When querying a table that is also accessed through the memcached interface, remember that ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-memcached-replication.html
Because the daemon_memcached plugin supports the MySQL binary log, updates made on a source server through the memcached interface can be replicated for backup, balancing intensive read workloads, and high availability. You do not need to set up ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-multi-versioning.html
It keeps information about old versions of changed rows to support transactional features such as concurrency and rollback. This information is stored in the system tablespace or undo tablespaces in a data structure called a rollback segment. InnoDB ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-buffer-pools.html
For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, by reducing contention as different threads read and write to cached pages. This feature is typically intended for ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-online-ddl-space-requirements.html
Online DDL operations have the following space requirements: Temporary log files: A temporary log file records concurrent DML when an online DDL operation creates an index or alters a table. The temporary log file is extended as required by the ...
https://dev.mysql.com/doc/refman/5.7/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 ...