zalando / zalando/postgres-operator
autovacuum does not work
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
I've got many tables with dead rows, but autovacuum doesn't work.
SELECT last_autovacuum, autovacuum_count, vacuum_count FROM pg_stat_user_tables; shows what last_autovacuum is NULL, autovacuum_count is 0 for all tables.
- Which image of the operator are you using?
registry.opensource.zalan.do/acid/postgres-operator:v1.5.0 - Where do you run it - cloud or metal? Kubernetes or OpenShift?
Bare Metal K8s - Are you running Postgres Operator in production?
yes - Type of issue?
Bug report
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported query in the affected PostgreSQL cluster and inspect the operator and database configuration related to autovacuum. Compare the behavior with the reported operator image version; done means autovacuum runs and the relevant pg_stat_user_tables counters and timestamps update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100