[FAQ Bot] NEW: Postgres fails to start after upgrading from postgres:16 to postgres:18 #112
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.
✨ FAQ NEW
Course: data-engineering-zoomcamp
Section: module-1 (This is a Docker/Postgres startup/configuration issue that fits Module 1 (Docker and Terraform) since it concerns container volume mounting behavior and initialization of a data directory.)
Related Issue: #111
Question
Postgres fails to start after upgrading from postgres:16 to postgres:18 in Docker
Decision Rationale
The proposal describes a Postgres startup failure after upgrading to Postgres 18 due to a changed data directory mount path in Docker, not covered by existing FAQs. The closest related item is a permissions issue in Module 1, but this exact upgrade-path startup problem and its fix are not currently documented.
Placement Details
module-1postgres-18-startup-after-upgrade🤖 Generated by FAQ Bot
Closes #111