I have a question about a blog

regarding blog

Chasing a Hung MySQL Transaction: InnoDB History Length Strikes Back - Percona Database Performance Blog

I. changed the transaction level isolation to READ COMMITED instead of repeatable read to reduce innodb history list length . But it resulted in customer service outage as our binary logging was statement and some inserts were failing

What is your question?

The documentation states

MySQL :: MySQL 5.6 Reference Manual :: Setting The Binary Log Format

“If you are using InnoDB tables and the transaction isolation level is READ COMMITTED or READ UNCOMMITTED, only row-based logging can be used. It is possible to change the logging format to STATEMENT, but doing so at runtime leads very rapidly to errors because InnoDB can no longer perform inserts.”

Thank you Vadim. My question got answered.