PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/populating-spatial-columns.html
After you have created spatial columns, you can populate them with spatial data. Values should be stored in internal geometry format, but you can convert them to that format from either Well-Known Text (WKT) or Well-Known Binary (WKB) format. For ...
https://dev.mysql.com/doc/refman/5.7/en/reloading-delimited-text-dumps.html
For backups produced with mysqldump --tab, each table is represented in the output directory by an .sql file containing the CREATE TABLE statement for the table, and a .txt file containing the table data. To reload a table, first change location ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs-relaylog.html
Successive relay log files are created using successive sequence numbers, beginning with 000001. On a Unix system, this can be done as shown here: $> cat new_relay_log_name.index >> old_relay_log_name.index $> mv old_relay_log_name.index ... The ...
https://dev.mysql.com/doc/refman/5.7/en/replica-logs.html
A replica server creates several repositories of information to use for the replication process: The relay log, which is written by the replication I/O thread, contains the transactions read from the replication source server's binary log. The ...
https://dev.mysql.com/doc/refman/5.7/en/replica-sql-thread-states.html
Making temporary file (create) before replaying LOAD DATA INFILE The thread is executing a LOAD DATA statement and is creating a temporary file containing the data from which the replica reads rows. This state can only be encountered if the original ...
https://dev.mysql.com/doc/refman/5.7/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/5.7/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/5.7/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/5.7/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/5.7/en/replication-solutions-unexpected-replica-halt.html
In older MySQL Server versions, this repository could only be created as a file in the data directory that was updated after the transaction had been applied. This creates a risk of losing synchrony with the source depending at which stage of ... In ...