-
Notifications
You must be signed in to change notification settings - Fork 4
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
Postgresql migration epic #2735
Comments
|
We prioritized migrating services that were connecting to postgres on Some projects have staging running on postgresql 13 while production is still running on postgresql 10. These will require extra testing before we migrate and upgrade production. |
We migrated gscatalog/geoserver to a lambda on AWS. |
Remaining work is documented in #4383. |
Component parts:
lib-postgres3
andlib-postgres-prod1
to the new replicated servers,lib-postgres-prod3
and its replicated boxlib-postgres-prod2
)Check off when the project has been migrated to the new servers and to psql 13 if necessary. Projects that run on postgres:
Related postgres tickets include #2210 #1522 #2305 #2405 #2444 #2464.
Edit: make the list a checklist.
The text was updated successfully, but these errors were encountered: