Re: Newly created replication slot may be invalidated by checkpoint

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "suyu(dot)cmj" <mengjuan(dot)cmj(at)alibaba-inc(dot)com>, tomas <tomas(at)vondra(dot)me>, michael <michael(at)paquier(dot)xyz>, "bharath(dot)rupireddyforpostgres" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Subject: Re: Newly created replication slot may be invalidated by checkpoint
Date: 2026-01-12 02:57:51
Message-ID: CAA4eK1+aAybMgf4VS1SMr8CtHDveG4gTyyviEmwpOyD1Cxs=7g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 8, 2026 at 10:25 AM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> > However, if required, we can
> > move LogStandbySnapshot() and XLogFlush() outside the loop similar to
> > 16 and above branches. OTOH, doing minimal changes in bank branches
> > and that too in 15 and 14 to fix this issue seems like a prudent
> > choice.
>
> Per my understanding, minimizing the code changes for backbracnhes is more
> important unless it is really needed.
>

Thanks. I pushed this last week.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-01-12 03:30:58 Re: pg_upgrade: optimize replication slot caught-up check
Previous Message Andrew Jackson 2026-01-12 02:50:39 Add ldapservice connection parameter