Re: How can end users know the cause of LR slot sync delays?
Shlok Kyal <shlok.kyal.oss@gmail.com>
From: Shlok Kyal <shlok.kyal.oss@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>,
Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Ashutosh Sharma <ashu.coek88@gmail.com>,
shveta malik <shveta.malik@gmail.com>
Date: 2025-11-26T04:00:15Z
Lists: pgsql-hackers
Attachments
- v12-0001-Add-slotsync_skip_reason-to-pg_replication_slots.patch (application/octet-stream)
On Wed, 26 Nov 2025 at 09:00, Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > Dear Hou, > > > I think we did not sync slots to standby2, so I removed the checks for that. > > > > I also adjusted the test in a way that it cleans up existing slots before starting > > new tests. > > Thanks for updating the patch. I confirmed on my env that your patch could be > applied cleanly and tests were passed. Pgperltidy say nothing for your patch. > Also, I preferred the current style. > > I think it is worth checking on BF to see how they say. > Thanks Amit for pushing the 0001 patch. Thanks Hou-san and Kuroda-san on fixing the test. I have rebased the 0002 patch on the current HEAD. Thanks, Shlok Kyal