On Tuesday, August 5, 2025 10:09 AM Zhijie Hou (Fujitsu) <houzj.f...@fujitsu.com> wrote: > Here is V57 patch set which addressed most of comments. > > In this version, I also fixed a bug that the apply worker continued to find > dead > tuples even if it has already stop retaining dead tuples.
Here is a V58 patch set which improved few things by internal review: 0001: * Remove the slot invalidation. Initially, we thought it would be convenient for users to determine if they can reliably detect update_deleted by checking the validity of the conflict detection slot. However, after re-thinking, even if the slot is valid, it doesn't guarantee that each apply worker can reliably detect conflicts. Some apply workers might have stopped retention, yet the slot remains valid due to other active workers continuing retention. Instead of querying the slot, users should verify the ability of a specific apply worker to reliably detect conflicts by checking the view pg_stat_subscription.retain_dead_tuples. So, slot invalidation would be necessary. We could set slot.xmin to invalid instead to allow dead tuples to be removed when all apply workers stop retention. This approach simplifies implementation and avoids introducing a new invalidation type solely for one internal slot. * Fixed a bug that parallel apply worker continues to search dead tuples when the retention has already stopped. The parallel and table sync worker referred to its own stop_conflict_info_retention flag, but should refer to the retention flag of the leader instead because only leader mananges this flag. 0002: * Allow the apply worker to wait for the slot to be recover after resuming the dead tuple retention instead of restarting the apply worker. Best Regards, Hou zj
v58-0002-Resume-retaining-the-information-for-conflict-de.patch
Description: v58-0002-Resume-retaining-the-information-for-conflict-de.patch
v58-0001-Introduce-a-new-GUC-max_conflict_retention_durat.patch
Description: v58-0001-Introduce-a-new-GUC-max_conflict_retention_durat.patch
