Re: Fix lag columns in pg_stat_replication not advancing when replay LSN stalls - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Fix lag columns in pg_stat_replication not advancing when replay LSN stalls
Date
Msg-id CAHGQGwHoyCd_Sv7JyqXYd5_Mppccvr9ttH9yoiydDJZ8KVtmnw@mail.gmail.com
Whole thread Raw
In response to Re: Fix lag columns in pg_stat_replication not advancing when replay LSN stalls  (Xuneng Zhou <xunengzhou@gmail.com>)
Responses Re: Fix lag columns in pg_stat_replication not advancing when replay LSN stalls
List pgsql-hackers
On Wed, Oct 22, 2025 at 4:49 PM Xuneng Zhou <xunengzhou@gmail.com> wrote:
> How about something like:
>
> /*
>  * Overflow entries for read heads that collide with the write head.
>  *
>  * When the cyclic buffer fills (write head is about to collide with a read
>  * head), we save that read head's current sample here and mark it as using
>  * overflow (read_heads[i] = -1). This allows the write head to continue
>  * advancing while the overflowed mode continues lag computation using the
>  * saved sample.
>  *
>  * Once the standby's reported LSN advances past the overflow entry's LSN,
>  * we transition back to normal buffer-based tracking.
>  */

LGTM. Thanks!

I've created a patch adding your suggested comments (attached).
Since this is a follow-up to commit 883a95646a8, which was recently applied
and backpatched to all supported branches, I think we should backpatch
this one as well. Thought?

Regards,

--
Fujii Masao

Attachment

pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Skip unregistered custom kinds on stats load
Next
From: "Matheus Alcantara"
Date:
Subject: Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue