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

From: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Subject: Re: How can end users know the cause of LR slot sync delays?
Date: 2025-11-27 05:38:00
Message-ID: CANhcyEWwTGHfsWiUtaoko_GX=_iLrSKmLEAOU6q4hqYtSmtNwQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 27 Nov 2025 at 10:42, shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> On Thu, Nov 27, 2025 at 9:25 AM Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> wrote:
> >
> > I have made some minor changes in documentation and comments. Attached
> > the updated patch.
> >
>
> 1)
> <literal>NULL</literal> if
> slot synchronization is successful.
>
> We shall add 'It is' to maintain continuity as the previous sentence has it.
>
> 2)
> Related to previous patch: pgstat_report_replslotsync() currently has
> sanity check Assert(SlotIsLogical(slot));
> Instead, shall we have Assert(slot->synced)? It will implicitly ensure
> that the slot is logical, plus it is important to check that we are
> updating stats of synced slot only.
>
Hi Shveta,

I have addressed the comments and attached the updated patch.

Thanks,
Shlok Kyal

Attachment Content-Type Size
v16-0001-Add-slotsync_skip_reason-to-pg_replication_slots.patch application/octet-stream 16.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2025-11-27 05:48:11 Re: Support tid range scan in parallel?
Previous Message Michael Paquier 2025-11-27 05:18:29 Re: Consistently use palloc_object() and palloc_array()