canonical / canonical/postgresql-operator
archive volume usage
- Dominant language
- Python
- Stars
- 20
- Forks
- 36
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 30
Description
1. We can avoid removing files from the archive volume `/var/snap/charmed-postgresql/common/data/archive` during restoration from the backup and when configuring asynchronous replication.
2. If it is necessary, we might consider moving `pg_wal` to the archive volume instead of removing it on recovery from failure.
Contributor guide
Research direction
Start by tracing the backup restoration and asynchronous replication entry points that handle /var/snap/charmed-postgresql/common/data/archive and pg_wal. Determine the current file-removal behavior and the intended archive-volume lifecycle. Done requires an agreed approach for preserving archive files or relocating pg_wal, with the affected behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100