From: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: RE: Mention idle_replication_slot_timeout in pg_replication_slots docs
Date: Thu, 26 Jun 2025 06:43:16 +0000
Message-ID: <OSCPR01MB149667D264CBA6838AEB20648F57AA@OSCPR01MB14966.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <78b34e84-2195-4f28-a151-5d204a382fdd@oss.nttdata.com>
References: <78b34e84-2195-4f28-a151-5d204a382fdd@oss.nttdata.com>
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 not been documented yet.
> https://www.postgresql.org/docs/devel/view-pg-replication-slots.html
Oh, I feel the doc should be also updated.
> 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.
One comment:
```
<para>
<literal>lost</literal> means that some required WAL files have
been removed and this slot is no longer usable.
</para>
```
IIUC, there is a case that status is "lost" but the required WALs have not been
dropped yet if the slot was invalidated due to the timeout. How about removing the
first part:
```
<literal>lost</literal> means that this slot is no longer usable.
```
Best regards,
Hayato Kuroda
FUJITSU LIMITED
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: kuroda.hayato@fujitsu.com, masao.fujii@oss.nttdata.com, pgsql-docs@lists.postgresql.org
Subject: RE: Mention idle_replication_slot_timeout in pg_replication_slots docs
In-Reply-To: <OSCPR01MB149667D264CBA6838AEB20648F57AA@OSCPR01MB14966.jpnprd01.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox