From 7bccb16c1119e00194939dfe154d1aa0e8d19842 Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Thu, 26 Jun 2025 00:55:46 +0900 Subject: [PATCH v1] doc: Mention idle_replication_slot_timeout in pg_replication_slots docs. The pg_replication_slots documentation previously mentioned 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 was not documented. This commit updates the documentation to also mention idle_replication_slot_timeout as a factor that can cause wal_status to become unreserved or lost. --- doc/src/sgml/system-views.sgml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/system-views.sgml b/doc/src/sgml/system-views.sgml index 986ae1f543d..f97da9f7e61 100644 --- a/doc/src/sgml/system-views.sgml +++ b/doc/src/sgml/system-views.sgml @@ -2832,8 +2832,9 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx The last two states are seen only when is - non-negative. If restart_lsn is NULL, this - field is null. + non-negative and/or + is greater than zero. If restart_lsn is NULL, + this field is null. -- 2.49.0