Hi
On Thursday, February 25, 2021 4:02 PM Peter Smith <smithpb2...@gmail.com> > Please find attached the latest patch set v43* > > - Added new patch 0007 "Fix apply worker prepare" as discussed here [2] > > [2] > https://www.postgresql.org/message-id/CAA4eK1L%3DdhuCRvyDvrXX5wZ > gc7s1hLRD29CKCK6oaHtVCPgiFA%40mail.gmail.com I tested the scenario that we resulted in skipping prepared transaction data and the replica became out of sync, which was described in [2]. And, as you said, the problem is addressed in v43. I used twophase_snapshot.spec as a reference for the flow (e.g. how to make a consistent snapshot between prepare and commit prepared) and this time, as an alternative of the SQL API(pg_create_logical_replication_slot), I issued CREATE SUBSCRIPTION, and other than that, I followed other flows in the spec file mainly. I checked that the replica has the same data at the end of this test, which means the mechanism of spoolfile works. Best Regards, Takamichi Osumi
