There are several modes of binlog in mysql

This article will explain in detail several modes of binlog in mysql. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

1. Statement level mode. Every sql that modifies the data is recorded in the bin-log of master.

When slave is copied, the sql process parses to the same sql that was executed on the original master side and executes again.

The advantages of statement level, first of all, solve the shortcomings of row level, do not need to record the changes of each row of data, reduce the number of bin-log logs, save io, and improve performance. Because he only needs to record the details of the statement executed on the master, as well as the context information when the statement is executed.

2, rowlevel mode, the log will be recorded in the form of each line of data has been modified.

The same data is modified on the slave side. Bin-log does not record the context-sensitive information of the executed sql statement, just record which record was modified and how it was modified. So the contents of row level's log will clearly record the details of each line of data modification. And there is no problem that the calls and triggers of stored procedures, or function, and trigger can not be copied correctly in certain cases.

3. Mixed mode is the combination of the first two modes.

In mixed mode, mysql distinguishes the log form of the record based on each specific sql statement executed, that is, choosing between statement and row.

This is the end of this article on "there are several modes of binlog in mysql". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.