PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/innodb-optimize-tablespace-page-allocation.html
As of MySQL 8.0.22, 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.
https://dev.mysql.com/doc/refman/8.0/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/8.0/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/8.0/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/8.0/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/8.0/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/8.0/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 ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-transaction-scheduling.html
InnoDB uses the Contention-Aware Transaction Scheduling (CATS) algorithm to prioritize transactions that are waiting for locks. When multiple transactions are waiting for a lock on the same object, the CATS algorithm determines which transaction ...
https://dev.mysql.com/doc/refman/8.0/en/install-plugin.html
INSTALL PLUGIN plugin_name SONAME 'shared_library_name' This statement installs a server plugin. It requires the INSERT privilege for the mysql.plugin system table because it adds a row to that table to register the plugin. plugin_name is the name ...
https://dev.mysql.com/doc/refman/8.0/en/installing-development-tree.html
This section describes how to install MySQL from the latest development source code, which is hosted on GitHub. To obtain the MySQL Server source code from this repository hosting service, you can set up a local MySQL Git repository. On GitHub, ...