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/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/replace-utility.html
< file_name from represents a string to look for and to represents its replacement. In this case, any file named on the command line is modified in place, so you may want to make a copy of the original before converting it. For example, the ... The ...
https://dev.mysql.com/doc/refman/5.7/en/replication-administration-pausing.html
This makes it easier for the replica to catch up when you restart the replication SQL thread. This can be useful when you want to pause execution to catch up with events already received from the source, when you want to perform administration on ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-auto-increment.html
(Bug #45677) An INSERT into a table that has a composite primary key that includes an AUTO_INCREMENT column that is not the first column of this composite key is not safe for statement-based logging or replication. This occurs because the order in ... Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID(), and TIMESTAMP values is done correctly, subject to the following exceptions: When using statement-based replication prior to MySQL 5.7.1, AUTO_INCREMENT columns in tables on the replica must match the same columns on the source; that is, AUTO_INCREMENT columns must be replicated to AUTO_INCREMENT ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-fractional-seconds.html
MySQL 5.7 permits fractional seconds for TIME, DATETIME, and TIMESTAMP values, with up to microseconds (6 digits) precision. There may be problems replicating from a source server that understands fractional seconds to an older replica (MySQL 5.6.3 ...Statements that use temporal data types with an fsp value of 0 work with statement-based logging but not row-based ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-limit.html
(Such statements can be replicated correctly with statement-based replication only if they also contain an ORDER BY clause.) When such a statement is encountered: When using STATEMENT mode, a warning that the statement is not safe for ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-optimizer.html
It is possible for the data on the source and replica to become different if a statement is written in such a way that the data modification is nondeterministic; that is, left up the query optimizer. (In general, this is not a good practice, even ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-repair-table.html
When used on a corrupted or otherwise damaged table, it is possible for the REPAIR TABLE statement to delete rows that cannot be recovered. However, any such modifications of table data performed by this statement are not replicated, which can ...
https://dev.mysql.com/doc/refman/5.7/en/se-csv-repair.html
When running the CHECK TABLE statement, the CSV file is checked for validity by looking for the correct field separators, escaped fields (matching or missing quotation marks), the correct number of fields compared to the table definition and the ...
https://dev.mysql.com/doc/refman/5.7/en/selinux-policies.html
MySQL Server SELinux policy modules include: mysqld_selinux mysqld_safe_selinux For information about MySQL Server SELinux policy modules, refer to the SELinux manual pages. The manual pages provide information about types and Booleans associated ...