PostgreSQL upgrade 13-alpine to 14/15-alpine

[tomkolp]

Describe the issue

I tried to upgrade PostgreSQL from version 13 to 14.
I followed the docs (completed all steps):
https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-postgresql-container
After starting the stack, I get a message about the wrong password and the lack of scram-sha-256 encryption.
How to switch to scram-sha-256 encryption from plaintext?

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

1I followed the docs (completed all steps):
https://docs.weblate.org/en/latest/admin/install/docker.html#upgrading-postgresql-container
2After starting the stack, I get a message about the wrong password and the lack of scram-sha-256 encryption.

Expected behavior

Please help me update PostgreSQL. It's probably in the documentation.

Screenshots

No response

Exception traceback

No response

Additional context

No response

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

[nijel]

PostgreSQL 14 seems to default to scram-sha-256 for POSTGRES_HOST_AUTH_METHOD. The question is: Where is the error – is the password wrongly stored in PostgreSQL, or is the client library having problems? What is the actual error message?

The client library should work just fine with that because we're already using PostgreSQL 15 in our CI since WeblateOrg/docker-compose#160. So most likely it's the password in the database, in that case recovery should be

docker-compose exec -T database psql --username weblate --dbname postgres -c "ALTER USER weblate WITH PASSWORD 'weblate'"

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[tomkolp]

@nijel I confirm this solution works. We managed to move from PostgresSQL 13 straight to version 15.