Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run PostgreSQL upgrades locally & in new testing environment #1374

Open
rachelekm opened this issue Feb 8, 2024 · 0 comments
Open

Run PostgreSQL upgrades locally & in new testing environment #1374

rachelekm opened this issue Feb 8, 2024 · 0 comments

Comments

@rachelekm
Copy link
Collaborator

rachelekm commented Feb 8, 2024

This card is to setup a testing environment created from a snapshot of our production RDS instance, and then run upgrades locally and in testing environment. These two tasks will allow us to gain familiarity with the production database upgrade steps and ensure no issues for #1375.

The last PostgreSQL update was completed by first testing on develop and then running updates on the Production database. See step-by-step here. There shouldn't be difficulties between versions given the last few PostgreSQL upgrades and available documentation. However, we have limited developer familiarity with production database updates, last run 2 yeas ago, and at one point our development environment had gotten out of sync with our RDS environment (though this should have been addressed in last update). In addition, we are upgrading Python versions, psycopg2, and PostGIS as part of #1372 task list. Given scope of upgrades and a potential lack of parity and familiarity, a temporary staging database made from a duplicate of production to run upgrades will lower risk and production downtime.

@rachelekm rachelekm changed the title Evaluate and prep prod database update steps Run PostgreSQL upgrades locally & in new testing environment Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants