Bump postgres to v15 locally #3233
Conversation
…d to upgrade in the fall
murny
requested review from
ConnorSheremeta,
jefferya,
lagoan and
pgwillia
as code owners
| @@ -15,7 +15,7 @@ volumes: | |||
| services: | |||
| postgres: | |||
| restart: always | |||
| image: postgres:12-alpine | |||
| image: postgres:15-alpine | |||
There was a problem hiding this comment.
@pgwillia I'm wondering if UAT is still being used? and if this is okay? If's its not really being used or we able to just wipe the DB and start fresh this might be fine.
Otherwise, we need to do a proper upgrade for UAT for Postgres (where we dump the DB, start the new database with the new server and import the dump, or do a no downtime approach, etc).
There was a problem hiding this comment.
UAT is available, but definitely not heavily used. Matt Kingcroft is filling in for Sean and I don't think he's been onboarded about UAT.
Is there value in practicing database migration in UAT? I don't have a strong opinion.
There was a problem hiding this comment.
I don't there's probably much value for our team practising database migrations in UAT (unless Neil finds that useful for himself, but I assume he doesn't need to practice for this kind of stuff). If the data in UAT is ephemeral in nature, then the easy approach would to just start fresh (or do a simple dump and reload after migrating it)
Context
Neil mentioned production is on v13 of postgres and in the fall he wants to upgrade to v15: https://ualbertalib-di.slack.com/archives/CSEHP0L0K/p1695137129713599
So we should be at least matching production, but we can get ahead locally and see if there are any problems with v15 before the upgrade.
All test past locally, so think we should be okay for the fall upgrade