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

From: shveta malik <shveta(dot)malik(at)gmail(dot)com>
To: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
Cc: "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>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: How can end users know the cause of LR slot sync delays?
Date: 2025-11-03 09:44:10
Message-ID: CAJpy0uByLfSyP0XDGFoF+VjiiErFrcFCpeMoy5B2m5ifU4iadA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> I have attached the latest patch.
>

Thanks. I have started going through it.

I’m not sure if this has already been discussed; I couldn’t find any
mention of it in the thread. Why don’t we persist
'slot_sync_skip_reason' (it is outside of
ReplicationSlotPersistentData)? If a slot wasn’t synced during the
last cycle and the server restarts, it would be helpful to know the
reason it wasn’t synced prior to the node restart.

thanks
Shveta

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ocean_li_996 2025-11-03 09:49:35 Re: [PATCH] Add a guc parameter to control limit clause adjust path cost.
Previous Message Jim Jones 2025-11-03 08:41:45 Re: [PoC] XMLCast (SQL/XML X025)