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/stored-programs-logging.html
Mixed format binary logging (binlog_format=MIXED) uses statement-based binary logging, except for cases where only row-based binary logging is guaranteed to lead to proper results. When you attempt to execute a stored function, if ... The binary log ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-lifecycle.html
Temporary tables are dropped automatically when a replica begins to apply events from a source that has just been started, and when statement-based replication is in use (binlog_format=STATEMENT) and a user session that has open temporary tables ...
https://dev.mysql.com/doc/refman/5.7/en/replication-formats.html
The logging format in a running MySQL server is controlled by setting the binlog_format server system variable. Changing the global binlog_format value requires privileges sufficient to set global system variables. Changing the session binlog_format ... Replication works because events written to the binary log are read from the source and then processed on the ...
https://dev.mysql.com/doc/refman/5.7/en/miscellaneous-functions.html
A warning is logged if you use this function when binlog_format is set to STATEMENT. A warning is logged if you use this function when binlog_format is set to STATEMENT. A warning is logged if you use this function when binlog_format is set to ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-temptables.html
The discussion in the following paragraphs does not apply when binlog_format=ROW because, in that case, temporary tables are not replicated; this means that there are never any temporary tables on the replica to be lost in the event of an unplanned ...The remainder of this section applies only when using statement-based or mixed-format ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-adding-instances.html
Create the configuration file [mysqld] # # Disable other storage engines # disabled_storage_engines="MyISAM,BLACKHOLE,FEDERATED,ARCHIVE,MEMORY" # # Replication configuration parameters # server_id=3 gtid_mode=ON enforce_gtid_consistency=ON ... At ...
https://dev.mysql.com/doc/refman/5.7/en/faqs-replication.html
How do I tell whether a replication source server is using statement-based or row-based binary logging format? Check the value of the binlog_format system variable: mysql> SHOW VARIABLES LIKE 'binlog_format'; The value shown is always one of ... In ...
https://dev.mysql.com/doc/refman/5.7/en/replication-upgrade.html
If you use statement-based logging (binlog_format=STATEMENT), if a replica is upgraded before the source, the source executes statements which succeed there but which may fail on the replica and so cause replication to stop. Alternatively, if you ...
https://dev.mysql.com/doc/refman/5.7/en/replication-features-load-data.html
When binlog_format=MIXED is set, the statement is logged in row-based format. When binlog_format=STATEMENT is set, note that LOAD DATA does not generate a warning, unlike other unsafe statements. LOAD DATA is considered unsafe for statement-based ...
https://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previous-series.html
A resulting incompatibility for replication if you use statement-based logging (binlog_format=STATEMENT) is that if a replica is upgraded, a source which has not been upgraded executes the preceding example without error, whereas the INSERT fails on ... Before upgrading to MySQL 5.7, review the changes described in this section to identify those that apply to your current MySQL installation and ...