agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedFrom: Fujii Masao <masao.fujii@oss.nttdata.com>
To: pgsql-docs@lists.postgresql.org
Subject: Clarify old WAL files cannot be removed until they are summarized
Date: Fri, 18 Oct 2024 02:25:15 +0900
Message-ID: <fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com> (raw)
Hi,
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. Attached patch adds that clarification to
the documentation. Thought?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From 1339bbb4096df0182913c19a6277a105a2f5bee8 Mon Sep 17 00:00:00 2001
From: Fujii Masao <fujii@postgresql.org>
Date: Fri, 18 Oct 2024 02:20:49 +0900
Subject: [PATCH v1] 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.
---
doc/src/sgml/wal.sgml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index a34cddb5ed..5588f31c55 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -643,6 +643,8 @@
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 WAL summarization is enabled, old segments are kept
+ until they are summarized.
</para>
<para>
--
2.46.2
Attachments:
[text/plain] v1-0001-doc-Clarify-old-WAL-files-are-kept-until-they-are.patch (1.1K, ../fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com/2-v1-0001-doc-Clarify-old-WAL-files-are-kept-until-they-are.patch)
download | inline diff:
From 1339bbb4096df0182913c19a6277a105a2f5bee8 Mon Sep 17 00:00:00 2001
From: Fujii Masao <fujii@postgresql.org>
Date: Fri, 18 Oct 2024 02:20:49 +0900
Subject: [PATCH v1] 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.
---
doc/src/sgml/wal.sgml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index a34cddb5ed..5588f31c55 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -643,6 +643,8 @@
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 WAL summarization is enabled, old segments are kept
+ until they are summarized.
</para>
<para>
--
2.46.2
view thread (5+ messages) latest in thread
Message-ID: <fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com>
Permalink: ../fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com/
Also on: postgresql.org/message-id/fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com
reply
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: masao.fujii@oss.nttdata.com, pgsql-docs@lists.postgresql.org
Subject: Re: Clarify old WAL files cannot be removed until they are summarized
In-Reply-To: <fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox