_Rho_@lemmy.worldtoLemmy Server Performance@lemmy.ml•Lemmy scaling/performance: Move expensive PostgreSQL triggers to scheduled jobs. · GitHub Issue #3528 · LemmyNet/lemmy
3·
1 year agoMoving more processes to be asynchronous make sense. As that’s also how Reddit’s backend works.
Sort of an unrelated question, but are Lemmy instances specifically designed to work on top of Postgres? Or could they technically use “any” database?
This is fascinating
My biggest takeaway from reading through the GitHub comments though is that it seems like no one actually knows where much of the SQL comes from? As in it’s possible that the bug in question is just one manifestation of old, handwritten Postres code that may or may not be optimized (Or even logical?).
I don’t mean this in a critical way, as things like this are bound to happen in an open-source, federated world. However, I would think a comprehensive audit of the Lemmy Postgres triggers, queries, etc could potentially save us all from some future headaches.