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/replication-features-blackhole.html
When performing binary logging, all inserts to such tables are always logged, regardless of the logging format in use. The BLACKHOLE storage engine accepts data but discards it and does not store it. Updates and deletes are handled differently ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-limit.html
Statement-based replication of LIMIT clauses in DELETE, UPDATE, and INSERT ... SELECT statements is unsafe since the order of the rows affected is not defined. (Such statements can be replicated correctly with statement-based replication only if ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-max-allowed-packet.html
This means that, when you are replicating large column values using row-based replication, you must take care to set max_allowed_packet large enough to accommodate the largest row in any table to be replicated, even if you are replicating updates ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-triggers.html
(Bug #45677) A trigger can have triggers for different combinations of trigger event (INSERT, UPDATE, DELETE) and action time (BEFORE, AFTER), but before MySQL 5.7.2 cannot have multiple triggers that have the same trigger event and action time.
https://dev.mysql.com/doc/refman/5.7/en/replication-implementation.html
Tables are created or their structure modified, and data is inserted, deleted, and updated according to the changes that were originally made on the source. Replication is based on the replication source server keeping track of all changes to its ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html
This section explains the server options and system variables that apply to replicas and contains the following: Startup Options for Replicas Options for Logging Replica Status to Tables System Variables Used on Replicas Specify the options either ...
https://dev.mysql.com/doc/refman/5.7/en/replication-snapshot-method.html
This can be more efficient than using mysqldump and importing the file on each replica, because it skips the overhead of updating indexes as the INSERT statements are replayed. If the database on the source contains existing data it is necessary to ...
https://dev.mysql.com/doc/refman/5.7/en/revoke.html
For example: REVOKE INSERT ON *.* FROM 'jeffrey'@'localhost'; The host name part of the account name, if omitted, defaults to '%'. The REVOKE statement enables system administrators to revoke privileges from MySQL accounts. For details on the levels ...
https://dev.mysql.com/doc/refman/5.7/en/savepoint.html
(For a new inserted row, the lock information is carried by the transaction ID stored in the row; the lock is not separately stored in memory. SAVEPOINT identifier ROLLBACK [WORK] TO [SAVEPOINT] identifier RELEASE SAVEPOINT identifier InnoDB ...
https://dev.mysql.com/doc/refman/5.7/en/select-optimization.html
Besides SELECT statements, the tuning techniques for queries also apply to constructs such as CREATE TABLE...AS SELECT, INSERT INTO...SELECT, and WHERE clauses in DELETE statements. Queries, in the form of SELECT statements, perform all the lookup ...