Re: Unexpected behavior when setting "idle_replication_slot_timeout"

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Nisha Moond <nisha.moond412@gmail.com>, Gunnar Morling <gunnar.morling@googlemail.com>, pgsql-bugs@lists.postgresql.org
Date: 2025-07-05T04:22:33Z
Lists: pgsql-bugs
On Fri, Jul 4, 2025 at 9:37 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> Stepping back a bit, I am not happy with the documentation.  I looked at it,
> trying to figure out what the parameter does, and I am none the wiser.
> What exactly does it mean for a replication slot to idle?
>
> - Does it mean that the standby is not connected?
>

It means the above. The slot is used for purposes other than the
standby as well, so we can't mention something only specific to the
standby. This parameter mainly cares when the slot becomes inactive.
You can get more information by looking at
pg_replication_slots.inactive_since (as indicated by sentence: "The
duration of slot inactivity is calculated using the slot's
pg_replication_slots.inactive_since value.").

>
> I think we could do better here.
>

Sure, feel free to propose what you think makes it better.

-- 
With Regards,
Amit Kapila.



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. doc: Clarify meaning of "idle" in idle_replication_slot_timeout.

  2. Change unit of idle_replication_slot_timeout to seconds.