On Saturday, July 5, 2025, Laurenz Albe <
laurenz.albe@cybertec.at> wrote:
I am sure that there is some information in these sentences, but I cannot
extract it, even after reading them twice.
Maybe: “During checkpoint if the interval since pg_replication_slots.inactive_since and now is larger than this value pg_replication_slots.conflicting is set to true and pg_replication_slots.inactive_reason is set to ‘timeout’. See section wherever for more information on handling conflicted slots.”
Heck, writing this, “idle” is probably better, a slot can recover from being idle on its own but usually inactive would imply having to do something to make it active again.
IMO our documentation for replication has serious flaws but this particular area is clear enough. Like any good timeout the slot is killed if it goes unused “idle” for some length of time. We can describe that in many ways but the name, to me, is fully descriptive and consistent with other timeouts like “idle_in_transaction_timeout”.
David J.
