It is very common to see many customer cases where a sudden increase in disk space usage is caused by a lot of WAL segments filling up the WAL directory (pg_wal). Panicking customers generally ask Why isnt PostgreSQL deleting them?. The most common reasons we used to find were: Failing WAL archival A slot holding [&]

https://www.percona.com/blog/2020/09/09/why-postgresql-wal-archival-is-slow/