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 1uluXL-007CBC-Cu for pgsql-general@arkaria.postgresql.org; Tue, 12 Aug 2025 19:19:55 +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 1uluXJ-009Ipw-UP for pgsql-general@arkaria.postgresql.org; Tue, 12 Aug 2025 19:19:54 +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 1uluXJ-009Ipn-2e for pgsql-general@lists.postgresql.org; Tue, 12 Aug 2025 19:19:53 +0000 Received: from fout-b6-smtp.messagingengine.com ([202.12.124.149]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1uluXG-000Efd-1P for pgsql-general@lists.postgresql.org; Tue, 12 Aug 2025 19:19:52 +0000 Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailfout.stl.internal (Postfix) with ESMTP id 5D7791D00118; Tue, 12 Aug 2025 15:19:50 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Tue, 12 Aug 2025 15:19:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding: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=1755026390; x=1755112790; bh=R63cDmCOeFgIfzZtKY0b64i+QLdfA1InlA0ntA3L3K4=; b= YUgqwB8CTOo+oOlp1/imPTs1KRbZBfrQfBpjHfmCtOHM126xas2F2Z0AZ+Fq/GZ9 8TpWQlUaa8j+EK8If/W2TpHPn5+JkxE5DxYZBPmvMDYh+Oxh1+fqkU0M9JJwrYZV GC9jZp2k0ITbCc+S633A/K+chKx2/t9r7r6ay3CC3iTJSdmTkSLoqw1zE0FdiGPK NgD5D6VI9DU/JawcxnLRCHPCoqvBmgi4+DLgCli/mwrqQ+YPP123688+obAIN3Jf 12kwBSaTmS0OoThynD4eT05P4Jt4hh3gjAaWYGS6guEuDRvjVsyb2B5SIvLvNvdR 0YKljjuWzt1S6oIy5Xg1qA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm3; t=1755026390; x=1755112790; bh=R 63cDmCOeFgIfzZtKY0b64i+QLdfA1InlA0ntA3L3K4=; b=FXA8irEKooYg4v6ow M65uFuZwEYV1af7J630eOSNmT31Z96RmBWgXQFyXK9YVXAnAsRe4pBFns01xPyom k+xMO4hJRGXAjHwn1rJ6edwwSpTjVBsrWJJ6YY1RP7U05HWrD5J7N4hhBAoOqpOV kqbx52Nyo9aDewfthYqkVIfbb9946xH1EGr+Y9HI52Y9+RfY34uwiXeV2iTLafyu yEr7EI0ct0qp8nWrIX+wQUMgl3ZqgoRGYUio2a7CT1h0lNx51XI5/ucwb7WU29SD PMu/XIAJCd2JsYdJtDVpSyzq7cea9n02xVmrY50UP2J9suk/6s7HnnIXoOX6exrR Mqj4g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgddufeeiudeiucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhirghn ucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqe enucggtffrrghtthgvrhhnpeeiteevfeegvdfhgfdtudffgfevvddtfffghfduleejjeej fedtvdettdffvedvveenucffohhmrghinhepphhgsggrtghkrhgvshhtrdhorhhgnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghn rdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhoug gvpehsmhhtphhouhhtpdhrtghpthhtohepsghosghjohhllhhifhhfvgesghhmrghilhdr tghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlihhsthhsrdhpohhsth hgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 12 Aug 2025 15:19:49 -0400 (EDT) Message-ID: Date: Tue, 12 Aug 2025 12:19:48 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Questions about the continuity of WAL archiving To: Bob Jolliffe , pgsql-general@lists.postgresql.org References: <73f3723b-f279-43c6-884d-d12b3151ec9e@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/12/25 10:40, Bob Jolliffe wrote: > On Tue, 12 Aug 2025 at 17:14, Adrian Klaver > wrote: > The solution is to use a more capable storage platform. > > > That is an interesting point you make Adrian.  S3 seems quite popular > for this type of archiving.  What would you suggest as a more capable Yes but from here: https://pgbackrest.org/user-guide-rhel.html#s3-support File creation time in S3 is relatively slow so backup/restore performance is improved by enabling file bundling. Where file bundling is explained here: https://pgbackrest.org/user-guide-rhel.html#backup/bundle Though I don't think would help in this case. > (and cost effective) storage platform? I would say anything that does not use object storage and instead uses block storage, so you are not doing the conversion. I have no specific recommendations as this is not something I do, archive to the cloud. > > Regards > Bob > -- Adrian Klaver adrian.klaver@aklaver.com