BI-2212 - Update Postgres Version#454
Merged
Merged
Conversation
nickpalladino
approved these changes
May 28, 2025
mlm483
commented
May 28, 2025
mlm483
commented
May 28, 2025
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.
Description
Story: https://breedinginsight.atlassian.net/browse/BI-2212
Update the postgres version to 17.
This change will affect local and the changes to bi-docker-stack (PR here) will affect qa-test, but not rel-test or production, which use RDS (those are a separate task).
Dependencies
None
Testing
Running this without existing data will work without issues.
To upgrade data locally, you can use
pg_dumpwith the old database and then restore to the new postgres instance, but unless you really need that data locally, it's probably not worth it.The upgrade for rel-test and production will be similar to the process I described, but slightly different because we use RDS, not a local postgres docker container.
Checklist: