Dear Michail, Thanks for pointing out the issue!
>* RelationFindReplTupleByIndex > >Amit, this is why I've included you in this previously solo thread :) >RelationFindReplTupleByIndex uses DirtySnapshot and may not find some records >if they are updated by a parallel transaction. This could lead to lost >deletes/updates, especially in the case of streaming=parallel mode. >I'm not familiar with how parallel workers apply transactions, so maybe this >isn't possible. IIUC, the issue can happen when two concurrent transactions using DirtySnapshot access the same tuples, which is not specific to the parallel apply. Consider that two subscriptions exist and publishers modify the same tuple of the same table. In this case, two workers access the tuple, so one of the changes may be missed by the scenario you said. I feel we do not need special treatments for parallel apply. Best regards, Hayato Kuroda FUJITSU LIMITED
