Does row-based replication with "binlog_row_image=minimal" cause issues when ALTER TABLE reorders columns? Just trying to get my head around the caveats of using binlow_row_image=minimal with row-based replication in MySQL 8.0.23... To avoid silent data drift, the requirements seem to be that:

All tables need a primary key in both databases, which is identical for each pair of tables.
All tables need to have the same number and type of columns, in the correct order, in both databases.

Given the above, if an ALTER TABLE for example deleted a column, could you ever have a race condition where replication of pending binlog events which insert rows into that table would break? Would this only happen if you used something like slave_parallel_workers, or would even that be safe?
I'm trying to figure out if this is worth using or if it's more performance tweak when you don't require hard data consistency.
Parallel replication allows concurrent transactions out of order, but does not allow concurrent non-transactional updates. Certain SQL statements — including DDL statements — cannot be rolled back, so they cause a &quot;barrier&quot; such that they wait until all parallel workers catch up, and workers are blocked from executing changes after the non-transactional change.
This means there's no race condition. DDL effectively forces a kind of &quot;synchronization&quot;.