Bump postgres to version 15 #151
Merged
Conversation
This file contains 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
marjisound
reviewed
Sep 29, 2023
| }), | ||
| allowMajorVersionUpgrade: true, |
There was a problem hiding this comment.
Just for my own understanding, what would happen if we don't use this field? allowMajorVersionUpgrade
There was a problem hiding this comment.
The upgrade would be blocked by RDS - it's like an extra safety feature. Once this is merged and the DB has been upgraded on PROD i think we should remove this line again so we don't accidentally upgrade!
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 does this change?
There is currently a mismatch between the version of postgres we are running locally via docker and the version we are running in RDS. Rather than downgrade our local version I decided to upgrade to 15.3 in RDS. As we're using 15.3 locally already, we have a good amount of confidence that we won't have any compatability issues.
How to test
This has already been deployed on CODE and doesn't appear to cause any issues.
Deploy steps for PROD:
How can we measure success?
Queries that work locally should also work in AWS 🎉