zalando / zalando/postgres-operator
Error: could not restore file "00000004.history" from archive: command not found
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
I need your assistance with an issue I'm facing in my replication process. One of the clusters on my production server encounters an error indicating that the "00000004.history" file couldn't be restored from the archive (FATAL: could not restore file "00000004.history" from archive: command not found). However, upon inspecting the pg_wal (formerly known as pg_xlog) folder, I found a file named 00000003.history with the following content: "1 B/C0FFFCF0 no recovery target specified".
I'm unsure about the next steps to take in this situation. Regarding the content in the 00000003.history file within the pg_wal folder, I'm seeking guidance on what actions should be taken or if there's a tool available to address this issue.
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 reviewing the PostgreSQL replication and archive-restore configuration for the affected cluster, including the reported pg_wal file 00000003.history and the missing 00000004.history. Determine why the archive-restore command is unavailable and what corrective action is expected; the issue is resolved when the cause and recovery steps are documented or verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100