A possible reason for pg_wal buildup is that there is a sort of replication
going on(logical or physical replication) and the receiving side of the
replication has stopped somehow.
This means: a different server that has a connection to your server and is
expecting to receive data. And your server
On Fri, Nov 1, 2024 at 2:40 AM Muhammad Usman Khan
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 poste
