Skip to content
Discussion options

You must be logged in to vote

hey, I tested the DB/migration path on a fresh 18 DB and it works.

The repo still pins postgres:15-alpine in compose/prod/k8s/CI, but the backend is just SQLAlchemy + asyncpg through DATABASE_URL. I ran the Alembic migrations against a fresh postgres:18-alpine DB and upgrade head completed cleanly. Running it a second time was a no-op at the same head.

The catch is existing data. Do not reuse the same postgres_data volume from 15 after changing the tag. I tested that too and 18 refused the 15-initialized data dir. So for a new private install, 18 looks fine to try. For an existing install, do dump/restore or pg_upgrade, not just an image-tag swap.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@lagset
Comment options

Answer selected by lagset
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants