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 1ruLFI-004g9Z-Qf for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Apr 2024 23:51:21 +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 1ruLFH-00CmCb-N4 for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Apr 2024 23:51:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruLFH-00CmCT-Di for pgsql-hackers@lists.postgresql.org; Tue, 09 Apr 2024 23:51:19 +0000 Received: from wfout1-smtp.messagingengine.com ([64.147.123.144]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruLFE-0006b7-Fm for pgsql-hackers@postgresql.org; Tue, 09 Apr 2024 23:51:18 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.west.internal (Postfix) with ESMTP id 4805C1C000FF; Tue, 9 Apr 2024 19:51:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 09 Apr 2024 19:51:13 -0400 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=fm2; t=1712706672; x=1712793072; bh=8rqXefVxjs jRIO3NOYsx6y6pQcepQtlKQ8lxEkUbfoE=; b=Z0BcCLrNurmMzuzTElAMlpINte R2smJ14Lu5UyAb90LGfnXqJsFqyzkOSAxOl9lOnX6Q/CHPpYEZCMOZ0EVtyGlz6w 43bWfyfkhGlg5okZesXD5gBxwri09JWb0kHmwyqCbSx6RIiIuel1yRrXRYZ73XUQ /4DUrHkZZwpcmrT5CpSmpRz9o5usRt0t4tkyS40IPN8BcSRxCiIORcW7Us0AI6+W amxDlFjZIVh069dSS9OwVBiHC7rd1NzULv3nkld9qq2vMTJb6JHLapTfc4Eq8qo7 boBOL66ZmRZSxfMiPRieuG6grtRKHzA4XZst+KA+todEeV7OVNxkLFk9y+lg== 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-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1712706672; x=1712793072; bh=8rqXefVxjsjRIO3NOYsx6y6pQcep QtlKQ8lxEkUbfoE=; b=aFIpkl+ijpIZkyoLkVdDc0duQ19A+SSEUpDRwdJnOqro OOo/z1YInmSJO63FeVHcLUD3mjlCTUQ/zvjM6nhj9tyMyeehf1NtqjJvvt2/OcdI RAq38ppA3ksAEhvteQPQFIjaJNzUA4WUeOpDpSh9urq1GPZIBeAwxV0utnamUlC3 x+QMzsBk/lv6GiAX8GSU4t/sZ7hVauVxBYLWrQLM2fstpIuSAUKuXQn4pjqtBXLq WtI3zJgcEduLlB0s0NSPmnW3XLrMJCCGZtNYK0DoBFQ4XE+NVleqz4TSkJXmCd+b D8IT0fHBr+yrn91IkGKKT8DT7NSt39uJfzibC7fEOA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudehhedgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepgeffjeevgfevuddvjedtvddt ieejheduueelvddufedtgfefjedvkeevkeeivddvnecuffhomhgrihhnpehpohhsthhgrh gvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 9 Apr 2024 19:51:09 -0400 (EDT) Date: Wed, 10 Apr 2024 08:50:56 +0900 From: Michael Paquier To: David Steele Cc: "Andrey M. Borodin" , Alvaro Herrera , Stefan Fercot , Robert Haas , Tomas Vondra , "pgsql-hackers@postgresql.org" Subject: Re: post-freeze damage control Message-ID: References: <202404091545.7zont3umry74@alvherre.pgsql> <4D31BF67-4138-41DC-831D-4BCE0466A59F@yandex-team.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="rbw5VSo6aBQAd0Pm" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --rbw5VSo6aBQAd0Pm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 10, 2024 at 09:29:38AM +1000, David Steele wrote: > Even so, only keeping WAL for the last backup is a dangerous move in any > case. Lots of things can happen to a backup (other than bugs in the > software) so keeping WAL back to the last full (or for all backups) is > always an excellent idea. Yeah, that's an excellent practive, but is why I'm less worried for this feature. The docs at [1] caution about "not to remove earlier backups if they might be needed when restoring later incremental backups". Like Alvaro said, should we insist a bit more about the WAL retention part in this section of the docs, down to the last full backup? [1]: https://www.postgresql.org/docs/devel/continuous-archiving.html#BACKUP-INCREMENTAL-BACKUP -- Michael --rbw5VSo6aBQAd0Pm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmYV1GAACgkQnvQgOdby QH0ilA/9EVVV19dfHbDnUduzTTG80kgWVE3MO7xf064OVUzZbqsHS8PSLMS/TXGG ia2Fe677NZb8ImzRmST3tAxg1FWIe3Q8Uh+7AIX/gYXYNdHT6qb8euuDQVLgpnC8 QW9oKvJDMvzuhDY0cULGhty4pl6CITOY2vXRCPKTY1V6JGKL1M3tOFnEwDju6mU1 kn+5Xpo4BucC7BZRvR6je/be5ZI8b3ZrJjQPw3Yl4WrqtEIrl7GmtZdDL6brUF00 oDtlh0HrNtjlIf9QYDqSvO9Wp78Ub+9KXlL6Yauu+ylrTi+uDpSpoe8pkIRq9QbZ sDb0H7qtRiP9pk7bB6xScAUQAUnRdqhuYm91DRSat1cS/WqEHeFhoK39iUUSXEKN cbG2gjQG9hD11ZfAG3GL+nDhAVQ5yLZtxp961BeoNuuUbalagnNvQ7VSXq8hXsuM IqBDG5/vxFqJSWckX62qUSMcC80+oMNFxjDDucRfInUo/9ZC0QutcJR86E4fTegz yre4YlEYEKQEFXvOgVvmp2opbTpgT6gT04120DtlSOn7pMO40EA8ln0uNSoRvIZj JK57WL3Kp2Lc+9c5wBv2hV/b2xnRW4iStsbeDGkPw/VcKcbVp4a92K1+xHSXEmuL zYhfOBFzpAzDH1+4+ycQDFAnNAGGA77Py2R9kFklVgpaLDiIUDI= =pZhe -----END PGP SIGNATURE----- --rbw5VSo6aBQAd0Pm--