I moved my pinball and retro gaming account @apzpins over today. It was a nice stress test for this instance's hardware and I was glad to see it didn't even break a sweat when pulling all the old followers in.
I also examined the outcome from the #Mastodon image cache clean up script I made earlier. Looking at the picture storage usage graph, it does what I intended.
One curious thing caught my eye in the logs, which was a reaction to tootctl accounts prune:
Error processing 116064247286474491: PG::ForeignKeyViolation: ERROR: insert or update on table "account_stats" violates foreign key constraint "fk_rails_215bb31ff1"
DETAIL: Key (account_id)=(116064247286474491) is not present in table "accounts".
Postgre threw this one. I examined the database structure for some time and came to the conclusion this has to be a very corner case race condition. The referred did not exist and the error was also gone when I ran it again. 🤷
After some web searching I found an old bug report about this which apparently had come to the same conclusion. Seeing that for the first time made me wonder if this was the spot where I had killed the database with Glitch migration. 😆