Re: How can end users know the cause of LR slot sync delays?

Michael Banck <mbanck@gmx.net>

From: Michael Banck <mbanck@gmx.net>

To: Shlok Kyal <shlok.kyal.oss@gmail.com>

Cc: shveta malik <shveta.malik@gmail.com>, "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Ashutosh Sharma <ashu.coek88@gmail.com>

Date: 2025-11-28T09:29:10Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Rename column slotsync_skip_at to slotsync_last_skip.
- 5db6a344abc2 19 (unreleased) landed
Add slotsync_skip_reason column to pg_replication_slots view.
- e68b6adad96d 19 (unreleased) landed
Fix test failure caused by commit 76b78721ca.
- e3e787ca0234 19 (unreleased) landed
Fix a BF failure caused by commit 76b78721ca.
- 3df4df53b06d 19 (unreleased) landed
Add slotsync skip statistics.
- 76b78721ca49 19 (unreleased) landed

Hi,

On Thu, Nov 27, 2025 at 11:08:00AM +0530, Shlok Kyal wrote:
> I have addressed the comments and attached the updated patch.

Maybe it would be better to break out the slotsync parts of
pg_replication_slots into a new view? I think people are using
pg_replication_slots a lot for monitoring and keeping an eye on
replication and having it much wider makes it somewhat less useful.

Just a suggestion.


Micheal