MIME-Version: 1.0
References: <CAFeSbqjySUzp_Q4XNR_ajnV84O=om0f5rzpjPsQaNitDkxXjHw@mail.gmail.com>
 <CAPnRvGuJ5oxEJ1xmJ2ULU63VNCKMcpbvkU-vO9wEdehA2KyZRw@mail.gmail.com>
In-Reply-To: <CAPnRvGuJ5oxEJ1xmJ2ULU63VNCKMcpbvkU-vO9wEdehA2KyZRw@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 1 Nov 2024 09:10:06 -0400
Message-ID: <CAKAnmmJwRQekE-4bGAmVEoP9KQdLtWz9+=CzBYGa_11KTbeQ2g@mail.gmail.com>
Subject: Re: pg_wal folder high disk usage
To: Muhammad Usman Khan <usman.k@bitnine.net>
Cc: Paul Brindusa <paulbrindusa88@gmail.com>, pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000009f6f720625d9a9c9"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmJwRQekE-4bGAmVEoP9KQdLtWz9%2B%3DCzBYGa_11KTbeQ2g%40mail.gmail.com>
Precedence: bulk

--0000000000009f6f720625d9a9c9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 1, 2024 at 2:40=E2=80=AFAM Muhammad Usman Khan <usman.k@bitnine=
.net>
wrote:

> For immediate space, move older files from pg_Wal to another storage but
> don't delete them.
>

No, do not do this! Figure out why WAL is not getting removed by Postgres
and let it do its job once fixed. Please recall the original poster is
trying to figure out what to do because they are not the database admin, so
having them figure out which WAL are "older" and safe to move is not good
advice.

Resizing the disk is a better option. Could also see if there are other
large files on that volume that can be removed or moved elsewhere, esp.
large log files.

Hopefully all of this is moot because their DBA is back from leave. :)

Cheers,
Greg

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

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Nov 1, 2024 at 2:40=E2=80=AFAM Mu=
hammad Usman Khan &lt;<a href=3D"mailto:usman.k@bitnine.net">usman.k@bitnin=
e.net</a>&gt; wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr">For immediate space, move olde=
r files from pg_Wal to another storage but don&#39;t delete them.<br></div>=
</blockquote><div><br></div><div>No, do not do this! Figure out why WAL is =
not getting removed by Postgres and let it do its job once fixed. Please re=
call the original poster is trying to figure out what to do because=C2=A0th=
ey are not the database admin, so having them figure out which WAL are &quo=
t;older&quot; and safe to move is not good advice.</div><div><br></div><div=
>Resizing the disk is a better option. Could also see if there are other la=
rge files on that volume that can be removed or moved elsewhere, esp. large=
 log files.</div><div><br></div><div>Hopefully all of this is moot because =
their DBA is back from leave. :)=C2=A0</div><div><br></div><div>Cheers,</di=
v><div>Greg</div><div><br></div><div><br></div></div></div>

--0000000000009f6f720625d9a9c9--