MIME-Version: 1.0
References: <CAFeSbqjySUzp_Q4XNR_ajnV84O=om0f5rzpjPsQaNitDkxXjHw@mail.gmail.com>
In-Reply-To: <CAFeSbqjySUzp_Q4XNR_ajnV84O=om0f5rzpjPsQaNitDkxXjHw@mail.gmail.com>
From: Muhammad Usman Khan <usman.k@bitnine.net>
Date: Fri, 1 Nov 2024 11:40:36 +0500
Message-ID: <CAPnRvGuJ5oxEJ1xmJ2ULU63VNCKMcpbvkU-vO9wEdehA2KyZRw@mail.gmail.com>
Subject: Re: pg_wal folder high disk usage
To: Paul Brindusa <paulbrindusa88@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000096ec70625d437e5"
Archived-At: <https://www.postgresql.org/message-id/CAPnRvGuJ5oxEJ1xmJ2ULU63VNCKMcpbvkU-vO9wEdehA2KyZRw%40mail.gmail.com>
Precedence: bulk

--000000000000096ec70625d437e5
Content-Type: text/plain; charset="UTF-8"

First of all check if postgres cannot archive or delete old WAL files. For
immediate space, move older files from pg_Wal to another storage but don't
delete them.
Restart postgres in recovery mode and if archiving is not working then try
disabling it temporarily to let PostgreSQL automatically clear older WAL
files
archive_mode = off

On Thu, 31 Oct 2024 at 15:36, Paul 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 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
>
>

--000000000000096ec70625d437e5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">First of all check if postgres cannot archive or delete ol=
d WAL files. For immediate space, move older files from pg_Wal to another s=
torage but don&#39;t delete them.<br>Restart postgres in recovery=C2=A0mode=
 and if archiving is not working then try disabling it temporarily to let P=
ostgreSQL automatically clear older WAL files<br>archive_mode =3D off<br></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Thu, 31 Oct 2024 at 15:36, Paul Brindusa &lt;<a href=3D"mailto:paulbrindus=
a88@gmail.com">paulbrindusa88@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Good morning,<=
/div><div><br></div><div>On one of our postgres instances we have the pg_wa=
l/data folder up to 196GB, out of 200GB disk filled up.</div><div>This has =
stopped the posgresql.service this morning causing two applications to cras=
h.</div><div>Unfortunately our database admin is on leave today, and we are=
 trying to figure out how to get the disk down?</div><div>Any ideas or sugg=
estions are more than welcome. <br></div><div>=C2=A0<br></div><div>Thank yo=
u in advance.<br></div><div><div><div><div><div><br><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><d=
iv dir=3D"ltr"><div>Kind Regards,</div><div>Paul Brindusa</div><div><a href=
=3D"mailto:paulbrindusa88@gmail.com" target=3D"_blank">paulbrindusa88@gmail=
.com</a></div><div><br></div></div></div></div></div></div></div></div></di=
v>
</blockquote></div>

--000000000000096ec70625d437e5--