postgres role - version 14 of pg introduced breaking change in password_encryption
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1.4k
- Forks
- 379
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 8
Description
before version 14:
password_encryption = on
in 14: Available values: md5, scram-sha-256
so the role must distinguish between versions and in new version probably use scram-sha-256 as default with an option to move back to md5
password_encryption = scram-sha-256
the most annoying thing is that with password_encryption = on version 14 does not start giving an error.
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 with the PostgreSQL role's password_encryption configuration and its handling of PostgreSQL versions. Check how the role represents version-specific defaults and user overrides, then verify behavior for PostgreSQL before and after version 14. Done means version 14 uses a valid default while retaining an option to select md5, without breaking older versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100