upgrade: Container upgrades existing data on start #24
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.
Postgres will not automatically upgrade existing data when moving
to a different major version. These changes detect existing data
and compare their major versions to see if an upgrade is required.
If the upgrade is required then the correct tooling for the existing
data is installed and
pg_upgrade
is run.Also part of this PR is the restructure of the data volume so that a
versioned sub-directory is used instead of the root of the mount. This
means that as you upgrade major versions you will keep a version of your
data which can be used.
Signed-off-by: Rich Bayliss [email protected]
Change-type: minor