fix(infra): pin PGDATA path for forward-compatible Postgres upgrades#707
Merged
Conversation
Postgres 18 changed the default PGDATA from /var/lib/postgresql/data to /var/lib/postgresql/18/docker. Pinning PGDATA keeps existing dev volumes working across the version bump.
wpfleger96
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PGDATA=/var/lib/postgresql/dataexplicitly in the postgres service's environment block indocker-compose.ymlThe repo currently uses
postgres:17-alpinewhere this path is already the default, making this a no-op today. The explicit pin ensures volume mounts remain stable when Renovate PR #676 upgrades to Postgres 18, which changes the defaultPGDATAlocation. Setting it proactively avoids a brokendocker compose upafter the image tag bump.