| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Mention idle_replication_slot_timeout in pg_replication_slots docs |
| Date: | 2025-06-25 16:25:56 |
| Message-ID: | 78b34e84-2195-4f28-a151-5d204a382fdd@oss.nttdata.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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 yet.
https://www.postgresql.org/docs/devel/view-pg-replication-slots.html
So, how about updating the documentation to also mention
idle_replication_slot_timeout as a factor that can cause wal_status to
become unreserved or lost? Patch attached.
Regards,
--
Fujii Masao
NTT DATA Japan Corporation
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-doc-Mention-idle_replication_slot_timeout-in-pg_r.patch | text/plain | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2025-06-26 06:43:16 | RE: Mention idle_replication_slot_timeout in pg_replication_slots docs |
| Previous Message | Fujii Masao | 2025-06-25 00:06:35 | Re: Minor documentation fixes related to v18 |