Hi Amit.
IIUC the tablesync worker runs in a single transaction.
Last week I discovered and described [1] a problem where/if (by
unlucky timing) the tablesync worker gets to handle the 2PC PREPARE
TRANSACTION then that whole single tx is getting committed, regardless
that a COMMIT PREPARED was not even been executed yet. i.e. It means
if the publisher subsequently does a ROLLBACK PREPARED then the table
records on Pub/Sub nodes will no longer be matching.
AFAIK this is a new problem for the current WIP patch because prior to
this the PREPARE had no decoding.
Please let me know if this issue description is still not clear.
Did you have any thoughts how we might address this issue?
---
[1] https://www.postgresql.org/message-id/CAHut%2BPuEMk4SO8oGzxc_ftzPkGA8uC-y5qi-KRqHSy_P0i30DA%40mail.gmail.com
Kind Regards,
Peter Smith.
Fujitsu Australia