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/query-log.html
Server restarts and log flushing do not cause a new general query log file to be generated (although flushing closes and reopens it). The general query log is a general record of what mysqld is doing. The server writes information to this log when ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-skip.html
If the failing transaction generated an error in a worker thread, you can obtain its GTID directly from the APPLYING_TRANSACTION field in the Performance Schema table replication_applier_status_by_worker. If replication stops due to an issue with ...
https://dev.mysql.com/doc/refman/5.7/en/replication-channels.html
The error codes and messages that are issued when multi-source replication is enabled specify the channel that generated the error. In MySQL multi-source replication, a replica opens multiple replication channels, one for each replication source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-delayed.html
MySQL 5.7 supports delayed replication such that a replica server deliberately lags behind the source by at least a specified amount of time. Use the MASTER_DELAY option for CHANGE MASTER TO to set the delay to N seconds: CHANGE MASTER TO ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-memory.html
This generated event is identifiable by a comment in the binary log, and if GTIDs are in use on the server, it has a GTID assigned. When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html
Client transactions are guaranteed to have monotonically increasing GTIDs without gaps between the generated numbers. A global transaction identifier (GTID) is a unique identifier created and associated with each transaction committed on the server ...
https://dev.mysql.com/doc/refman/5.7/en/replication-setup-replicas.html
If you are setting up a new replication environment using the data from a different existing database server to create a new source, run the dump file generated from that server on the new source. Before you proceed, ensure that you have: Configured ...
https://dev.mysql.com/doc/refman/5.7/en/reset-master.html
After verifying the setup, resetting the source and replica and ensuring that no unwanted data or binary log files generated by testing remain on source or replica, you can start the replica and begin replicating. RESET MASTER Warning Use this ...
https://dev.mysql.com/doc/refman/5.7/en/security-against-attack.html
To make FILE-privilege operations a bit safer, files generated with SELECT ... When you connect to a MySQL server, you should use a password. Password handling during the client connection sequence was upgraded in MySQL 4.1.1 to be very secure. If ...
https://dev.mysql.com/doc/refman/5.7/en/security-guidelines.html
That does not mean the combination needs to be a random string of characters that is difficult to remember and reproduce, although this is a good approach if you have, for example, password manager software that can generate and fill such passwords ... Anyone using MySQL on a computer connected to the Internet should read this section to avoid the most common security ...