PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.3Kb
Man Pages (Zip)
- 402.5Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-buffer-page-table.html
The INNODB_BUFFER_PAGE table provides information about each page in the InnoDB buffer pool. For related usage information and examples, see Section 17.15.5, “InnoDB INFORMATION_SCHEMA Buffer Pool Tables”. Do not query this table on a ...To ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-status-variable-tables.html
Status variable information is available in these Performance Schema tables: global_status: Global status variables. An application that wants only global values should use this table. An application that wants all status variable values for its own ... The MySQL server maintains many status variables that provide information about its operation (see Section 7.1.10, “Server Status ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-auto-increment-handling.html
To make this clear, consider an example that uses this table: CREATE TABLE t1 ( c1 INT(11) NOT NULL AUTO_INCREMENT, c2 VARCHAR(10) DEFAULT NULL, PRIMARY KEY (c1) ) ENGINE=InnoDB; Suppose that there are two transactions running, each inserting rows ... InnoDB provides a configurable locking mechanism that can significantly improve scalability and performance of SQL statements that add rows to tables with AUTO_INCREMENT ...
https://dev.mysql.com/doc/refman/8.0/en/information-schema-innodb-ft-config-table.html
use_stopword: Indicates whether a stopword table is used, which is defined when the FULLTEXT index is created. The INNODB_FT_CONFIG table provides metadata about the FULLTEXT index and associated processing for an InnoDB table. Before querying it, ...The values for this column might change, depending on the needs for performance tuning and debugging for InnoDB full-text ...
https://dev.mysql.com/doc/refman/8.0/en/metadata-locking.html
Metadata locking applies not just to tables, but also to schemas, stored programs (procedures, functions, triggers, scheduled events), tablespaces, user locks acquired with the GET_LOCK() function (see Section 14.14, “Locking Functions”), and ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-temptables.html
In statement-based replication mode, CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements cannot be used inside a transaction, procedure, function, or trigger when GTIDs are in use on the server (that is, when the enforce_gtid_consistency ...
https://dev.mysql.com/doc/refman/8.0/en/innodb-information-schema-metrics-table.html
Create a simple InnoDB table: mysql> USE test; Database changed mysql> CREATE TABLE t1 (c1 INT) ENGINE=INNODB; Query OK, 0 rows affected (0.02 sec) Enable the dml_inserts counter. The INNODB_METRICS table provides information about InnoDB ...SET ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-events-transactions-current-table.html
The table stores one row per thread showing the current status of the thread's most recent monitored transaction event, so there is no system variable for configuring the table size. Other tables that contain transaction event rows are logically ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-processlist-table.html
For a comparison of this table with other sources, see Sources of Process Information. Note If the performance_schema_show_processlist system variable is enabled, the processlist table also serves as the basis for an alternative implementation ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-upgrade.html
Each time you upgrade MySQL, you should execute mysql_upgrade, which looks for incompatibilities with the upgraded MySQL server: It upgrades the system tables in the mysql schema so that you can take advantage of new privileges or capabilities that ... Note As of MySQL 8.0.16, the MySQL server performs the upgrade tasks previously handled by mysql_upgrade (for details, see Section 3.4, “What the MySQL Upgrade Process ...