![](https://lemmy.ca/pictrs/image/5c3eb492-892d-401a-97b5-5b020368d08b.jpeg)
Nothing too crazy. My discovery this week is that our custom postgres conf actually wasn’t being applied and I had never noticed. It got fixed a while ago but I haven’t been following the upstream ansible repo - https://github.com/LemmyNet/lemmy-ansible/commit/22aa431a3d1ed8437a418633e9d92ae4af45bbf5
So just fixing up postgres to actually use the conf with our tuned wal & worker settings, along with the usual apt-get update/upgrade/reboot.
No, but developers are free to implement things in whatever crazy way they can dream up.