PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/rename-table.html
You must have ALTER and DROP privileges for the original table, and CREATE and INSERT privileges for the new table. RENAME TABLE tbl_name TO new_tbl_name [, tbl_name2 TO new_tbl_name2] ... As of MySQL 8.0.13, you can rename tables locked with a ...
https://dev.mysql.com/doc/refman/8.0/en/repair-table-optimization.html
REPAIR TABLE for MyISAM tables is similar to using myisamchk for repair operations, and some of the same performance optimizations apply: myisamchk has variables that control memory allocation. You may be able to its improve performance by setting ...
https://dev.mysql.com/doc/refman/8.0/en/replace.html
To use REPLACE, you must have both the INSERT and DELETE privileges for the table. REPLACE [LOW_PRIORITY | DELAYED] [INTO] tbl_name [PARTITION (partition_name [, partition_name] ...)] [(col_name [, col_name] ...)] { {VALUES | VALUE} (value_list) [, ...
https://dev.mysql.com/doc/refman/8.0/en/replica-connection-thread-states.html
If the incompatible changes have an impact for you, set the terminology_use_previous system variable to BEFORE_8_0_26 to make MySQL Server use the old versions of the names for the objects specified in the previous list. These thread states occur ...
https://dev.mysql.com/doc/refman/8.0/en/replica-sql-thread-states.html
If the incompatible changes have an impact for you, set the terminology_use_previous system variable to BEFORE_8_0_26 to make MySQL Server use the old versions of the names for the objects specified in the previous list. The following list shows ...
https://dev.mysql.com/doc/refman/8.0/en/replication-asynchronous-connection-failover-source.html
If multiple sources have the same weight, the replica orders them randomly. To activate asynchronous connection failover for a replication channel set SOURCE_CONNECTION_AUTO_FAILOVER=1 on the CHANGE REPLICATION SOURCE TO statement (from MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption.html
When binary log files have been encrypted, mysqlbinlog cannot read them directly, but can read them from the server using the --read-from-remote-server option. From MySQL 8.0.14, binary log files and relay log files can be encrypted, helping to ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-blackhole.html
For this reason we recommend when you replicate to tables using the BLACKHOLE storage engine that you have the binlog_format server variable set to STATEMENT, and not to either ROW or MIXED. The BLACKHOLE storage engine accepts data but discards it ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-functions.html
For this reason, if you select from the replica's copy of mytable after the CREATE TABLE and INSERT statements just shown have been replicated, you might expect mycol to contain the value 2009-09-01 18:00:00. Certain functions do not replicate well ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-limit.html
When using STATEMENT mode, warnings are issued for DML statements containing LIMIT even when they also have an ORDER BY clause (and so are made deterministic). Statement-based replication of LIMIT clauses in DELETE, UPDATE, and INSERT ... SELECT ...