Search Results
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-data-lock-waits-table.html
The data_lock_waits table implements a many-to-many relationship showing which data lock requests in the data_locks table are blocked by which held data locks in the data_locks table. The table exposes not only which lock a session or transaction ...Held locks in data_locks appear in data_lock_waits only if they block some lock ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-table-characteristics.html
The name of the performance_schema database is lowercase, as are the names of tables within it. Many tables in the performance_schema database are read only and cannot be modified: mysql> TRUNCATE TABLE performance_schema.setup_instruments; ERROR ...Generally, the effect is to reset the summary columns to 0 or NULL, not to remove ...
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-status-variable-summary-tables.html
The Performance Schema makes status variable information available in the tables described in Section 29.12.15, “Performance Schema Status Variable Tables”. It also makes aggregated status variable information available in summary tables, ...
https://dev.mysql.com/doc/heatwave/en/mys-hw-modifying-tables.html
When an InnoDB table is loaded into MySQL HeatWave Cluster, DDL operations such as ALTER TABLE, RENAME TABLE, TRUNCATE TABLE, and DROP TABLE are permitted. While any of these operations are being executed, queries involving the modified table are ...If you are explicitly trying to use the secondary engine, these queries generate an offload ...
https://dev.mysql.com/doc/refman/8.4/en/create-table-files.html
For an InnoDB table created in a file-per-table tablespace or general tablespace, table data and associated indexes are stored in a .ibd file in the database directory. When an InnoDB table is created in the system tablespace, table data and ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-cmpmem-table.html
The INNODB_CMPMEM and INNODB_CMPMEM_RESET tables provide status information on compressed pages within the InnoDB buffer pool. The INNODB_CMPMEM and INNODB_CMPMEM_RESET tables have these columns: PAGE_SIZE The block size in bytes. row ...PAGES_USED ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-indexes-table.html
For related usage information and examples, see Section 17.15.3, “InnoDB INFORMATION_SCHEMA Schema Object Tables”. The INNODB_INDEXES table has these columns: INDEX_ID An identifier for the index. TABLE_ID An identifier representing the table ...
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-trx-table.html
The INNODB_TRX table provides information about every transaction currently executing inside InnoDB, including whether the transaction is waiting for a lock, when the transaction started, and the SQL statement the transaction is executing, if any.
https://dev.mysql.com/doc/refman/8.4/en/information-schema-innodb-virtual-table.html
The INNODB_VIRTUAL table provides metadata about InnoDB virtual generated columns and columns upon which virtual generated columns are based. A row appears in the INNODB_VIRTUAL table for each column upon which a virtual generated column is based.
https://dev.mysql.com/doc/refman/8.4/en/performance-schema-events-stages-current-table.html
The table stores one row per thread showing the current status of the thread's most recent monitored stage event, so there is no system variable for configuring the table size. Of the tables that contain stage event rows, events_stages_current is ...