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

From: Michael Banck <mbanck(at)gmx(dot)net>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(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-28 10:07:30
Message-ID: 20251128100729.GD13635@p46.dedyn.io;lightning.p46.dedyn.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-11-28 10:29:17 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Previous Message Amit Kapila 2025-11-28 10:00:48 Re: How can end users know the cause of LR slot sync delays?