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: Amit Kapila <amit.kapila16@gmail.com>

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

Date: 2025-11-28T10:07:30Z

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 Fri, Nov 28, 2025 at 03:30:48PM +0530, Amit Kapila wrote:
> I suggested the current one because having the last was making the
> column name bit longer, and anyway the description clarifies it, but I
> see your point. So, the other options could be
> slotsync_last_skip_time, sync_last_skip_time, last_slotsync_skip_time,
> last_sync_skip_time . 

I also noticed while going through src/backend/catalog/system_views.sql
that *_last_*_time is rare, so in terms of brevity, removing the _time
at the end would be ok. "last_" already conveys time/a timestamp.

Michael