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/replication-gtids-concepts.html
In the event of the server stopping unexpectedly, the set of GTIDs from the current binary log file is not saved in the mysql.gtid_executed table. To save space, the MySQL server compresses the mysql.gtid_executed table periodically by replacing ...
https://dev.mysql.com/doc/refman/5.7/en/dynamic-format.html
If a string column has a length of zero after trailing space removal, or a numeric column has a value of zero, it is marked in the bitmap and not saved to disk. Nonempty strings are saved as a length byte plus the string contents. Dynamic storage ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema-events-table.html
The EVENTS table provides information about Event Manager events, which are discussed in Section 23.4, “Using the Event Scheduler”. The EVENTS table has these columns: EVENT_CATALOG The name of the catalog to which the event belongs.
https://dev.mysql.com/doc/refman/5.7/en/innodb-compression-internals.html
This section describes some internal implementation details about compression for InnoDB tables. The information presented here may be helpful in tuning for performance, but is not necessary to know for basic use of compression. Compression ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-basics.html
Generally speaking, when data is saved to disk, it is said that a checkpoint has been reached. NDBCLUSTER (also known as NDB) is an in-memory storage engine offering high-availability and data-persistence features. The NDBCLUSTER storage engine can ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-event-reports.html
By default, the cluster log is saved to a file named ndb_node_id_cluster.log, (where node_id is the node ID of the management server) in the management server's DataDir. Cluster logging information can also be sent to stdout or a syslog facility in ... In this section, we discuss the types of event logs provided by NDB Cluster, and the types of events that are ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-install-configuration.html
The management node needs a config.ini file telling it how many fragment replicas to maintain, how much memory to allocate for data and indexes on each data node, where to find the data nodes, where to save data to disk on each data node, and where ... In this section, we discuss manual configuration of an installed NDB Cluster by creating and editing configuration ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-import.html
--stats Command-Line Format --stats Introduced 5.7.20-ndb-7.6.4 Save information about options related to performance and other internal statistics in files named *.sto and *.stt. ndb_import imports CSV-formatted data, such as that produced by ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-bulk-data-loading.html
SET unique_checks=1; For big tables, this saves a lot of disk I/O because InnoDB can use its change buffer to write secondary index records in a batch. SET foreign_key_checks=1; For big tables, this can save a lot of disk I/O. These performance ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-unexpected-replica-halt.html
This means the replica's record of the current position read from the source's binary log (in the source metadata repository) is never ahead of the record of transactions saved in the relay log. This setting, which is the default, ensures that ...