From: Michael Paquier <michael@paquier.xyz>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Clarify old WAL files cannot be removed until they are summarized
Date: Wed, 11 Dec 2024 09:18:48 +0900
Message-ID: <Z1jaaLi2vq-Wpk9y@paquier.xyz> (raw)
In-Reply-To: <fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com>
References: <fd0eb0a5-f43b-4e06-b450-cbca011b6cff@oss.nttdata.com>
On Fri, Oct 18, 2024 at 02:25:15AM +0900, Fujii Masao wrote:
> 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?
>
> @@ -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>
Sounds like a good idea to me. I'd suggest to add a link to
runtime-config-wal-summarization as it is the first reference to WAL
summarization in this file.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../Z1jaaLi2vq-Wpk9y@paquier.xyz/2-signature.asc)
download
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: michael@paquier.xyz, 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: <Z1jaaLi2vq-Wpk9y@paquier.xyz>
* 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