MySQL Forums
Forum List  »  Docs

Discrepancy in sync_binlog parameter documentation
Posted by: Ashu Sharma
Date: September 07, 2016 08:18AM

Hello Team, I was going through the documentation for sync_binlog parameter and found a discrepancy in sync_binlog parameter documentation.

The documentation here says:

A value of 1 is the safest choice because in the event of a crash you lose at most one commit group from the binary log.

which essentially means that the data will be updated but might not be there in the binlogs.

However,in the binary log documentation here says:

For example, if you are using InnoDB tables and the MySQL server processes a COMMIT statement, it writes many prepared transactions to the binary log in sequence, synchronizes the binary log, and then commits this transaction into InnoDB. If the server crashes between those two operations, the transaction is rolled back by InnoDB at restart but still exists in the binary log.

which essentially means that the transaction is first written in binlog and then committed to the InnoDB, so there is a chance that in case of crash the row is there in the binlog but doesn;t exist in the Database.

Can some-one please comment on which information is correct.

Appreciate your help.

Options: ReplyQuote

Written By
Discrepancy in sync_binlog parameter documentation
September 07, 2016 08:18AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.