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/optimizing-innodb-logging.html
If you specify a value for innodb_log_write_ahead_size that is larger than the innodb_page_size value, the innodb_log_write_ahead_size setting is truncated to the innodb_page_size value. Setting the value too high may have a slight impact on fsync ... Consider the following guidelines for optimizing redo logging: Make your redo log files big, even as big as the buffer ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-restrictions.html
CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements are not supported inside transactions, procedures, functions, and triggers when using GTIDs (that is, when the enforce_gtid_consistency system variable is set to ON). For information about ...This section provides information about restrictions on and limitations of replication with ... Because GTID-based replication is ...
https://dev.mysql.com/doc/refman/5.7/en/packet-too-large.html
For example, to set the variable to 16MB, start the server like this: $> mysqld --max_allowed_packet=16M You can also use an option file to set max_allowed_packet. For example, to set the size for the server to 16MB, add the following lines in an ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-innodb-sys-indexes-table.html
For full-text indexes, the PAGE_NO column is unused and set to -1 (FIL_NULL) because the full-text index is laid out in several B-trees (auxiliary tables). The INNODB_SYS_INDEXES table provides metadata about InnoDB indexes, equivalent to the ...
https://dev.mysql.com/doc/refman/5.7/en/stored-routines-syntax.html
For example, to invoke a stored procedure p or function f that is associated with the test database, you can say CALL test.p() or test.f(). A stored procedure or function is associated with a particular database. This has several implications: When ... A stored routine is either a procedure or a ...
https://dev.mysql.com/doc/refman/5.7/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. In this case, attempting to make changes to the database (for InnoDB, MyISAM, or other types of tables) ...A ...Eliminating unnecessary transaction IDs reduces the size of internal data structures that are consulted each time a query or data change statement constructs a read ...
https://dev.mysql.com/doc/refman/5.7/en/myisam-storage-engine.html
Table 15.2 MyISAM Storage Engine Features Feature Support B-tree indexes Yes Backup/point-in-time recovery (Implemented in the server, rather than in the storage engine.) Yes Cluster database support No Clustered indexes No Compressed data Yes ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-table-descriptions.html
Tables in the performance_schema database can be grouped as follows: Setup tables. For example, to set the sizes of the wait event history tables, set performance_schema_events_waits_history_size and ...The events_waits_current table contains the ...These tables have the same structure as the current events tables, but contain more ...
https://dev.mysql.com/doc/refman/5.7/en/audit-log-restrictions.html
Prior to MySQL 5.7.21, MySQL Enterprise Audit uses MyISAM tables in the mysql system database. MySQL Enterprise Audit is subject to these general restrictions: Only SQL statements are logged. Changes made by no-SQL APIs, such as memcached, Node.JS, ...
https://dev.mysql.com/doc/refman/5.7/en/event-scheduler.html
You may also find the MySQL User Forums to be helpful. Section 23.4.3, “Event Syntax”, discusses the SQL statements for creating, altering, and dropping MySQL Events. Section 23.4.4, “Event Metadata”, shows how to obtain information about ...