postgresql.conf edit parameters

[neelasha-09]

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? v1.6.2
• Where do you run it - cloud or metal? Kubernetes or OpenShift? Openshift
• Are you running Postgres Operator in production? [yes | no] Not yet
• Type of issue? [Bug report, question, feature request, etc.] question

Hi Team, We are having an issue with our postgres-operator-cluster with disk space is full. /dev/sdk 976M 894M 15M 99% /home/postgres/pgdata

Manually, we modified the below values in postgresql.conf file,

archive_mode = 'off'
log_statement = 'none'

and the FS is now ok

I wanted to check if there is a way to turn off the archiving using cluster manifest? I see the parameter log_statement: "all" but not for archive.

Can you suggest how can we turn off the archive mode ?

[FxKu]

Couldn't you just increase the volume size? You could also check, how big your Postgres logs are at $PGLOG and truncate a few files there. Maybe you have unnecessary indexes that can be dropped, too? Don't see the point of turning off archiving for saving disk space because you loose continuous backup and PITR capability.

[neelasha-09]

@FxKu The reason we ask this is because of the the replica pod is not able to sync with the master. This causes the lag in replica due to the WAL files not getting deleted and the disk space of the master and of the working replicas fill up fast causing the FS to be full & cluster in Syncfailed state. We have already opened the ticket for same

https://github.com/zalando/postgres-operator/issues/1492 https://github.com/zalando/postgres-operator/issues/1498

[pawanku2]

@neelasha-09 We also face the same issue . Disk get full . We also tried changing archive_mode = off. But patroni again back it to archive_mode = on. Did you find a way to stop the wal file size increase?