Re: Mention idle_replication_slot_timeout in pg_replication_slots docs

2025-06-25 Thread Nisha Moond
On Wed, Jun 25, 2025 at 9:56 PM Fujii Masao wrote: > > Hi, > > The pg_replication_slots documentation mentions only max_slot_wal_keep_size > as a condition under which the wal_status column can show unreserved or lost. > However, since commit ac0e33136ab, idle_replication_slot_timeout can also > c

RE: Mention idle_replication_slot_timeout in pg_replication_slots docs

2025-06-25 Thread Hayato Kuroda (Fujitsu)
Dear Fujii-san, > The pg_replication_slots documentation mentions only max_slot_wal_keep_size > as a condition under which the wal_status column can show unreserved or lost. > However, since commit ac0e33136ab, idle_replication_slot_timeout can also > cause this behavior when it is set. This has n

Mention idle_replication_slot_timeout in pg_replication_slots docs

2025-06-25 Thread Fujii Masao
Hi, The pg_replication_slots documentation mentions only max_slot_wal_keep_size as a condition under which the wal_status column can show unreserved or lost. However, since commit ac0e33136ab, idle_replication_slot_timeout can also cause this behavior when it is set. This has not been documented