zalando / zalando/postgres-operator
Cant update timescale parameter
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Updating parameter in CRD but nothing applied, only max_standby_archive_delay and max_standby_streaming_delay
postgresql:
parameters:
max_connections: '300'
shared_buffers: '80MB'
max_standby_archive_delay: "900"
max_standby_streaming_delay: "900"
timescaledb.max_background_workers: "64"
version: "15"
postgres-operator-8595fcf9bc-c47r4 postgres-operator time="2024-02-21T11:54:54Z" level=debug msg="patching Postgres config via Patroni API on pod db-cluster-core/db-cluster-core-0 with following options: {\"postgresql\":{\"parameters\":{\"max_standby_archive_delay\":\"900\",\"max_standby_streaming_delay\":\"900\"}}}" cluster-name=db-cluster-core/db-cluster-core pkg=cluster
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 tracing how PostgreSQL parameters from the CRD are selected for the Patroni API patch, using the reported debug log as the expected behavior to compare against. Reproduce with the shown parameters and verify that timescaledb.max_background_workers is included in the applied configuration alongside the two max_standby settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100