MIME-Version: 1.0
References: 
 <OS0PR01MB5716BB506AF934376FF3A8BB947BA@OS0PR01MB5716.jpnprd01.prod.outlook.com>
 <CAFiTN-uGkrCDi9kqXJqLB+3ATn_ZULmRER73VhkLSDSAnO8SNg@mail.gmail.com>
 <OSCPR01MB149660EB8A874AC3AE777C658F57BA@OSCPR01MB14966.jpnprd01.prod.outlook.com>
In-Reply-To: 
 <OSCPR01MB149660EB8A874AC3AE777C658F57BA@OSCPR01MB14966.jpnprd01.prod.outlook.com>
From: Dilip Kumar <dilipbalaut@gmail.com>
Date: Wed, 25 Jun 2025 13:55:34 +0530
Message-ID: 
 <CAFiTN-uiVOGwPNmDBPmLnC-86hX9-pKEYH2D_OKUmJd5RAUv=g@mail.gmail.com>
Subject: Re: Slot's restart_lsn may point to removed WAL segment after hard
 restart unexpectedly
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>,
 Alexander Korotkov <aekorotkov@gmail.com>,
	Amit Kapila <amit.kapila16@gmail.com>,
 Vitaly Davydov <v.davydov@postgrespro.ru>,
	Tom Lane <tgl@sss.pgh.pa.us>, Alexander Lakhin <exclusion@gmail.com>,
	pgsql-hackers <pgsql-hackers@postgresql.org>,
 Masahiko Sawada <sawada.mshk@gmail.com>,
	"tomas@vondra.me" <tomas@vondra.me>, vignesh C <vignesh21@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAFiTN-uiVOGwPNmDBPmLnC-86hX9-pKEYH2D_OKUmJd5RAUv%3Dg%40mail.gmail.com>
Precedence: bulk

On Wed, Jun 25, 2025 at 1:18=E2=80=AFPM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> Dear Dilip,
>
> Another idea is to call ReplicationSlotsComputeRequiredLSN() when at leas=
t one
> of the restart_lsn is updated, like attached. I feel this could reduce th=
e computation
> bit more.

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

--=20
Regards,
Dilip Kumar
Google