Skip to content

⬆️ Bump postgres from 17 to 18 in /phantom #93

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

⬆️ Bump postgres from 17 to 18 in /phantom #93

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion phantom/nextcloud.compose.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ services:
environment:
- POSTGRES_DB=nextcloud
- POSTGRES_USER=nextcloud
image: postgres:17
image: postgres:18
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Major-version bump will brick existing data volume.

Jumping straight from postgres:17 to postgres:18 while keeping the same persisted data directory will make the 18 server refuse to start (“database files are incompatible with server”); you must run pg_upgrade, pg_dumpall/restore, or otherwise migrate the cluster first. Please hold this change (or provide the migration tooling) before merging.

🤖 Prompt for AI Agents 
In phantom/nextcloud.compose.yaml around line 77, the image was changed from
postgres:17 to postgres:18 which will break existing on-disk databases; either
revert the image back to postgres:17 to avoid automatic upgrade, or implement an
explicit migration path: add a one-shot migration service or script that runs
pg_upgrade (or pg_dumpall + restore) between the old data directory and a new
cluster, ensure the compose mounts separate data paths for pre- and post-upgrade
clusters, and document the exact steps and backup/rollback procedure; do not
merge the version bump without including the migration tooling and instructions.

networks:
- nextcloud-postgres
- uptime-kuma-nextcloud-postgres
Expand Down