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 1taeby-003rwr-Hr for pgsql-general@arkaria.postgresql.org; Wed, 22 Jan 2025 17:33:54 +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 1taebw-002fUq-VE for pgsql-general@arkaria.postgresql.org; Wed, 22 Jan 2025 17:33:52 +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 1taebw-002fUi-Km for pgsql-general@lists.postgresql.org; Wed, 22 Jan 2025 17:33:52 +0000 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1taebt-000wpz-2C for pgsql-general@postgresql.org; Wed, 22 Jan 2025 17:33:52 +0000 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-aaecf50578eso5630966b.2 for ; Wed, 22 Jan 2025 09:33:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737567229; x=1738172029; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=x2JCaxjWPXhC4fOqcEP8vVAEw2XCyUBYDIya1wactrM=; b=OIPTewLn6EpztWSdMMsqM9Ej3/qGNVJPFPDP0IgNAYvtB3gqtAc2/wssV6D9ENo3Z8 ZaLN6Z8cF6TEMGuS56uyqGnis/AGyb7gbs7kIYeEWN4fEmKGtbdRyjL1yNQAGbAP31e+ LC7fLZrOl/IZEppRQ0FO7C3U4qrManrtA/KxkjZlpK3cKsuYJHsaQcYkGzYszbgyUvGG PF31QPWBZSH1MwzCyaq1w5mtAfiUA5TtbnIDLVjDgTwwdvEGEudaCf45GpLLn0LrUvIv s8VgnycWVf20j4jZbuZs5djLq86govrMsM/p2kG7SWf5o9Rx0bowb3EWEeA0lXqNK6dL EcMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737567229; x=1738172029; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=x2JCaxjWPXhC4fOqcEP8vVAEw2XCyUBYDIya1wactrM=; b=hTNS0mt6HHpQS82v1gJY5vPmBtXXTUSVnXqKC7/H0JAO06PHc/2G05qdEQLqBSG44f Gc6LiHJlvxMEpmJAC8kOtwkGOur5NU7vLHhi0vpo3HOWzl/zyhL9AwLorzn88Pqf8Gg6 tWmlp5ZaIqLLnbhZhWtWC8FKs2io41hwNIk36RDZEnCmxP95Yr2Eh1TQ3XPg3UrL8shV o9H4dKLrzjLMlOUmRhqXBWI1hLFo/RxjxMGg/Ett2Sk1/dJ7hwiNkeehwqbsi1/6ombs SgCzpbXZ9+LZ0cI/hCc59NrmYwkwHZsGi0pIIGHqHDohl9ovcc42/qIOIJZ7JZ5h2QKB 0zwQ== X-Gm-Message-State: AOJu0Yxk6G27viv6ZEw7chsXh+Qhu9O85/tHiIvUA7LCMwqcWfC23FLF fIgjsgGJ1vzka15hItw1LJE2e+7l7uhJCye9PSbpOxqxBVM8lzHzZqwUhMVLnyncmI6h2OLVi0R MIQ6Jtrp1BAugmOIlCQOR7MiloWogBire X-Gm-Gg: ASbGncu3ccu2eLI3Yiz/qY1Zr/QdAajpOO+kh2RUPRNQKcQrSkUjgSxpkWZH/X6jnZY mUMjQZ8sbk/0PZO7M8faEL+myNmogpkNS60JYgPCRY4qHEtI1ZUMtteHPkDtW X-Google-Smtp-Source: AGHT+IG5M/qj9k6psLQ+Zo0Ct+FrMEW5ZCfbM6Vbkb8H6hiyTMVUKsPmPXeLoIvGz74ICt7nIMqZPMoIgWj36wANfVs= X-Received: by 2002:a17:907:989:b0:a9a:bbcc:5092 with SMTP id a640c23a62f3a-ab38b380857mr2054895766b.39.1737567228525; Wed, 22 Jan 2025 09:33:48 -0800 (PST) MIME-Version: 1.0 From: Paul Brindusa Date: Wed, 22 Jan 2025 17:33:37 +0000 X-Gm-Features: AbW1kvaVMhFtsEszVJmtFv5qmWgABmw9gtyZ6rHF5sGN1W8koEYW17o-IlWxsEc Message-ID: Subject: Return of the pg_wal issue.. To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000006e076d062c4ee59a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006e076d062c4ee59a Content-Type: text/plain; charset="UTF-8" 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. " 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 --0000000000006e076d062c4ee59a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Good afternoon,

Followi= ng below we are facing a similar issue and im getting a real buzz to get th= is working myself, speaking to my DBA=C2=A0 in the=C2=A0 company has actual= ly 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 t= he pg_wal files filling up the drive at a ridiculous rate. I have been manu= ally moving logs to a different directory but have had no luck in finding a= n actual solution.

The cluster is a 3 node clu= ster with HA which is running wirth patroni.

Pleas= e help me out, I will mention that I have test cluster spun up in case some= thing needs testing.=C2=A0

Also want to give a sho= ut out to Lorenz Albe's for posting stuff about wal files on his compan= y blog.

Again any help will be greatly appreciated= .


" On one of our postgres ins= tances 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.
=C2=A0=
Thank you in advance."=C2=A0


=
--
Kind Regards,
Paul Brindusa
--0000000000006e076d062c4ee59a--