MrKaplan

mostly indexes and in some cases changing queries.

there are lots of queries in piefed that are not using indexes and some that are just unoptimized sql statements. for example, there are a lot of like '%foo%' queries but there are no GIN indexes to support those queries.

unfortunately it’s a hassle to manage custom indexes as they can’t be part of the code migrations without fucking other things up, so for the time being i’m just keeping track of them by having a dedicated prefix for the index names and updating them in our DB manually. once/if they’re upstreamed i’m removing our custom ones again, but it’s not possible for us to track them in code.

some of the code changes for sql statements were upstreamed, but rimu didn’t want to incorporate all of them without evidence of performance impact. it took me a bit to make sense of the more complex statements, but i don’t have time or motivation to demonstrate performance impact for them, so i’ll just keep the remainder in our fork. e.g. 1bf4d8409b vs c41d47850e.

should be working now

this is likely related to a bug that will be fixed in the next piefed release (currently in a development branch)

there are a few running 1.5 still: https://fedidb.com/software/piefed

most, like us, have updated to 1.6 already.

deleted by creator

hi, what do you mean by this?

we can programmatically move all the subscribers

i’m afraid there was a bit of a misunderstanding. we can move the Lemmy.World and PieFed.World subscribers only, not subscribers on other instances. while we could update that on our end, that would only mean that we send content to other instances with subscribers, but it wouldn’t be synchronized on their end and show it e.g. in subscribed feeds or their subscribed communities lists.