Skip to content

fix: Upgrade postgres 14 -> 17 #67

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

Merged
merged 1 commit into from
Oct 21, 2025
Merged

fix: Upgrade postgres 14 -> 17 #67

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 docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ services:
- codecov

postgres:
image: postgres:14-alpine
image: postgres:17-alpine
Copy link

@seer-by-sentry seer-by-sentry bot Oct 21, 2025

Choose a reason for hiding this comment

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

Bug: Upgrading PostgreSQL from version 14 to 17 without a data migration path will break existing self-hosted deployments with persistent data.
(Severity: Critical 0.85 | Confidence: 0.98)

🔍 Detailed Analysis

The postgres service image is upgraded from postgres:14-alpine to postgres:17-alpine, which is a major version upgrade. For existing self-hosted deployments that use the persistent postgres-volume, the new PostgreSQL 17 container will attempt to read data files created by PostgreSQL 14. Due to binary incompatibility between major PostgreSQL versions, this will cause the container to fail on startup, making the service unavailable. The change lacks the necessary data migration scripts (e.g., using pg_upgrade or pg_dump) or documentation to guide users through the upgrade process.

💡 Suggested Fix

Provide a data migration strategy for users with existing data. This could involve documenting a manual pg_dump/pg_restore process, providing a migration script, or using a tool like pgautoupgrade. At a minimum, clearly document this as a breaking change and advise users on how to handle their existing data.

🤖 Prompt for AI Agent 
Fix this bug. In docker-compose.yml at line 77: The `postgres` service image is upgraded
from `postgres:14-alpine` to `postgres:17-alpine`, which is a major version upgrade. For
existing self-hosted deployments that use the persistent `postgres-volume`, the new
PostgreSQL 17 container will attempt to read data files created by PostgreSQL 14. Due to
binary incompatibility between major PostgreSQL versions, this will cause the container
to fail on startup, making the service unavailable. The change lacks the necessary data
migration scripts (e.g., using `pg_upgrade` or `pg_dump`) or documentation to guide
users through the upgrade process.

Did we get this right? 👍 / 👎 to inform future reviews.

environment:
- POSTGRES_PASSWORD=testpassword
- POSTGRES_USER=postgres
Expand Down
Loading