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.96) (envelope-from ) id 1vVuRC-009dFV-0w for pgsql-general@arkaria.postgresql.org; Wed, 17 Dec 2025 16:31:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vVuRB-00EWZj-0T for pgsql-general@arkaria.postgresql.org; Wed, 17 Dec 2025 16:31:41 +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.96) (envelope-from ) id 1vVuRA-00EWZZ-0x for pgsql-general@lists.postgresql.org; Wed, 17 Dec 2025 16:31:41 +0000 Received: from fhigh-b6-smtp.messagingengine.com ([202.12.124.157]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVuR8-001GGG-01 for pgsql-general@lists.postgresql.org; Wed, 17 Dec 2025 16:31:40 +0000 Received: from phl-compute-11.internal (phl-compute-11.internal [10.202.2.51]) by mailfhigh.stl.internal (Postfix) with ESMTP id B63B47A0110; Wed, 17 Dec 2025 11:31:35 -0500 (EST) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-11.internal (MEProxy); Wed, 17 Dec 2025 11:31:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc: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=fm3; t=1765989095; x=1766075495; bh=gRbUXglFK0xJvK4gdqdVQ6LPvE8VydSUypp8bDSd6ug=; b= S3Uq5kerq8puocAZtTYnROrVr/iWIArj14ooYGmFmkCp5lLDy3COmvCiVkuaNvBT TFIil0pe9TOp+dr7iJ2QbXIAcgB+dr4o9BaGHgEy/Yza7S1Am8GMvmXOXlufcd6J yOLjfI3QLsOvhUtm5DKExen38ZRjJ8jS2N56KkzPQBVcXLlZMDpBn6ntLAP7FpAI 0pw/iDuY76gPWg3SGWFW++pUW21ITITuJj8MjRi7EdvM2qtB1gnEFC01mZnzct0J Hg/ybM6hNdfe6Ij6cPxiAETe5IxBrbfxU2bcW+e1cFozBcsaGBKVu2I0tUYhUG5r NOb1CdYae2HeMKgDjx6u8g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=fm1; t=1765989095; x= 1766075495; bh=gRbUXglFK0xJvK4gdqdVQ6LPvE8VydSUypp8bDSd6ug=; b=M kiNnZnIGbzgGHjETDZ5f1/ueuPxNw+k1w+Tio6sQQ1rm5hK4RiLj+3mzVoYqzh3y +EN16PcEOodQW31iMijWWHc0aZg3MXOmLGzGPuHJHR53xMCUFMMUcyBNxMA6dU7N r+P8H+I6E42gK8Yc4ltdeKMWmviSe/aUndReNdIxZtg8bIEjewT5vRHHwm7z35Ix PIuhGFLkLDtCVHTFmnOTMmNsqj91EvM7AlpKHOUbW3d3FZebwaRbotdNvNiokDxR wnE/YOIrCuhN+OgxWwq1yOe0KlX2PYZGpM5Eyt3V5nUv8Qf9tCWDNgDZg+Jg7J2n dZ7Ylz3ILdcdp2C+J2j5g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdegfedtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefkffggfgfuvfevfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhirghn ucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqe enucggtffrrghtthgvrhhnpeefgeefieeutdfggfetgefgheekjeehteeileeigfetieek jedvieeviefgheevtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmpdhnsggp rhgtphhtthhopeefpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopegtohhlihhnth hhrghrthesghhmrghilhdrtghomhdprhgtphhtthhopehlrghurhgvnhiirdgrlhgsvges tgihsggvrhhtvggtrdgrthdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlsehlih hsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 17 Dec 2025 11:31:34 -0500 (EST) Message-ID: Date: Wed, 17 Dec 2025 08:31:34 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wal segment size To: Colin 't Hart , Laurenz Albe Cc: PostgreSQL General References: <2a301859ab47c2e83ba5c8ebf75112d61246a8cd.camel@cybertec.at> 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 12/17/25 08:10, Colin 't Hart wrote: > Thanks Laurenz, that confirms what I was assuming. Archiving is via > pgbackrest to a backup server, over SSH. Approx 750ms to archive each > segment is crazy -- I'll check compression parameters too. How much of that time is network travel? What are the configuration settings for the archiving portion of pgBackRest? > > Any reason not to bump it up to 1GB? Or is that overkill? > > /Colin > > On Wed, 17 Dec 2025 at 16:25, Laurenz Albe > wrote: > > On Wed, 2025-12-17 at 16:13 +0100, Colin 't Hart wrote: > > I see very little advice on tuning WAL segment size. > > > > One of my clients has a few datawarehouses at around 8 - 16 TB > > > > On one of the nodes there are approx 15000 WAL segments of 16MB > each, totalling > > approx 230GB. The archiver is archiving approx one per second, so > approx 4 hours to clear. > > > > Would we gain anything by bumping the WAL segment size? > > Very likely yes, if the problem is the overhead of starting the > archive_command. > > Another thing that can slow down archiving is if you compress these > segments > too aggressively. > > Yours, > Laurenz Albe > -- Adrian Klaver adrian.klaver@aklaver.com