Re: Allow reading LSN written by walreciever, but not flushed yet - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Allow reading LSN written by walreciever, but not flushed yet
Date
Msg-id 5BBF0BB4-97F6-4787-9FD7-312234CBC7AF@yandex-team.ru
Whole thread Raw
In response to Re: Allow reading LSN written by walreciever, but not flushed yet  (Jeremy Schneider <schneider@ardentperf.com>)
List pgsql-hackers

> On 6 Oct 2025, at 04:42, Jeremy Schneider <schneider@ardentperf.com> wrote:
>
> A large and stressed system could get into a state where fsync takes
> awhile.

For such cases I would like to have a function that ensures walreceiver will not acknowledge any new LSN. And then
returnslast ack'ed LSN. 

Today we have to stop walreceiver, which takes some time from our 9999s.


Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: get rid of RM_HEAP2_ID
Next
From: Xuneng Zhou
Date:
Subject: Re: Improve read_local_xlog_page_guts by replacing polling with latch-based waiting