Skip to content

Upgrade to postgres 18 - #5

Open
mgpeter wants to merge 1 commit into
mainfrom
mgpeter/upgrade-to-postgres-18
Open

mgpeter wants to merge 1 commit into
mainfrom
mgpeter/upgrade-to-postgres-18

Conversation

@mgpeter

@mgpeter mgpeter commented Aug 21, 2026

Copy link
Copy Markdown
Owner

No description provided.

- Postgres 18 relocated PGDATA under the image, so pointing the old
  17-era bind mount at it silently initializes an empty cluster
  instead of failing; the standalone profile and the NAS compose file
  move to a new `pgdata18` folder with the old one left as the rollback
- Aspire's dev volume needed a fresh name for the same reason, plus
  an explicit image tag pinned before the data volume is configured
  so it targets the right container path
- Pin the backup sidecar to the matching major, since pg_dump refuses
  to dump a newer server
- cambelt.app is unaffected: it uses Asgard's shared 17.6 cluster, so
  the suite now runs one major ahead of production
@mgpeter
mgpeter force-pushed the mgpeter/upgrade-to-postgres-18 branch from c5afb4e to 2a9c26b Compare September 27, 2026 10:47
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

Successfully merging this pull request may close these issues.

1 participant