Skip to content

Conversation

@scelikcapa
Copy link

The volume path has to be updated after PostgreSQL v18+. Otherwise, it throws an error:

Error: in 18+, these Docker images are configured to store database data in a
db-1 | format which is compatible with "pg_ctlcluster" (specifically, using
db-1 | major-version-specific directory names). This better reflects how
db-1 | PostgreSQL itself works, and how upgrades are to be performed.
db-1 |
db-1 | See also docker-library/postgres#1259
db-1 |
db-1 | Counter to that, there appears to be PostgreSQL data in:
db-1 | /var/lib/postgresql/data (unused mount/volume)
db-1 |
db-1 | This is usually the result of upgrading the Docker image without
db-1 | upgrading the underlying database using "pg_upgrade" (which requires both
db-1 | versions).
db-1 |
db-1 | The suggested container configuration for 18+ is to place a single mount
db-1 | at /var/lib/postgresql which will then place PostgreSQL data in a
db-1 | subdirectory, allowing usage of "pg_upgrade --link" without mount point
db-1 | boundary issues.
db-1 |
db-1 | See docker-library/postgres#37 for a (long)
db-1 | discussion around this process, and suggestions for how to do so.

The volume path has to be updated after PostgreSQL v18+. Otherwise, it throws an error
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