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-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 undo tablespaces in a data structure called a rollback segment. InnoDB uses the information in ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-online-ddl-failure-conditions.html
The failure of an online DDL operation is typically due to one of the following conditions: An ALGORITHM clause specifies an algorithm that is not compatible with the particular type of DDL operation or storage engine. A LOCK clause specifies a low ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-online-ddl-single-multi.html
Before the introduction of online DDL, it was common practice to combine many DDL operations into a single ALTER TABLE statement. Because each ALTER TABLE statement involved copying and rebuilding the table, it was more efficient to make several ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-optimize-tablespace-page-allocation.html
You can optimize how InnoDB allocates space to file-per-table and general tablespaces on Linux. By default, when additional space is required, InnoDB allocates pages to the tablespace and physically writes NULLs to those pages. This behavior can ...
https://dev.mysql.com/doc/refman/9.7/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/9.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 ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-performance-optimizer-statistics.html
This section describes how to configure persistent and non-persistent optimizer statistics for InnoDB tables. Persistent optimizer statistics are persisted across server restarts, allowing for greater plan stability and more consistent query ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-performance-ro-txn.html
InnoDB can avoid the overhead associated with setting up the transaction ID (TRX_ID field) for transactions that are known to be read-only. A transaction ID is only needed for a transaction that might perform write operations or locking reads such ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-purge-configuration.html
InnoDB does not physically remove a row from the database immediately when you delete it with an SQL statement. A row and its index records are only physically removed when InnoDB discards the undo log record written for the deletion. This removal ...
https://dev.mysql.com/doc/refman/9.7/en/innodb-restrictions-limitations.html
This section describes restrictions and limitations of the InnoDB storage engine. You cannot create a table with a column name that matches the name of an internal InnoDB column (including DB_ROW_ID, DB_TRX_ID, and DB_ROLL_PTR. This restriction ...