![](https://reddthat.com/pictrs/image/4802e205-69c2-4685-9a6e-fbcc167c3272.png)
Before I start reading, if this has anything to do with differential privacy, I’m going to be disappointed.
Self Proclaimed Internet user and Administrator of Reddthat
Before I start reading, if this has anything to do with differential privacy, I’m going to be disappointed.
2nd best reporting in.
A faster db. Just the regular performance benefits, https://www.postgresql.org/about/news/postgresql-16-released-2715/
Also, Lemmy is built against v16 (now) so at some point it will eventually no longer JustWork
The script will be useless to you, besides for referencing what to do.
Export, remove pg15, install pg16, import. I think you can streamline with both installed at once as they correctly version. You could also use the in place upgrade. Aptly named: pg_upgradeclusters
But updating to 0.19.4, you do not need to go to pg16… but… you should, because of the benefits!
That awkward moment when you are the person they are talking about when running beta in production!
See my PR for a new backup script. https://github.com/LemmyNet/lemmy-ansible/pull/210
I’ll get to adding it to the main docs on the weekend.
Tldr, piping your backups via docker is CPU expensive. Directly writing to filesystem in a postgres compatible format with compression is faster and more efficient on the CPU.
My 90GB+ (on filesystem) db compresses to 6GB and takes less than 15 mins.
Been running this since -rc1 & 0.19.1 for the past 13 hours. No issues related to Federation since! just higher CPU load compared to 0.18.x releases.
Thanks for another great release. Suppose I should go fix our ansible ey?
Should be fixed. (It already got merged: https://github.com/LemmyNet/lemmy/pull/4213)
Oh that’s super nice!
That’s why I asked if they were hiring. Sounds like a nice place to work. I work at a job that doesn’t allow me to have non-work time during my allotted on-work time. ie 9-5.
Obviously I agree that this is definitely on the riskier side of the line, whether it crosses into NSFW territory is unfortunately dependant on everyone’s own definition.
See the other comment(s) from Red that go into detail regarding what is going to be done regarding the future of the community and the riskiness.
Removing the post at this time would not be for the benefit of the community when we can have active discussions on what we want the community to become.
Unfortunately I have a feeling that some of the commenters here are from All and are not active subscribers. So they may not be used to seeing content like this. They also may not understand the difference between instances and the nuances with federation.
Edit: This is the comment from Red regarding what we are going to do: https://reddthat.com/comment/2250572
But you are doing it while you are “at work”? So you are using company time to look at fediverse content.
What job do you have that your company pays you to look at Reddthat/Fediverse? Are you hiring?
Don’t forget & in community names and sidebars.
Constantly getting trolled by &
No reddthat too? 😜
What a hero!
Oh I was wrong, after further reading this looks to be a lot better than what I was thinking.
I must have been thinking about another methodology of attempted privacy over a dataset.