Migrating to PG 18

[rohittp0]

Warning

Be careful this can cause data loss, always start with a backup. Do not proceed if you are not sure what you are doing

The django-shared-base has been updated to Postgres 18, this is a breaking change from 17 and can cause data loss if not properly migrated.

Two possible paths:

1. In your fork override the postgres version and volume mount point to stay on PG 17
2. Migrate to the data

For migrating the data do a pg_dump on your current db. Delete the postgres volume. Update to 18 then load the data back in.

[rohittp0]

@Lascade-Co/backend

[rohittp0]

I would recommend

1. Dumping data from prod
2. Upgrading staging
3. Loading data to staging
4. Verify staging works fine
5. Then proceed with prod