Re: Newly created replication slot may be invalidated by checkpoint - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Newly created replication slot may be invalidated by checkpoint
Date
Msg-id CAA4eK1KHObZ-giSMwrTchtvjXs8yj0sQw9Jt-x2M9Nqxapkjvg@mail.gmail.com
Whole thread Raw
In response to Re: Newly created replication slot may be invalidated by checkpoint  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
On Mon, Jan 26, 2026 at 3:06 PM Chao Li <li.evan.chao@gmail.com> wrote:
>
> > On Jan 26, 2026, at 13:35, Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote:
> >
> > Dear Hou,
> >
> > Thanks for updating the patch. I ran tests and reproducer [1] for all versions.
> > Confirmed the issue happened before the patch and fixed after applying them.
> >
> > One difference between master and others is that pg_sync_replication_slots()
> > on HEAD is not returned. Because the behavior was changed by 0d2d4a0, not
> > related with the fix.
> >
> > I feel these patches are enough good shape.
> >
> > [1]:
https://www.postgresql.org/message-id/TY7PR01MB14554DBE84290130EB421DD28F596A%40TY7PR01MB14554.jpnprd01.prod.outlook.com
> >
> > Best regards,
> > Hayato Kuroda
> > FUJITSU LIMITED
> >
>
> Yeah, I agree v4 is solid. I have a few nitpicks:
>

Pushed after minor cosmetic changes.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: tablecmds: reject CLUSTER ON for partitioned tables earlier
Next
From: Corey Huinker
Date:
Subject: Re: Extended Statistics set/restore/clear functions.