On Friday, April 10, 2026 5:53 PM Amit Kapila <[email protected]> wrote: > On Fri, Apr 10, 2026 at 8:28 AM Zhijie Hou (Fujitsu) <[email protected]> > wrote: > > > > > > Perhaps we could simply compare the slot's old and new LSN/xmin to > > determine whether updated_xmin_or_lsn needs to be set. > > > > The patch works for me. Can we change the comment to as follows: "It is > possible that the slot's xmin or LSNs are not updated, when the synced slot > has reached consistent snapshot state or cannot build the one at all."?
Changed as suggested. Here are the patches for both HEAD and back branches. Best Regards, Hou zj
v4-0001-Fix-slotsync-worker-busy-loop-causing-repeated-lo.patch
Description: v4-0001-Fix-slotsync-worker-busy-loop-causing-repeated-lo.patch
v4_PG17_18-0001-Fix-slotsync-worker-busy-loop-causing-rep.patch
Description: v4_PG17_18-0001-Fix-slotsync-worker-busy-loop-causing-rep.patch
