Details here: https://github.com/LemmyNet/lemmy/issues/3165
This will VASTLY decrease the server load of I/O for PostgreSQL, as this mistaken code is doing writes of ~1700 rows (each known Lemmy instance in the database) on every single comment & post creation. This creates record-locking issues given it is writes, which are harsh on the system. Once this is fixed, some site operators will be able to downgrade their hardware! ;)
Holy hell. Post this to one of the programming-related communities. That is interesting.
Not that interesting when it turns out it was an ORM artifact.
True. I have experienced quite a few of those… But, still interesting nonetheless.