On Monday, December 15, 2025 7:06 PM Amit Kapila <[email protected]> wrote: > > On Fri, Dec 12, 2025 at 8:53 AM shveta malik <[email protected]> > wrote: > > > > On Fri, Dec 12, 2025 at 5:35 AM Ajin Cherian <[email protected]> wrote: > > > > > > > > > I have included these changes as well as comments by Chao. Attaching > > > v37 with the changes. > > > > > > > Thanks. v37 LGTM. > > > > Pushed.
My college reported a related BF failure[1] to me off-list. After analyzing, I think the issue is that the newly added test in 040_standby_failover_slots_sync synchronizes a replication slot to the standby server without configuring synchronized_standby_slots. This omission allows logical failover slots to advance beyond the designated physical replication slot, resulting in intermittent synchronization failures. I confirmed the same from the log where the slotsync failed due to the reason mentioned above: -- 2025-12-15 12:30:33.502 CET [3015371][client backend][1/2:0] ERROR: skipping slot synchronization because the received slot sync LSN 0/06017C90 for slot "lsub1_slot" is ahead of the standby position 0/06017C58 2025-12-15 12:30:33.502 CET [3015371][client backend][1/2:0] STATEMENT: SELECT pg_sync_replication_slots(); -- Here is a small patch to fix it. [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=serinus&dt=2025-12-15%2011%3A25%3A38 Best Regards, Hou zj
v1-0001-Fix-an-intermittent-BF-failure.patch
Description: v1-0001-Fix-an-intermittent-BF-failure.patch
