Re: Introduce XID age based replication slot invalidation

Hi,

On Wed, Aug 19, 2026 at 4:09 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> > > Additionally, for synced slots, we could add a LOG/WARNING when they
> > > are nearing invalidation as there are no direct consumers for the
> > > same.
> >
> > That's an interesting idea. I see this as useful not just for XID-age
> > based invalidation but for slot invalidation in general. Having some
> > warning before a slot gets invalidated, something like when the
> > database approaches XID wraparound limits, whether built into core or
> > via a documented SQL query, would be nice to have. It's worth
> > discussing separately.
> >
> I thought for synced slots, it is important as there is no active
> consumer for them.

Understood. Even though synced slots show up in pg_replication_slots
on the standby, I agree it's worth adding early warnings before they
get invalidated. I will try to discuss this separately since the idea
applies to synced slot invalidation in general, not just the XID-age
based one.

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