Bump Postgres 12.2 to 15.x on docker-compose.yml #9641
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Bump Postgres 12.2 to 15.x on docker-compose.yml
Why
Misskey v13 requires Postgres 15.x
Additional info (optional)
Should work properly 🥴
User needs to manually update PostgreSQL.
Part 1 - Backup DB from PostgreSQL 12.2
Part 2 - Import DB to PostgreSQL 15
Part 3 - Confirm import of DB has no serious errors
$ docker-compose logs db
and confirm there are not any errors in the import stage. Below is a list of known errors, and their resolution.Error 1
These errors are bad and need to be investigated.
Running
vacuumdb
has apparently resolved these issues. Please read the optional command as an alternative to step 1.Error 2
These errors can be ignored.
Part 4 - Upgrade Misskey
Alternative Step 1 - Vacuum DB before backup