Book Image

MySQL 8 Cookbook

By : Karthik Appigatla
Book Image

MySQL 8 Cookbook

By: Karthik Appigatla

Overview of this book

MySQL is one of the most popular and widely used relational databases in the World today. The recently released MySQL 8 version promises to be better and more efficient than ever before. This book contains everything you need to know to be the go-to person in your organization when it comes to MySQL. Starting with a quick installation and configuration of your MySQL instance, the book quickly jumps into the querying aspects of MySQL. It shows you the newest improvements in MySQL 8 and gives you hands-on experience in managing high-transaction and real-time datasets. If you've already worked with MySQL before and are looking to migrate your application to MySQL 8, this book will also show you how to do that. The book also contains recipes on efficient MySQL administration, with tips on effective user management, data recovery, security, database monitoring, performance tuning, troubleshooting, and more. With quick solutions to common and not-so-common problems you might encounter while working with MySQL 8, the book contains practical tips and tricks to give you the edge over others in designing, developing, and administering your database effectively.
Table of Contents (20 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Binary log format


Binary logs can be written in three formats:

  1. STATEMENT: Actual SQL statements are logged.
  2. ROW: Changes made to each row are logged. For example, an update statement updates 10 rows, the updated information of all 10 rows is written to the log. Whereas in statement-based replication, only the update statement is written. The default format is ROW.
  3. MIXED: MySQL switches from STATEMENT to ROW as and when needed. 

There are statements that can cause different results when executed on different servers. For example, the output of the UUID() function differs from server to server. Those statements are called non-deterministic and are unsafe for statement-based replication. In those situations, a MySQL server switches to row-based format when you set the MIXED format. 

Refer to https://dev.mysql.com/doc/refman/8.0/en/binary-log-mixed.html to learn more about the unsafe statements and when switching happens.

How to do it...

You can set the format using the dynamic variable, binlog_format...