Search



Search Results
Displaying 2971 to 2980 of 3565 total results
https://dev.mysql.com/doc/refman/8.4/en/replication-features-charset.html
The following applies to replication between MySQL servers that use different character sets: If the source has databases with a character set different from the global character_set_server value, you should design your CREATE TABLE statements so ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-masterstatus.html
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 binary log index file along with the data snapshot. In that situation, the source creates a new binary log ... 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/8.4/en/replication-rules-channel-based-filters.html
The syntax to create channel specific replication filters extends the existing SQL statements and command options. The default replication channel is the replication channel which always exists once replication has been started, and differs from ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules-db-options.html
Important For statement-based logging, an exception is made in the rules just given for the CREATE DATABASE, ALTER DATABASE, and DROP DATABASE statements. In those cases, the database being created, altered, or dropped replaces the default database ... When evaluating replication options, the replica begins by checking to see whether there are any --replicate-do-db or --replicate-ignore-db options that ...
https://dev.mysql.com/doc/refman/8.4/en/replication-rules.html
The rules governing such filters are the same whether they are created on startup using --replicate-* options or while the replica server is running by CHANGE REPLICATION FILTER. For statements affecting databases only (that is, CREATE DATABASE, ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-performance.html
Also, as each replica must receive a full copy of the source's binary log, the network load on the source may also increase and create a bottleneck. One way to improve the performance of the replication process is to create a deeper replication ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-unexpected-replica-halt.html
This repository is created by default as an InnoDB table named mysql.slave_relay_log_info. This creates a risk of losing synchrony with the source depending at which stage of processing a transaction the replica halts at, or even corruption of the ... In order for replication to be resilient to unexpected halts of the server (sometimes described as crash-safe) it must be possible for the replica to recover its state before ...
https://dev.mysql.com/doc/refman/8.4/en/replication.html
Analytics - live data can be created on the source, while the analysis of the information can take place on the replica without affecting the performance of the source. Long-distance data distribution - you can use replication to create a local copy ... Replication enables data from one MySQL database server (known as a source) to be copied to one or more MySQL database servers (known as ...
https://dev.mysql.com/doc/refman/8.4/en/reset-binary-logs-and-gtids.html
A new empty binary log file is created so that binary logging can be restarted. Issuing RESET BINARY LOGS AND GTIDS without the optional TO clause deletes all binary log files listed in the index file, resets the binary log index file to be empty, ... Note This statement takes the place of the old RESET MASTER statement, which is no longer ...
https://dev.mysql.com/doc/refman/8.4/en/reusing-ssl-sessions.html
Server-Side Runtime Configuration and Monitoring for SSL Session Reuse To create the initial TLS context, the server uses the values that the context-related system variables have at startup. To suppress the error message, and to establish the ...
Displaying 2971 to 2980 of 3565 total results