Add upgrade scripts for database files #28
Draft
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
Postgres changes the format of the database files on disk between major versions. This means that in order to upgrade a postgres database, it is not sufficient to just bump the container versions.
To help with this process, we now can use migration scripts that will take care of updating the database version without the need of a manual dump/restore.
Why
pg_upgrade
requires the new and old postgres binaries to be present, therefore the image now containstwo postgres versions in parallel. This does affect image size (~35MB increase), but not runtime memory
consumption, as only one version of postgres is ever running at the same time.
References
DEVOPS-1292
Checklist