this post was submitted on 24 Aug 2024
86 points (95.7% liked)
Fediverse
27935 readers
325 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
0.19.4 requires upgrading Postgres (and exporting/importing the database to the new version).
I just don't have time for that right now since my Postgres DB is on a dedicated machine and is shared with a few other active services.
They make breaking changes like that in patch releases?? Do they not follow semver?
Lol, yeah.
I think they plan to do semvar, but if I recall (and I may be wrong), since it's pre 1.0.0, they're "allowed" to make breaking changes since it's still in alpha.
The lemmy devs are not exactly industry developers.
Hell, they don't even respect gpdr, and one day the EU is going to wreck an instance and maybe an admin too if they didn't separate liability properly.
Technically this is entirely within semver since it's 0.x.y.
this isn't true. it was incorrectly stated in the upgrade guide but has been removed a while ago. it was supposed to be a recommendation due to some issues with postgres 15. there is no postgres upgrade required between 0.19 releases.
Why would you do that, given that Lemmy is 0.x software?
Because I'm not made out of server resources lol. I've already got a beefy server that's dedicated to Postgres and is well tuned, and everything else already hooks into it. I've also had better performance (and less overhead) with one, big well-tuned database versus lots of stack-local databases.
If Lemmy goes tango uniform, then any damage would be limited to its schema. The worst it could really do would be resource starve it, but Zabbix would alert me of that quickly.
My understanding is that postgres doesn't need to be upgraded. It'll still work with version 15 or whatever you have. Postgres 15 has some sort of memory leak that they're trying to get away from, so they made 16 the new default.
Same with the "requirement" to upgrade pict-rs to the latest version. You can keep the old version if you don't care about the new image proxy feature.
Really it's a not a problem of needing to upgrade this stuff, but a problem with the documentation which isn't clear. That's a big weak spot for the Lemmy project in my opinion. I only learned the above information from lurking a bit in the Matrix chat.
Good to know. Last time I recall a DB upgrade being mentioned, it was when pg15 became the new minimum so I assumed this was the same case. That one was required since they used some new feature in pg15 (don't recall the specifics, but my test instance that was on pg14 failed the DB migrations for that lemmy release, and that was why)
Ah, interesting. That experience combined with the wording of "this update requires postgres 16", I can see where the confusion comes from.
Interestingly enough, they fixed the documentation. Now it says "We recommend upgrading to PostgreSQL 16 due to a known memory leak in PSQL 15. To use the new image proxy feature, pict-rs version 0.5+ is required." https://join-lemmy.org/news/2024-06-07_-_Lemmy_Release_v0.19.4_-_Image_Proxying_and_Federation_improvements