Search Results
https://dev.mysql.com/doc/refman/8.4/en/information-schema-view-routine-usage-table.html
The VIEW_ROUTINE_USAGE table provides access to information about stored functions used in view definitions. The table does not list information about built-in (native) functions or loadable functions used in the definitions. You can see ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-view-table-usage-table.html
The VIEW_TABLE_USAGE table provides access to information about tables and views used in view definitions. You can see information only for views for which you have some privilege, and only for tables for which you have some privilege. The ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-adaptive-hash.html
The adaptive hash index enables InnoDB to perform more like an in-memory database on systems with appropriate combinations of workload and sufficient memory for the buffer pool without sacrificing transactional features or reliability. The adaptive ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-architecture.html
The following diagram shows in-memory and on-disk structures that comprise the InnoDB storage engine architecture. For information about each structure, see Section 17.5, “InnoDB In-Memory Structures”, and Section 17.6, “InnoDB On-Disk ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-flushing.html
InnoDB performs certain tasks in the background, including flushing of dirty pages from the buffer pool. Dirty pages are those that have been modified but are not yet written to the data files on disk. The number of page cleaner threads is ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-buffer-pool-in-core-file.html
A core file records the status and memory image of a running process. Because the buffer pool resides in main memory, and the memory image of a running process is dumped to the core file, systems with large buffer pools can produce large core files ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-compression-background.html
Because processors and cache memories have increased in speed more than disk storage devices, many workloads are disk-bound. Data compression enables smaller database size, reduced I/O, and improved throughput, at the small cost of increased CPU ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-configuration.html
This section provides configuration information and procedures for InnoDB initialization, startup, and various components and features of the InnoDB storage engine. For information about optimizing database operations for InnoDB tables, see Section ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-deadlock-detection.html
When deadlock detection is enabled (the default), InnoDB automatically detects transaction deadlocks and rolls back a transaction or transactions to break the deadlock. InnoDB tries to pick small transactions to roll back, where the size of a ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-doublewrite-buffer.html
The doublewrite buffer is a storage area where InnoDB writes pages flushed from the buffer pool before writing the pages to their proper positions in the InnoDB data files. If there is an operating system, storage subsystem, or unexpected mysqld ...