Horton
Menu

Re: Introduce XID age based replication slot invalidation

Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>

View thread
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Srinath Reddy Sadipiralla <srinath2133@gmail.com>, SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, John H <johnhyvr@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-04-06T02:52:07Z
Lists: pgsql-hackers 
Hi,

On Sun, Apr 5, 2026 at 1:03 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> Thank you for updating the patch!
>
> I've made some changes including moving MaybeInvalidateXidAgedSlot()
> to vacuum.c since the function seems more inherently tied to vacuum
> context. Also, updated the commit message and fixed typos.
>
> Please review the attached patch.

Thank you Sawada-san!

I took a look at the v10 patch and it LGTM. I tested it - make
check-world passes, pgindent doesn't complain.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix the handling of two GUCs during upgrade.