fix(Dockerfile): rollback to postgres:9.4-alpine #10
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
We are going back to 9.4 because upgrade 11.1 would require and upgrading proceedure using tools like pg_upgrade and scripts that would do the dump and restore on the postgres data directory. 🙈
|
Tested this and I agree, the upgrade to 11.1 is complicated (10 would be complicated too) and we haven't thought it all the way through. |
kingdonb
approved these changes
Nov 30, 2018
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.
We are going back to 9.4 because upgrade 11.1 would require and upgrading procedure using tools like pg_upgrade and scripts that would do the dump and restore on the postgres data directory. 🙈
Props to @kingdonb for finding this issue during an upgrade test! 👍
@duanhongyi @till @rwos just so you are aware.