Re: Return of the pg_wal issue..

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(at)gmail(dot)com <mailto:paulbrindusa88(at)gmail(dot)com>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com