Open rg2609 opened 1 month ago
Hey @rg2609!
When we see the WAL fill up like this, it is almost always due to backups not being run frequently enough. When a backup runs, it captures the current state of the database, allowing postgres to clear out the WAL files as they are no longer needed.
I recommend that you set up a schedule for your backups, or if you already have a schedule set, try increasing the frequency with which you run your backups so that the WAL can be regularly flushed out. Here are the docs for all things backups:
If you need further assistance, I recommend that you join our Discord group and ask questions there as it is a more active forum for the postgres-operator community.
I have installed the Crunchydata Postgres operator using the helm chart and I'm using the NFS file system storage as PVC with 200GB data. When I run
kubectl get pods
, the output shows that 1 instance has stopped working out of 4.The error that I'm encountering is:
Upon further investigation, I found that the
/pgdata/pg16_wal
is using up all the space.When I run
kubectl exec -it dravoka-postgres-instance1-c7ck-0 -- bin/bash
and thendf -h
, I get the following output:Is there a way to configure the WAL size limit and archive the old WAL files while also deleting the old archived files?