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 1t6Shd-00D95V-SX for pgsql-general@arkaria.postgresql.org; Thu, 31 Oct 2024 10:46:57 +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 1t6Shc-0003zL-11 for pgsql-general@arkaria.postgresql.org; Thu, 31 Oct 2024 10:46:56 +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 1t6Shb-0003zD-Lx for pgsql-general@lists.postgresql.org; Thu, 31 Oct 2024 10:46:56 +0000 Received: from mail-oi1-x22d.google.com ([2607:f8b0:4864:20::22d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t6ShZ-003yyI-QP for pgsql-general@postgresql.org; Thu, 31 Oct 2024 10:46:55 +0000 Received: by mail-oi1-x22d.google.com with SMTP id 5614622812f47-3e60f6ea262so427886b6e.1 for ; Thu, 31 Oct 2024 03:46:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730371612; x=1730976412; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fbBTwIaQHJQVRB/mT+QQ+1FcujODZ+AZbVa1YjpfbUo=; b=ai1+wqB4wLyxXL8Ke/qFDdzTNBepFZu4nb+I1zjxjW3LEmqn65gE1F242OyfBRxbeS 4W3xJ7V55OcJyDyY43QZhMU2lQK4Y0P70z/BTDRYVF4fWzXRAl8RFxf1RFGo4q6Eb6N0 9dOQDJZjumd+kh2Les2DV593aJXCAQEzfca5lAq8/p/M2TguQcXR6inKMbDgdzrVovLS diJ+rtPdzUuvc1bQtdEqUHCRwbpX/uWVfBPbhaJZVzDT/X9t4cuJ/oqMgyu++/d+KGSU 6GJ8mDo1qPn4oUmqd0yuPLANy8CbhiXWDkwzyQBjKAGdlsHTvTVqu9ScoBpOhivgS0oh cKjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730371612; x=1730976412; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fbBTwIaQHJQVRB/mT+QQ+1FcujODZ+AZbVa1YjpfbUo=; b=Uitn9RfnL6UT+q3N4yhHhHgox68tyfqI0no5WqlIiS7KRI9alQ5mGutxKcmLgDCNMU J7ccO1Bj4o/IDipDyKiGD2Gy77kKK8Rfpi/ak+wdTiZIsT5ARIckPGCdHptqd1vQqnla aAdwMjpj0kpzUUIcITsnQhiYhFTsRqXEYIN/mZh4odwgEYO918p5KFuSYgIHgTm/VvDS euSuEIVMrlQ+yEKJAUmkB2lzSLSrQQXGxP+UCKBRpYMQzm4S4ht0kKcs5E91OMbmMh1L 6SCI40paQG2h6SdCSxZ2Zj5TVSrxe0bTVF47MItKMJxxNeNRjWFV+/fJrQYt/B/YWyMc qp2w== X-Gm-Message-State: AOJu0YyEB2BZX/2tVDbx3Ik1oaFqM8dRwcsNfxqjqtjYlDUmPJ5lFFyV M474ekudq+WnDjp24yjFoQEXDKP5sOAUGq6THuGTQgsjg8nTm036NN8cU8pfm40qV4px09GIc7W 3ONTHQ2W46WCXj4l2Otmem0dz24M= X-Google-Smtp-Source: AGHT+IHQkqjJQDDtk38U+zKZBZpChs2cRFTHjrUl52gvE+mbYyIUU3Lxjpn4gMWne0E2n+FT+UfnidM4dsEKzNY6xCk= X-Received: by 2002:a05:6808:2e90:b0:3e5:f2f4:9a73 with SMTP id 5614622812f47-3e63847ec7dmr20495137b6e.21.1730371611848; Thu, 31 Oct 2024 03:46:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Thu, 31 Oct 2024 06:46:40 -0400 Message-ID: Subject: Re: pg_wal folder high disk usage To: Paul Brindusa Cc: pgsql-general Content-Type: multipart/alternative; boundary="00000000000040f9750625c389ab" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000040f9750625c389ab Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Oct 31, 2024 at 6:36=E2=80=AFAM Paul Brindusa wrote: > Good morning, > > 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. > Is data supposed to be replicated to a second (remote) database? Such growth would be explained if that network link is broken. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. crustacean! --00000000000040f9750625c389ab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Oct 31, 2024 at 6:36=E2=80=AFAM P= aul Brindusa <paulbrindusa88= @gmail.com> wrote:
Good morning,

On one of our postgres instances we have the pg_wal/= data folder up to 196GB, out of 200GB disk filled up.
This has st= opped the posgresql.service this morning causing two applications to crash.=
Unfortunately our database admin is on leave today, and we are t= rying to figure out how to get the disk down?
Any ideas or sugges= tions are more than welcome.
=C2=A0
Is data supposed to be replicated to a second (remote) database? Such grow= th would be explained if that network link is broken.

--
Death to <Redacted>,= and butter sauce.
Don't boil me, I'm still alive.
<Redacted> crustacean!
--00000000000040f9750625c389ab--