PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-setup-objects-table.html
The setup_objects table controls whether the Performance Schema monitors particular objects. This table has a maximum size of 100 rows by default. To change the table size, modify the performance_schema_setup_objects_size system variable at server ...The order in which matching occurs matters because different matching setup_objects rows can have different ENABLED and TIMED ...
https://dev.mysql.com/doc/refman/5.7/en/partitioning-handling-nulls.html
DROP PARTITION, see Section 13.1.8, “ALTER TABLE Statement”.) NULL is also treated in this way for partitioning expressions that use SQL functions. If you insert a row into a table partitioned by RANGE such that the column value used to ...
https://dev.mysql.com/doc/refman/5.7/en/checksum-table.html
[QUICK | EXTENDED] CHECKSUM TABLE reports a checksum for the contents of a table. If you run CHECKSUM TABLE against a view, the Checksum value is always NULL, and a warning is returned. For a nonexistent table, CHECKSUM TABLE returns NULL and ...You ...
https://dev.mysql.com/doc/refman/5.7/en/myisam-table-close.html
Each MyISAM index file (.MYI file) has a counter in the header that can be used to check whether a table has been closed properly. If you get the following warning from CHECK TABLE or myisamchk, it means that this counter has gone out of sync: ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-transaction-tables.html
These tables store transaction events: events_transactions_current: The current transaction event for each thread. There are also summary tables that aggregate information about transaction events; see Section 25.12.15.4, “Transaction Summary ...
https://dev.mysql.com/doc/refman/5.7/en/tracing-example.html
Next, for every table in the query, we estimate the cost of, and number of records returned by, a table scan or a range access. "resulting_clause_is_simple": true, "resulting_clause": "`test`.`alias1`.`col_int_key`" } /* clause_processing */ }, The ...Now we can examine the trace, whose first column (QUERY), containing the original statement to be traced, is shown here: SELECT * FROM INFORMATION_SCHEMA.OPTIMIZER_TRACE\G *************************** ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-data-encryption.html
mysql> CREATE TABLE t1 (c1 INT) ENCRYPTION='Y'; To enable encryption for an existing file-per-table tablespace, specify the ENCRYPTION option in an ALTER TABLE statement. mysql> ALTER TABLE t1 ENCRYPTION='Y'; To disable encryption for file-per-table ...About Data-at-Rest Encryption Encryption Prerequisites Enabling File-Per-Table Tablespace Encryption Master Key Rotation Encryption and Recovery Exporting Encrypted Tablespaces Encryption and Replication Identifying Encrypted Tablespaces Encryption Usage Notes Encryption Limitations About Data-at-Rest Encryption InnoDB uses a two tier encryption key architecture, consisting of a master encryption key and tablespace ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-binary-log.html
For example, DDL statements such as CREATE TABLE and ALTER TABLE are always logged as statements, without regard to the logging format in effect, so the following statement-based rules for --binlog-do-db always apply in determining whether or not ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-information-schema-buffer-pool-tables.html
The InnoDB INFORMATION_SCHEMA buffer pool tables provide buffer pool status information and metadata about the pages within the InnoDB buffer pool. The InnoDB INFORMATION_SCHEMA buffer pool tables include those listed below: mysql> SHOW TABLES FROM ...INNODB_BUFFER_PAGE_LRU: Holds information about the pages in the InnoDB buffer pool, in particular how they are ordered in the LRU list that determines which pages to evict from the buffer pool when it becomes ...
https://dev.mysql.com/doc/refman/5.7/en/audit-log-file-formats.html
The MySQL server calls the audit log plugin to write an audit record to its log file whenever an auditable event occurs. <AUDIT_RECORD> <TIMESTAMP>2019-10-03T14:09:38 UTC</TIMESTAMP> <RECORD_ID>6_2019-10-03T14:06:33</RECORD_ID> <NAME>Query</NAME> ...Typically the first audit record written after plugin startup contains the server description and startup ...