Horton
Menu

RE: Introduce XID age based replication slot invalidation

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

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

Thanks for re-working the project.

While seeing the old discussion, I found that Robert Haas was agaist the XID-based
invalidation, because it's difficult to determine the cutoff age [1].
Can you clarify your thought against the point? Are you focusing on solving the
wraparound issues, not for bloated instance issue?
The code may not be accepted unless we got his agreement.

[1]: https://www.postgresql.org/message-id/CA+TgmoZTbaaEjSZUG1FL0mzxAdN3qmXksO3O9_PZhEuXTkVnRQ@mail.gmail.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED

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.