@necrevistonnezr said in Mastodon shown as running, but won't load:
Is it just me or is there a general problem with the new Postgres version?
We have heard of some issues with postgres but so far it's been related to migration issues and not the database itself. We are fixing the migration code so this doesn't happen again.
What happens during migration is: we export the old database, run new postgres, reimport the database. The re-import takes a lot of memory and it's dependent on how much data you have in postgres. The fix we are making now is to give the database more memory when re-importing and then scaling it down after the import is over.
If you hit the above, the fix is easy, just give postgres more memory and restart the code with systemctl restart box. It will them re-import (it keeps track that it failed the last time around).