Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recent change to specify PostgreSQL v11 is effectively a downgrade, breaks existing deployments. #13

Open
nepella opened this issue Jul 10, 2020 · 0 comments

Comments

@nepella
Copy link

nepella commented Jul 10, 2020

Before 9b4b400, docker-compose.yml specified an unversioned tag (alpine) for the PostgreSQL image. When I deployed Manifold v4.1.2 with it, postgres:alpine was equivalent to postgres:12-alpine. Commit 9b4b400, merged into v5.0.0, specified postgres:11-alpine, so upgrading to Manifold v5.0.0 effects a downgrade of the Postgres database, and Postgres refuses to work with the existing data. From the service logs:

PostgreSQL Database directory appears to contain a database; Skipping initialization
[1] FATAL:  database files are incompatible with server
[1] DETAIL:  The data directory was initialized by PostgreSQL version 12, which is not compatible with this version 11.8.

I solved this for myself by patching docker-compose.yml to reference postgres:12-alpine. Would that be acceptable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant