PG_LOG removal - best practices?

[mgorsk1]

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

• Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.6.3
• **Where do you run it - cloud or metal? Bare Metal K8s
• Are you running Postgres Operator in production? yes
• Type of issue? question

We are deploying postgresql clusters on production using zalando postgres-operator. What we are curious about is what is the recommended way of removing older logs from pg_log directory? In our case we are mounting 32GB PVC and it gets filled within 2-3 days up to 100% which makes the db unusable. I didn't find anywhere in the settings a way to remove older logs, just to truncate them which means it would still grow continously.

[FxKu]

Logs are recycled weekly, hence the numbering of log files from 1 (monday) to 7 (sunday). By default, queries running longer than 500ms will get logged, to better analyze slow queries. Not sure, if that's the reason in your case (could also be logged connections).

You can increase the corresponding config option log_min_duration_statement e.g. by defining it in the manifest (parameters section under postgresql) or change in the pod with patronictl edit-config.