From 95a604eaebd145729d9f8c936b37703a212f27fd Mon Sep 17 00:00:00 2001 From: Fujii Masao Date: Fri, 3 Jul 2020 12:08:35 +0900 Subject: [PATCH] doc: Correct description of restart_lsn in pg_replication_slots Previously the document explained that restart_lsn indicates the LSN of oldest WAL won't be automatically removed during checkpoints. But since v13 this was no longer true thanks to max_slot_wal_keep_size. Back-patch to v13 where max_slot_wal_keep_size was added. Author: Fujii Masao Discussion: https://postgr.es/m/6497f1e9-3148-c5da-7e49-b2fddad9a42f@oss.nttdata.com --- doc/src/sgml/catalogs.sgml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 8945959f9d2..198ed62e96f 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -11214,7 +11214,9 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx The address (LSN) of oldest WAL which still might be required by the consumer of this slot and thus won't be - automatically removed during checkpoints. NULL + automatically removed during checkpoints unless this LSN + gets behind more than + from the current LSN. NULL if the LSN of this slot has never been reserved.