zalando / zalando/postgres-operator
Standby cluster is in archive recovery state
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi All,
I am using PostgreSQL 16.9.
I observe that standby pod show the state "in archive recovery" in patronictl list instead of streaming/running. Replication is fine and no errors in pod,postgres logs.
Postges15, the state is running for standby cluster. Is this expected?
Cluster: pg-pg16devjun271 (7520543320855007304) -----+---------------------+----+-----------+
| Member | Host | Role | State | TL | Lag in MB |
+--------------------+----------------+----------------+---------------------+----+-----------+
| pg-pg16devjun271-0 | 192.168.11.154 | Standby Leader | in archive recovery | 1 | |
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 comparing the patronictl output for the PostgreSQL 16.9 standby with the reported PostgreSQL 15 behavior, using the standby pod and PostgreSQL logs mentioned in the issue. Done means determining whether “in archive recovery” is expected for this setup or documenting a reproducible discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100