-
Notifications
You must be signed in to change notification settings - Fork 18
Upgrading Postgresql from v11.7 to v14.8 Locally
Matthew Thornton edited this page Apr 29, 2024
·
2 revisions
- First, stop all active Caseflow containers
-
make down
ormake down-m1
depending on your system
-
- Optional: Remove the
appeals-db
container if it's still showing as activedocker rm appeals-db
- Remove the volume used to house Caseflow's Postgresql data files
docker-compose down --volumes
- Optional: Explicitly remove the volume if it still persists
docker volume rm caseflow_postgresdata
- Ensure you're checked out to a branch with the Postgres image set to v14 in your docker-compose files (ex:
master
) - Restart your containers
-
make up
ormake up-m1
-
- Reinitialize your database schema:
bundle exec rake db:create db:schema:load
- Reseed your database
make reset
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- Appeals Consumer
- Caseflow Reader
- Caseflow eFolder
- Caseflow Hearings
- Caseflow Certification
- Caseflow APIs
- Appeal Status API
- Caseflow Dispatch
-
CSUM Roles
- System Admin
- VHA Team Management
- Active Record Queries Resource
- External Integrations
- Caseflow Demo
- Caseflow ProdTest
- Background
- Stuck Jobs
- VA Notify
- Caseflow-Team
- Frontend Best Practices
- Accessibility
- How-To
- Debugging Tips
- Adding a Feature Flag with FeatureToggle
- Editing AMA issues
- Editing a decision review
- Fixing task trees
- Investigating and diagnosing issues
- Data and Metric Request Workflow
- Exporting and Importing Appeals
- Explain page for Appeals
- Record associations and Foreign Keys
- Upgrading Ruby
- Stuck Appeals
- Testing Action Mailer Messages Locally
- Re-running Seed Files
- Rake Generator for Legacy Appeals
- Manually running Scheduled Jobs
- System Admin UI
- Caseflow Makefile
- Upgrading Postgresql from v11.7 to v14.8 Locally
- VACOLS VM Trigger Fix M1
- Using SlackService to Send a Job Alert
- Technical Talks