Skip to content

Update postgres Docker tag to v18 - #33

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/postgres-18.x
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/postgres-18.x

Conversation

@renovate

@renovate renovate Bot commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
postgres (source) service major 17-alpine → 18-alpine
postgres (source) major 17-alpine → 18-alpine

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@kilo666mj

Copy link
Copy Markdown
Owner

Superseded by #34. A plain tag bump breaks Compose: the postgres 18 image refuses the existing /var/lib/postgresql/data mount. #34 moves the mount, documents the 17 -> 18 dump/restore, and makes CI run the database tests uncached.

@kilo666mj kilo666mj closed this Oct 18, 2026
@renovate

renovate Bot commented Oct 18, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 18.x releases. But if you manually upgrade to 18.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate
renovate Bot deleted the renovate/postgres-18.x branch October 18, 2026 09:48
kilo666mj added a commit that referenced this pull request Oct 18, 2026
* Upgrade bundled PostgreSQL to 18 with a safe migration path

The postgres:18 image moved PGDATA to /var/lib/postgresql/18/docker and
its volume to /var/lib/postgresql, and its entrypoint refuses to start
when anything is mounted at the old /var/lib/postgresql/data path. The
plain tag bump in #33 would therefore stop every Compose install,
including fresh ones.

- compose.yaml: postgres 18-alpine, volume mounted at /var/lib/postgresql.
  The volume name is unchanged on purpose: an existing PostgreSQL 17
  volume makes the 18 container refuse to start instead of silently
  coming up empty.
- docs/operations.md: dump/restore procedure for 17 -> 18, keeping the
  old data in a rollback volume, plus the rollback steps.
- CI: run go test with -count=1. The setup-go cache restored every
  package as "(cached)", so the PostgreSQL integration tests did not
  run against a new server version.
- CI: new "compose postgres" job starts PostgreSQL from compose.yaml on
  a fresh volume and checks the server major matches the image tag;
  image publishing now depends on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* TEMPORARY: rehearse PostgreSQL 17 -> 18 upgrade procedure

Runs the docs/operations.md steps on a real PostgreSQL 17 volume. To be
removed before merge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Remove temporary PostgreSQL upgrade rehearsal

The rehearsal passed on the PR (run 39116646413): PostgreSQL 18 refused
the old volume, the dump restored on 18, the startup schema re-applied,
and the rollback volume brought 17 back.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant