Fix updater PostgreSQL client version#128
Merged
Merged
Conversation
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
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.
What changed
pg_dumpmatches the bundled PostgreSQL serverWhy
Control-plane updates failed during the required pre-upgrade database backup. The bundled server was PostgreSQL 18.4, while the updater image installed
pg_dump17.10 through Alpine's unversionedpostgresql-clientpackage. PostgreSQL rejects dumps when the client is older than the server, so the updater aborted before deploying the target version.Impact
Database backups can run against the bundled PostgreSQL 18 server, allowing updates to proceed. The updater remains a client-only image and does not inherit PostgreSQL server volumes, ports, entrypoints, or stop behavior.
Validation
go test ./...go vet ./...git diff --check{"ok":true}on both architectures