summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFujii Masao2024-12-15 02:18:18 +0000
committerFujii Masao2024-12-15 02:18:18 +0000
commit56499315a74f97d220373e396903c389d85c8933 (patch)
treed6c43d83c4c554edb0e96165b7aa1989e6058c80
parent969bbd0fafc0f4d9ef504ca98a127c8d945f71a0 (diff)
doc: Clarify old WAL files are kept until they are summarized.
The documentation in wal.sgml explains that old WAL files cannot be removed or recycled until they are archived (when WAL archiving is used) or replicated (when using replication slots). However, it did not mention that, similarly, old WAL files are also kept until they are summarized if WAL summarization is enabled. This commit adds that clarification to the documentation. Back-patch to v17 where WAL summarization was added. Author: Fujii Masao Reviewed-by: Michael Paquier Discussion: https://postgr.es/m/[email protected]
-rw-r--r--doc/src/sgml/wal.sgml3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index a34cddb5ed4..b908720adea 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -643,6 +643,9 @@
until the situation is resolved. A slow or failed standby server that
uses a replication slot will have the same effect (see
<xref linkend="streaming-replication-slots"/>).
+ Similarly, if <link linkend="runtime-config-wal-summarization">
+ WAL summarization</link> is enabled, old segments are kept
+ until they are summarized.
</para>
<para>