Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Gregory@grishka@mastodon.social (2026-06-23 22:00:11)
Ugh, I started a database migration on my Smithereen server to add a full-text index to posts. That was around 1 AM. I hoped it would be done in a few hours. It's the middle of the day now and it's still running and only 81% complete.
I really need to figure out how to do these sorts of things without downtime. I also really hope it's the last time I have to add columns to the posts table which contains 2.8 million rows and will only grow over time.
I'm sorry to everyone who uses my server.
---Reply---
Gregory@grishka@mastodon.social (2026-06-23 22:05:11)
Oh actually. Here's the fun part. Queries on that table still work as it's being altered. I should've just been doing this manually and asynchronously...
---Attachments---
image: https://files.mastodon.social/media_attachments/files/116/799/563/389/358/740/original/2ea811be563e034d.png
Reply
---Replies---
Gregory@grishka@mastodon.social (2026-06-23 22:21:40)
So I did a rather odd thing. I updated the schema version manually so the migration won't run again (this is normally done after it's completed) and started another instance of Smithereen while the daemon is busy running the dreaded ALTER TABLE. So it's up now. I had no idea these things don't lock anything now. MySQL 5.x was much less forgiving.