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 1taf8E-003ww8-C1 for pgsql-general@arkaria.postgresql.org; Wed, 22 Jan 2025 18:07:14 +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 1taf8C-003J2O-Py for pgsql-general@arkaria.postgresql.org; Wed, 22 Jan 2025 18:07:12 +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 1taf4v-003C56-WB for pgsql-general@lists.postgresql.org; Wed, 22 Jan 2025 18:03:50 +0000 Received: from fhigh-b2-smtp.messagingengine.com ([202.12.124.153]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1taf4s-000x3e-2O for pgsql-general@postgresql.org; Wed, 22 Jan 2025 18:03:49 +0000 Received: from phl-compute-05.internal (phl-compute-05.phl.internal [10.202.2.45]) by mailfhigh.stl.internal (Postfix) with ESMTP id CDA83254015C; Wed, 22 Jan 2025 13:03:45 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-05.internal (MEProxy); Wed, 22 Jan 2025 13:03:45 -0500 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=1737569025; x=1737655425; bh=fzHTa/7F+RSsmdqCpGSfvgfeLcNfy04H5EUh/04hfBM=; b= PneQK//HkrKZJ0iHxW41TgKgGV6NswgCq1hKr7fl/naDHFDWZWzM60pc2yPC1zbX octbyfpFzeJj9DDSqoGa2LQ2Sfh7pdYHlpCW1pyNKoiDG/l4yrBJ7qkijqxfJWJK uDTZT/dExgr9l0ejMLHGbo0UxQHRA8MJoTVkNKJvjOPimkXunA76346tjfoRBZtv 6VOA4YS6v81thXi//YPW9o5wmshsH7HAIIAE87yYzaVJNOpY7pLLjxrAQPKZsZX9 Rae/j9cwLKZ8cE9wg/ceDwMuYU9M7Jx74uNRT/xQ5gvWlvv3XsqZqsLAFNwvP/ew DIublZSCrpsJTzWEam4TMw== 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=1737569025; x=1737655425; bh=f zHTa/7F+RSsmdqCpGSfvgfeLcNfy04H5EUh/04hfBM=; b=gNSZTXYBJwFwJK2/M WbiK/wts3/bifkqUNg1n5VgDVjxoP+/1SakJD8popwNhXuOapRr2RUHi95yoj19i kTjWmIcRwuaEb9DxLuYmjP1rx6/6g3Bq2cre/psufiekcndJMc+y+jX/2cFsxubM 0rYPY6PvJD2B+BcQJ2s/+GcVIr7Kwc01s47lrbONkI1bSbbrPspRfTGr991IZvbG ccaq8Izxz5goV+BS6VFdhMC4h55GiplzWG3lmXeAImSNAhRo0Wv5f6xbdaljNnUm ESG/mMmukkxqweYun66q5QuvJ3f94cJS0Zvd9AWwMOKOq+eakeqFsx7dcvL2n4im MfKiw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrudejfedgvdefudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtvdej necuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrh esrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepffelgeeifefgveduhedt hfekuedtffejveegffegjeevtdehgfduieetfeehjeehnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghk lhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpd hrtghpthhtohepphgruhhlsghrihhnughushgrkeeksehgmhgrihhlrdgtohhmpdhrtghp thhtohepphhgshhqlhdqghgvnhgvrhgrlhesphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Jan 2025 13:03:44 -0500 (EST) Message-ID: <0ba329ef-62aa-4ab3-aefd-141baabced3b@aklaver.com> Date: Wed, 22 Jan 2025 10:03:44 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Return of the pg_wal issue.. To: Paul Brindusa , pgsql-general References: 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 1/22/25 09:33, Paul Brindusa wrote: > Good afternoon, > > Following below we are facing a similar issue and im getting a real buzz > to get this working myself, speaking to my DBA  in the  company has > actually left me a bit cold as he is not good with postgres. > > So I want to try and get a solution for this and fix this issue with the > pg_wal files filling up the drive at a ridiculous rate. I have been > manually moving logs to a different directory but have had no luck in > finding an actual solution. > > The cluster is a 3 node cluster with HA which is running wirth patroni. > > Please help me out, I will mention that I have test cluster spun up in > case something needs testing. > > Also want to give a shout out to Lorenz Albe's for posting stuff about > wal files on his company blog. > > Again any help will be greatly appreciated. A good deal more information is needed to troubleshoot this: 1) Postgres version(s). 2) The Patroni version. 3) The Patroni configuration. 4) Definition of 'ridiculous rate'. 5) Relevant information from the logs. > > > " On one of our postgres instances we have the pg_wal/data folder up to > 196GB, out of 200GB disk filled up. > This has stopped the posgresql.service this morning causing two > applications to crash. > Unfortunately our database admin is on leave today, and we are trying to > figure out how to get the disk down? > Any ideas or suggestions are more than welcome. > > Thank you in advance." > > > -- > Kind Regards, > Paul Brindusa > paulbrindusa88@gmail.com > -- Adrian Klaver adrian.klaver@aklaver.com