wal recycling problem - Mailing list pgsql-hackers

From Fabrice Chapuis
Subject wal recycling problem
Date
Msg-id CAA5-nLCrbc90DHbX_9Yav72hEXUetkZ9iO8zmKvCvYNZkDHx9g@mail.gmail.com
Whole thread Raw
Responses Re: wal recycling problem
List pgsql-hackers
Hello,

I have a question about the automatic removal of unused WAL files. When loading data with pg_restore (200Gb) we noticed that a lot of WALs files are generated and they are not purged automatically nor recycled despite frequent checkpoints, then pg_wal folder (150Gb) fill and become out of space.
We have a cluster of 2 members (1 primary and 1 standby) with Postgres version 14.9 and 2 barman server, slots are only configured for barman, barman is version 3.7.
The archive command is desactivated (archive_command=':')
I use pg_archivecleanup (with the wal file generated from the last checkpoint in parameter) to remove files manually before the limit of 150Gb so that the restore can terminate.

Why does postgres do not this cleanup automatically, which part of the code is responsible for removing or recycling the wals?

Thanks for your help

Fabrice

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: remaining sql/json patches
Next
From: David Rowley
Date:
Subject: Is it worth adding Assert(false) for iso-8859-1 paths in print_path()?