Repository navigation
This release moves the reference Docker Compose stack from PostgreSQL 15 to PostgreSQL 18. The server itself is unchanged and still works with PostgreSQL 15.
⚠️ Action required for existing deployments
PostgreSQL 18 cannot read data files written by PostgreSQL 15, and the postgres:18 image now stores its data in /var/lib/postgresql/18/docker. Simply bumping the image tag is not enough:
- If the volume is still mounted on
/var/lib/postgresql/data, the PostgreSQL 18 container refuses to start. - If the mount is changed without migrating, PostgreSQL 18 starts on an empty database.
Dump the database before switching images, then restore it into PostgreSQL 18:
# 1. Dump while the PostgreSQL 15 container is still running
docker exec shm-db pg_dump -U shm --clean --if-exists metrics > shm-pg15.sql
# 2. Stop the stack and delete the old volume (check the dump first!)
docker compose down
docker volume rm shm_postgres_data
# 3. In compose.yml: image postgres:18-alpine, volume mounted on /var/lib/postgresql
docker compose up -d db
# 4. Restore and start the rest of the stack
docker exec -i shm-db psql -U shm -v ON_ERROR_STOP=1 metrics < shm-pg15.sql
docker compose up -dThe full procedure is in docs/DEPLOYMENT.md.
Changes
compose.yml,README.mdanddocs/DEPLOYMENT.mdusepostgres:18-alpinewith the volume mounted on/var/lib/postgresql.- The dump and restore path was tested from PostgreSQL 15 to PostgreSQL 18.6, and the dashboard API endpoints were checked against PostgreSQL 18.
Documentation fix
The deployment guide wrongly stated that migrations are applied on startup. The server does not run migrations: the SQL files in migrations/ only run when the PostgreSQL volume is initialized for the first time. New migration files must be applied by hand with psql.
Full Changelog: v1.2.7...v1.3.0