chore(db): upgrade bundled PostgreSQL 17 → 18 (#96) - #225
Open
jakub-przepiora wants to merge 1 commit into
Open
Conversation
- docker-compose: postgres:17-alpine -> postgres:18-alpine. - docker-compose: move the data volume mount from /var/lib/postgresql/data to /var/lib/postgresql. The PG18 official image stores data in a major-version subdirectory and REFUSES to start against the old /…/data mount (docker-library/postgres#1259) — the tag bump alone is not enough. - README + docs bumped to PostgreSQL 18 (minimum supported stays 14+). - CHANGELOG note incl. the existing-deployment path: a major version can't reuse a 17 data dir in place — dump on 17, restore into 18. Verified end-to-end on a fresh stack: postgres:18.4-alpine boots with the logical-replication flags (wal_level=logical, slots/senders), the full migration set + seeders + admin run cleanly, PGDATA lands at /var/lib/postgresql/18/docker, and the app-level immutable audit_logs table is intact. Per request, the in-place data-migration runbook (pg_upgrade) is out of scope for this change (fresh installs + dump/restore only).
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Closes #96 (image/config/docs scope — in-place data-migration runbook intentionally out of scope per request; fresh installs + dump/restore only).
Changes
docker-compose.yml:postgres:17-alpine→postgres:18-alpine.docker-compose.yml: data volume mount/var/lib/postgresql/data→/var/lib/postgresql. The PG18 official image stores data in a major-version subdirectory and refuses to start against the old/…/datamount (docker-library/postgres#1259) — the tag bump alone is not enough.docs/development.mdbumped to PostgreSQL 18 (minimum supported stays 14+).Verified end-to-end on a fresh PG18 stack
postgres:18.4-alpineboots with the logical-replication flags →wal_level=logical✓engineering_documents)PGDATA=/var/lib/postgresql/18/docker(new version subdir) ✓audit_logsintact ✓ (audit immutability is app-level, not a DB trigger — unaffected by the PG version)Out of scope (per request)
The in-place
pg_upgraderunbook for migrating an existing 17 data volume. Existing deployments dump/restore into a fresh volume; the changed mount path is compatible with that.🤖 Generated with claude-flow