PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.3Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/group-replication-use-cases.html
It is important to understand that although the database service is available, in the event of an unexpected server exit, those clients connected to it must be redirected, or failed over, to a different server. Group Replication enables you to ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-view-changes.html
This section explains the process which controls how the view change identifier is incorporated into a binary log event and written to the log, The following steps are taken: Begin: Stable Group All servers are online and processing incoming ...
https://dev.mysql.com/doc/refman/5.7/en/gtid-functions.html
It is important to keep in mind that all of these functions take string representations of GTID sets as arguments. The functions described in this section are used with GTID-based replication. As such, the GTID sets must always be quoted when used ...
https://dev.mysql.com/doc/refman/5.7/en/index-statistics.html
For optimizer purposes, an important statistic is the average value group size. Storage engines collect statistics about tables for use by the optimizer. Table statistics are based on value groups, where a value group is a set of rows with the same ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-auto-increment-handling.html
There is no change in semantics compared to “traditional” mode for any statement that uses auto-increment, with one important exception. InnoDB provides a configurable locking mechanism that can significantly improve scalability and performance ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-flushing.html
When setting a high value it is important to ensure that redo log utilization does not reach 75% (the hardcoded limit at which asynchronous flushing starts), and that the innodb_max_dirty_pages_pct threshold keeps the number of dirty pages to a ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool-optimization.html
Knowing how the InnoDB buffer pool works, and taking advantage of it to keep frequently accessed data in memory, is an important aspect of MySQL tuning. InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory.
https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool.html
Knowing how to take advantage of the buffer pool to keep frequently accessed data in memory is an important aspect of MySQL tuning. The buffer pool is an area in main memory where InnoDB caches table and index data as it is accessed. The buffer ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-internals.html
It is important to minimize the number of times B-tree nodes are split, as well as to minimize the need to uncompress and recompress their content. This section describes some internal implementation details about compression for InnoDB tables. The ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-tuning.html
For some environments, the time it takes to load data can be as important as run-time retrieval. Most often, the internal optimizations described in InnoDB Data Storage and Compression ensure that the system runs well with compressed data. However, ...