canonical / canonical/postgresql-operator
Blocking the use of different versions of Postgres
- Dominant language
- Python
- Stars
- 20
- Forks
- 36
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 30
Description
#### Issue
Currently, you can use different versions of Postgres when you connect a storage with a different version of Postgresql, which can lead to incorrect operation.
It is necessary to implement a restriction on the use of different versions of postgres with the introduction of a new version of [charmed-postgresql-snap](https://github.com/canonical/charmed-postgresql-snap)
#### Implementation
Blocking the use of different versions of Postgres
#### Test cases
Check the use of different versions postgresql.
Contributor guide
Research direction
The issue names no source files, tests, or entry points. Start by locating the storage connection and PostgreSQL version handling, then inspect how the charm detects the versions of the existing storage and the new charmed-postgresql-snap. Done means mismatched PostgreSQL versions are rejected and the described version-mismatch test cases pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100