Request a Demo
Home   >   mailing lists

Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly
Date
Msg-id CAFiTN-uiVOGwPNmDBPmLnC-86hX9-pKEYH2D_OKUmJd5RAUv=g@mail.gmail.com
Whole thread Raw
In response to RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly  ("Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>)
List pgsql-hackers
Tree view 
On Wed, Jun 25, 2025 at 1:18 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> Dear Dilip,
>
> Another idea is to call ReplicationSlotsComputeRequiredLSN() when at least one
> of the restart_lsn is updated, like attached. I feel this could reduce the computation
> bit more.

Right, that makes sense, if there is nothing updated on disk then we
can avoid computing this.

--
Regards,
Dilip Kumar
Google

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Remove HeapTupleheaderSetXmin{Committed,Invalid} functions
Next
From: Maxim Orlov
Date:
Subject: Re: Issue with custom operator in simple case