@alex @matty since your site is down already, I would suggest a full database vacuum (e.g. sudo -Hu postgres psql then \c pleroma; and finally vacuum full verbose;) as a first step to deal with this. you’re likely running into corrupted indexes or similar. we had dealt with this just before the migration to the edit commit on rebased and again when the commit was merged. a repack (since we are live) in both instances resolved the issue. its long queries that are his issue
that ETS table error it’s throwing we also had, but once the database congestion got under control and we went back down to ~25 load average it stopped