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

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: Michael Banck <mbanck@gmx.net>

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

Date: 2025-12-05T09:10:54Z

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

On Fri, Nov 28, 2025 at 2:59 PM Michael Banck <mbanck@gmx.net> wrote:
>
> 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?
>

We have another view pg_stat_replication_slots, for the statistics of
slots, yet another might not make sense at this stage. If we decide to
have more statistics/monitoring columns for slots that require some
separation, then we can consider moving this one as well.

-- 
With Regards,
Amit Kapila.