![](https://lemmy.world/pictrs/image/947277b7-2103-4901-af81-3f4e1f0a100e.png)
![](https://lemmy.ml/pictrs/image/513b7653-7b74-480a-8a26-ddffde8a9cf2.png)
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.
Aaaaaaand why should I care?