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/pluggable-authentication-system-variables.html
For example, modifying the LDAP server host, port, or TLS settings does not affect existing connections. For example, modifying the LDAP server host, port, or TLS settings does not affect existing connections. Communication between the ...
https://dev.mysql.com/doc/refman/5.7/en/plugin-loading.html
For example, if the plugin implements a storage engine, existing tables for the storage engine become inaccessible, and attempts to create new tables for the storage engine result in tables that use the default storage engine unless the ... Server ...
https://dev.mysql.com/doc/refman/5.7/en/problems-connecting.html
If you have updated an existing MySQL installation to a newer version, did you perform the MySQL upgrade procedure? If not, do so. Reloading the grant tables affects new client connections, but it also affects existing connections as indicated in ...
https://dev.mysql.com/doc/refman/5.7/en/replace.html
When modifying an existing table that is not partitioned to accommodate partitioning, or, when modifying the partitioning of an already partitioned table, you may consider altering the table's primary key (see Section 22.6.1, “Partitioning Keys, ... REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] {VALUES | VALUE} (value_list) [, (value_list)] ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-directory.html
This can cause problems if no corresponding directory exists in the replica host's file system or if it exists but is not accessible to the replica server. If a DATA DIRECTORY or INDEX DIRECTORY table option is used in a CREATE TABLE statement on ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-failover.html
This poses some challenges when provisioning a new server with data from another existing server. This method has the advantage that a new server is available almost immediately; only those transactions that were committed while the snapshot or dump ... There are a number of techniques when using MySQL Replication with Global Transaction Identifiers (GTIDs) for provisioning a new replica which can then be used for scaleout, being promoted to source as necessary for ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-masterstatus.html
The next step depends on whether you have existing data on the source. Choose one of the following options: If you have existing data that needs be to synchronized with the replica before you start replication, leave the client running so that the ... To configure the replica to start the replication process at the correct point, you need to note the source's current coordinates within its binary ...
https://dev.mysql.com/doc/refman/5.7/en/replication-mode-change-online-enable-gtids.html
Ideally, wait for the server to purge all binary logs that existed when step 6 was completed. After this step, you must be sure that transactions without GTIDs do not exist anywhere in the topology. This section describes how to enable GTID ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-configuration.html
A multi-source replication topology requires at least two sources and one replica configured. In these tutorials, we assume you have two sources source1 and source2, and a replica replicahost. The replica replicates one database from each of the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-monitoring.html
To monitor the status of replication channels the following options exist: Using the replication Performance Schema tables. You can choose to monitor all channels, or a subset of the existing channels. This enables you to write complex queries ...