# Percona - missing rows in binlog, when format is STATEMENT

**URL:** <https://forums.percona.com/t/percona-missing-rows-in-binlog-when-format-is-statement/7418>\
**Category:** Other MySQL® Questions\
**Created:** [February 10, 2020, 1:05pm UTC](https://forums.percona.com/t/percona-missing-rows-in-binlog-when-format-is-statement/7418 "2020-02-10T13:05:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aravind.rrao](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@aravind.rrao](https://forums.percona.com/u/aravind.rrao)\
**Post date:** [February 10, 2020, 1:05pm UTC](https://forums.percona.com/t/percona-missing-rows-in-binlog-when-format-is-statement/7418/1 "2020-02-10T13:05:42Z")

</div>

I am trying to setup replication for my application. I have the binlog format set to STATEMENT and the tx\_isolation set to REPEATABLE-READ. It started with data missing in a couple of tables in the slave database. When I tried to dig further, I noticed that many of the records are inserted into the table in the database but do not have entries in the binlog. The question I have is why they are missing in the binlog?

A couple of other patters I noticed is that when I have multiple rows inserted in the table in the same millisecond, I see only 1 entry in the binlog. The other pattern is that a block of inserts into the database table are missing in the binlog.

I have tried to change the binlog format to MIXED. I still see the issue.

It will be great to find out what I am missing or how to fix this issue.

---

<div class="post-metadata">

**Author:** ![vaibhav\_upadhyay40](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/vaibhav_upadhyay40/32/9_2.png) [@vaibhav\_upadhyay40](https://forums.percona.com/u/vaibhav_upadhyay40)\
**Post date:** [July 3, 2020, 4:40pm UTC](https://forums.percona.com/t/percona-missing-rows-in-binlog-when-format-is-statement/7418/2 "2020-07-03T16:40:45Z")

</div>

Hi @“aravind.rrao”   
entries missing in the Binlog: This is possible in below cases,  
1) when set sql\_log\_bin=0 (session level)–\> insert statement. In this case it will not log to the binlog.  
2) binlog-ignore-db is used. (this is less likely as you have observed some inserts are working and some aren’t)&nbsp;&nbsp;