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-features-partitioning.html
Replication is supported between partitioned tables as long as they use the same partitioning scheme and otherwise have the same structure except where an exception is specifically allowed (see Section 16.4.1.10, “Replication with Differing Table ...DROP PARTITION) acting directly on partitions in such cases may produce different results on source and ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-source.html
On the source and each replica, you must set the server_id system variable to establish a unique replication ID. If their values have already been modified from the default, Group Replication does not alter them. It is not possible to restrict the ... This section describes the server options and system variables that you can use on replication source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-upgrade.html
Perform any table repair or rebuilding operations needed to re-create database objects, such as use of REPAIR TABLE or ALTER TABLE, or dumping and reloading tables or triggers. Changes affecting operations in strict SQL mode (STRICT_TRANS_TABLES or ... When you upgrade servers that participate in a replication topology, you need to take into account each server's role in the topology and look out for issues specific to ...
https://dev.mysql.com/doc/refman/5.7/en/information-schema.html
INFORMATION_SCHEMA provides access to database metadata, information about the MySQL server such as the name of a database or table, the data type of a column, or access privileges. Other terms that are sometimes used for this information are data ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-disk-data.html
It is possible to store the nonindexed columns of NDB tables on disk, rather than in RAM. As part of implementing NDB Cluster Disk Data work, a number of improvements were made in NDB Cluster for the efficient handling of very large amounts ...
https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb.html
This section explains how to optimize database operations for InnoDB tables. InnoDB is the storage engine that MySQL customers typically use in production databases where reliability and concurrency are important.
https://dev.mysql.com/doc/refman/5.7/en/optimizing-myisam.html
The MyISAM storage engine performs best with read-mostly data or with low-concurrency operations, because table locks limit the ability to perform simultaneous updates. In MySQL, InnoDB is the default storage engine rather than MyISAM.
https://dev.mysql.com/doc/refman/5.7/en/replication-features-invoked.html
You can do this by storing in a separate table the event names from the SELECT statement shown previously, or using ALTER EVENT statements to rename the events with a common prefix such as replicated_ to identify them. The following statements are ... Replication of invoked features such as loadable functions and stored programs (stored procedures and functions, triggers, and events) provides the following characteristics: The effects of the feature are always ...
https://dev.mysql.com/doc/refman/5.7/en/events-metadata.html
Value mysql.event EVENTS Table SHOW EVENTS Execute at UTC ETZ ETZ Starts UTC ETZ ETZ Ends UTC ETZ ETZ Last executed UTC ETZ n/a Created STZ STZ n/a Last altered STZ STZ n/a . To obtain metadata about events: Query the event table of the mysql ...
https://dev.mysql.com/doc/refman/5.7/en/firewall-installation.html
$> mysql -u root -p < linux_install_firewall.sql Enter password: (enter root password here) Note As of MySQL 5.7.21, for a new installation of MySQL Enterprise Firewall, InnoDB is used instead of MyISAM for the firewall tables. MySQL Enterprise ...