fix: update Postgres volume mount path for Postgres 18+ compatibility #318
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
Fixes the Postgres 18+ Docker container compatibility issue reported in #305.
Problem
When using Postgres 18+ Docker images, the container fails to start with an error about the volume mount configuration:
Solution
Changed the volume mount path from
/var/lib/postgresql/datato/var/lib/postgresql/.This allows Postgres 18+ to manage its own data directory structure with major-version-specific subdirectories, which is required for proper
pg_upgrade --linkfunctionality.Reference
PGDATAin 18+ to/var/lib/postgresql/MAJOR/dockerdocker-library/postgres#1259Testing
Reported working by:
Fixes #305