Re: Clarify old WAL files cannot be removed until they are summarized
Fujii Masao <masao.fujii@oss.nttdata.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-docs@lists.postgresql.org
Date: 2024-12-12T15:08:06Z
Lists: pgsql-docs
Attachments
- v2-0001-doc-Clarify-old-WAL-files-are-kept-until-they-are.patch (text/plain) patch v2-0001
On 2024/12/11 9:18, Michael Paquier wrote: > 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. Yes, that sounds like a good idea. I've updated the patch accordingly. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
Commits
-
doc: Clarify old WAL files are kept until they are summarized.
- 87e16d632622 17.3 landed
- 56499315a74f 18.0 landed