Hi, Andrei! On Jan 11, Andrei Elkin wrote:

On Tue, Jan 11, 2022 at 1:06 PM Sergei Golubchik <serg@mariadb.org> wrote:

...

Hi, Andrei!

On Jan 11, Andrei Elkin wrote:

...

Howdy, Sergei!

To the question of the usage of trX cache by non-trX let me answer broadly to mention @@binlog_direct_non_transactional_update = false leads to aggregation of mixed, say innodb + myisam, events in trx cache.

That's different. The bug summary is "GTID event falsely marked transactional", meaning, the group of events is not transactional and it's falsely marked as transactional. If you have an innodb/myisam mix, it is correctly marked transactional.

You need to have only non-transactional events in the transactional cache. And I'm trying to understand how can that happen.

Got your very specific point is about a pure myisam can be trx-cached. This is OPTION_BINLOG_GTID commit 5426facdcbfba2d78dab3c709cbf278073383b7c 's decision

...

...

- All tables are regarded as transactional tables in the binary log

(to ensure things are executed exactly as on the master)

Okay, thanks, that answers my question Regards, Sergei VP of MariaDB Server Engineering and security@mariadb.org