# UPDATE\_ROWS\_EVENTs are not in MINIMAL row image format

**URL:** <https://forums.percona.com/t/update-rows-events-are-not-in-minimal-row-image-format/16649>\
**Category:** Percona Server for MySQL 5.7\
**Created:** [July 20, 2022, 10:22am UTC](https://forums.percona.com/t/update-rows-events-are-not-in-minimal-row-image-format/16649 "2022-07-20T10:22:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin\_Vobruba](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/martin_vobruba/32/7015_2.png) [@Martin\_Vobruba](https://forums.percona.com/u/Martin_Vobruba)\
**Post date:** [July 20, 2022, 10:22am UTC](https://forums.percona.com/t/update-rows-events-are-not-in-minimal-row-image-format/16649/1 "2022-07-20T10:22:50Z")

</div>

Hi,

I have 3 master servers (5.7.35-38) and all of them have binlog\_row\_image = MINIMAL. But in binary logs I still see UPDATE\_ROWS\_EVENTs in FULL row image format if they originate from another master.

This is how UPDATE\_ROWS\_EVENTs look like in binary logs (same table, PK present):

On master A:  
UPDATE from master A → MINIMAL row image format  
UPDATE from master B → FULL row image format  
UPDATE from master C → FULL row image format

On master B:  
UPDATE from master A → FULL row image format  
UPDATE from master B → MINIMAL row image format  
UPDATE from master C → FULL row image format

On master C:  
UPDATE from master A → FULL row image format  
UPDATE from master B → FULL row image format  
UPDATE from master C → MINIMAL row image format

Is there any way how to store all UPDATE\_ROWS\_EVENTs in MINIMAL row image format on all master servers?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [July 20, 2022, 2:03pm UTC](https://forums.percona.com/t/update-rows-events-are-not-in-minimal-row-image-format/16649/2 "2022-07-20T14:03:22Z")

</div>

This probably has to do with `log_slave_updates` functionality not going through a proper code path. Have you searched [bugs.mysql.com](http://bugs.mysql.com) for similar reports?

---

<div class="post-metadata">

**Author:** ![Martin\_Vobruba](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/martin_vobruba/32/7015_2.png) [@Martin\_Vobruba](https://forums.percona.com/u/Martin_Vobruba)\
**Post date:** [July 20, 2022, 2:28pm UTC](https://forums.percona.com/t/update-rows-events-are-not-in-minimal-row-image-format/16649/3 "2022-07-20T14:28:25Z")

</div>

Yes, I did and found nothing, but I don’t know at all what to search for. Do you recommend to file this behavior as a bug there?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [July 23, 2022, 7:14pm UTC](https://forums.percona.com/t/update-rows-events-are-not-in-minimal-row-image-format/16649/4 "2022-07-23T19:14:25Z")

</div>

I’m wondering if this is intended behavior. You only see this issue when an event originates from another server, so I’m sure this has something to do with `log_slave_updates` functionality and the potential for a replica to be source for another replica.