Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLARd-00D8ig-5X for pgsql-docs@arkaria.postgresql.org; Wed, 11 Dec 2024 00:19:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tLARZ-00AH89-Vn for pgsql-docs@arkaria.postgresql.org; Wed, 11 Dec 2024 00:19:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLARZ-00AH81-I2 for pgsql-docs@lists.postgresql.org; Wed, 11 Dec 2024 00:19:10 +0000 Received: from fout-b1-smtp.messagingengine.com ([202.12.124.144]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLARY-002AGP-4G for pgsql-docs@lists.postgresql.org; Wed, 11 Dec 2024 00:19:09 +0000 Received: from phl-compute-03.internal (phl-compute-03.phl.internal [10.202.2.43]) by mailfout.stl.internal (Postfix) with ESMTP id 83E98114020C; Tue, 10 Dec 2024 19:19:07 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-03.internal (MEProxy); Tue, 10 Dec 2024 19:19:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1733876347; x=1733962747; bh=q4rRKGfJSR fmH/w4q9VcP0//GbhujWALGM65k9l/dGA=; b=PJEQ3Tu9Wsm3uLBG8pl3/bl0fj D5P5yQMI/znLFqw4Kkb9qtfg0kD7LMw9chaKf2HzKCkfDGbFWp/TMvg2dtN3jyZ6 VlfoIybZgw6U7yhHDHhJlTpd9EaI/9P1NTSAz6kUbc3Mcyd91P7pAg8jjmUdK+vN 2AmO7HBakxCi7AfLULn7hHLtGvS10A7f8AgOC+X3cZViKYQR3BLs/0tmoZTTqjVn 7FoVAVHlpzU+4IkkIS3CloL6nnxCswEKYKRgMBD77M0G9+Y8PYU2JMhT+bZPl1bj SrFYlpzGqWCBXZ8xAkdt03tRcxBrAkTh7BKTBM+heOrnzV/jsCwInyiboBpg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1733876347; x=1733962747; bh=q4rRKGfJSRfmH/w4q9VcP0//GbhujWALGM6 5k9l/dGA=; b=GkjJW5ZxF9hYHIsE+urj5ILhtt1/j4osexDjgPPFa/CFj6YvoeJ NuPVTbG7FZta+YmA7DeVHBs3iAMzkCpgW/tVXcIZ5aFcbV1Pq9u4jnHJUqQ9uuLg B71VG9QXlO0WT11wepg2jOlePNnKzIYHZi0vb3grlMJ8LwUA/Vx2ZodLKDld3P7x W/69mmxad2YLXzdVXU2T3r4mf5g6HUnATqJ3wTi15NUIPlEMcOR/yYEiDJGYDNg2 N1XF7DvoeFi7DULXYIqwBJoGTr9LUCqQ3g4M7aTIQLh6amPr6mjqoDshZmbLpZ0t dmLjUkNrGGZLZ0PVxrtJlCxsjAKLLLsuX/g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrjeelgddulecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenfghrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffkfhgg tggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoe hmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetleei fedufffhhfdtteelgeeggeffhfekueevteeigfduudevudetgfegiedvjeenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehp rghquhhivghrrdighiiipdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuth dprhgtphhtthhopehmrghsrghordhfuhhjihhisehoshhsrdhnthhtuggrthgrrdgtohhm pdhrtghpthhtohepphhgshhqlhdqughotghssehlihhsthhsrdhpohhsthhgrhgvshhqlh drohhrgh X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 10 Dec 2024 19:19:04 -0500 (EST) Date: Wed, 11 Dec 2024 09:18:48 +0900 From: Michael Paquier To: Fujii Masao Cc: pgsql-docs@lists.postgresql.org Subject: Re: Clarify old WAL files cannot be removed until they are summarized Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="kYGdEeOgSx560N2N" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --kYGdEeOgSx560N2N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 > ). > + Similarly, if WAL summarization is enabled, old segments are kept > + until they are summarized. > 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 --kYGdEeOgSx560N2N Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmdY2mgACgkQnvQgOdby QH2WZQ/8C4fCRApd08Bg37QrzQHVa85UTTtdHgxCuhaXas0tuLOEtIWzUNxp+9Id MSwHUcQEOJW8lFSk5hEVwTqq5TFriq0y2sGi7z00VPoXAqa9PwCgrf/FzI4vaj8I NXR1e1oGzrAK4tHTSTxGLC9rqN/+HYoPR2ebXpdXiFmZHTDyrQl1OBFpqxUCh6iH j0nBiVsYnoFNZX3AtywuqFWkovzZXVwTBoAfNZj6BfZi18v9+1LbK/oovxPWOByu J5V/qK2aPML29gZXzPpsDptuGhyzltslF0S3/jBHLF5XEJT9YYRbBTTnTAaoKn3v dEC9NKlptrRiyfSpcFR5hDJ/SUHPYHbbIvOo/wJyG/HY/m4NX7e+4wX+XhE+DtqR ey6Y7oc4VtymlLZgUHdq77RISPd/YoO5mbV4eW3CAI2TsgBtzYDVvRmV0yn9r8Un VBbAExJcmcpA7ROFcMurMpI0H2mJKJkrYSA8vvyVW/JxEZUtjGKOu2TDpWKm9amZ LknugjrCcEM8gwzQdv5MofQs1hBm9alIH/krDXFTMln9QbN7SmgIvnd9hZ8Gsn+4 XwP7puatbXWPQNW8DSS1/+UHkJ/yLHSJ5kJ9TqdeBEYG3i3AYP2dr8oLPMrWQ68Y bQlkeGIne7Zahkdpd/WJ+v7W1gIxwbn/d7FijhsgLW2hEmZZN3Q= =LJAg -----END PGP SIGNATURE----- --kYGdEeOgSx560N2N--