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/replication-features-invoked.html
For example, trying to replicate a loadable function with statement-based replication generates this warning because it currently cannot be determined by the MySQL server whether the function is deterministic. In the case of CREATE EVENT and ALTER ... 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/replication-features.html
If you are planning to use statement-based replication between MySQL 5.7 and a previous MySQL release series, it is a good idea to consult the edition of the MySQL Reference Manual corresponding to the earlier release series for information ... The ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-masterstatus.html
Warning This procedure uses FLUSH TABLES WITH READ LOCK, which blocks COMMIT operations for InnoDB tables. If you are planning to shut down the source to create a data snapshot, you can optionally skip this procedure and instead store a copy of 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-problems.html
Many users have lost time by not doing this soon enough after encountering problems. This should never happen if you have taken a proper snapshot of the source, and never modified the data on the replica outside of the replication threads. If the ...
https://dev.mysql.com/doc/refman/5.7/en/replication-upgrade.html
In this way you will never be in the situation where a replica still at the earlier release is attempting to handle transactions from a source at the later release. This restriction applies not only to release series, but to version numbers within ... 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/resetting-permissions.html
If you start the server manually, use whatever command you normally use. Alternatively, you can log in as root, but in this case you must start mysqld with the --user=mysql option. The exact location and name of this file depend on your ... If you ...
https://dev.mysql.com/doc/refman/5.7/en/server-system-variable-reference.html
This option is dynamic, but should be set only by server. The following table lists all system variables applicable within mysqld. The table lists command-line options (Cmd-line), options valid in configuration files (Option file), server system ...
https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html
When this manual refers to “strict mode,” it means a mode with either or both STRICT_TRANS_TABLES or STRICT_ALL_TABLES enabled. This makes it easier to use MySQL in different environments and to use MySQL together with other database servers.
https://dev.mysql.com/doc/refman/5.7/en/updating-direct-rpms.html
In this case, you must restart the server manually after the upgrade. It is preferable to use the MySQL Yum repository or MySQL SLES Repository to upgrade MySQL on RPM-based platforms. For an upgrade installation using RPM packages, the MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previous-series.html
Before upgrading to MySQL 5.7, review the changes described in this section to identify those that apply to your current MySQL installation and applications. Sometimes this involves dumping and reloading tables, or use of a statement such as CHECK ...Changes marked as Incompatible change are incompatibilities with earlier versions of MySQL, and may require your attention before ...